|
|
|
|
|
|
|
| ☜ | ETRIGGERDraft MDC Standard | ☞ | ||||
ETR[IGGER] postcond SP especref
| especref | ::= | │ │ │ |
expr V ^$W[INDOW] ( expec ) [ : einforef ] expr V ^$J[OB] ( erspec ) |
│ │ │ |
| einforef | ::= | │ │ |
See X11.6 | │ │ |
| espec | ::= | │ │ |
See X11.6 | │ │ |
| erspec | ::= | processid , expr1 V "EVENT", expr2 evclass expr3 V evid |
| evid | ::= | expr |
Note that the definitions of espec and einforef are copied from X11.6, the MWAPI. Note also that the range of values allowed for evid depends on the value of evclass, and may be implementation-specific.
ETrigger causes an event to occur, though use of a processid other than the current job’s own processid may be restricted by the implementation. This restricted use does not generate an error, but will not generate an event. Restrictions (if any) must be specified in the implementation’s conformance statement.
If the use is not restricted and the specified event is enabled for either synchronous or asynchronous event processing, the event processing for it will occur subsequently. The event that occurs is specified by evclass and evid. If evid does not specify a valid event, an error condition occurs with an ecode = "M103".
If evclass evaluates to "IPC" and evid is not the current job’s processid an error condition occurs with an ecode = "M104".
The definition in X11.6 reads:
| einforef | ::= | │ │ │ |
glvn @ expratom V einforef |
│ │ │ |
The definition in X11.6 reads:
| espec | ::= | L expr |
|
|
|
|
|
|
|
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 14-Nov-2023, 21:36:45.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)