|
|
|
|
|
|
|
| ☜ | controlmnemonicDraft MDC Standard | ☞ | ||||
For portability, the controlmnemonic must be one of the controlmnemonics assigned to a control-function specified in the chosen mnemonicspace and interpretation of the format specification must lead to the effect described in the mnemonicspace. There should be no other (side-)effects on the device.
With regard to the status of the process, the value of some special variables may change, e.g. with some control-functions $X and $Y would have to receive proper values. Apart from these documented effects, no other effects may be caused by any implementation.
An implementation needs not to allow for all controlmnemonics in all mnemonicspaces.
|
|
|
|
|
|
|
Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.
Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.
This page most recently updated on 30-Dec-2003, 14:17:32.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)