Next: outclock Up: Advanced Fields Previous: storemode Contents

## `no_elminfo`

This field has its origins in the `DUPLICATE` action: if this field is set, `hsolve` does not store some information about the model because it is already present in the `hsolve` element that was duplicated. A side effect of this is that this field can also be used without using `DUPLICATE`: this saves some memory, but the command `findsolvefield` and the actions `HPUT` and `HGET` fail to work. When you create the right incoming and outgoing messages before the `SETUP`, this is no problem. Nevertheless the `no_elminfo` field was used in times where computers were shipped with small memories, but in the current era it has become obsolete.