☜ | Embedded ProgramsAnnotations | ☞ |
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents the name of an external code processor.
Currently, the only external code processor is SQL (ANSI X3.135).
&SQL(SELECT * FROM PATIENT)
Additions in a future M[UMPS] language standard.
The names of external code processors are case insensitive.
&sql(cursor A on EMPLOYEE)
Implementors may include implementation specific extarnal code processors with names like &Zxxx.
&Zunix(grep MDC | more)
The text of the code to be passed to the external code processor may be empty
&ZOPSYS()
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents the specification a code segment that is in a language other than M[UMPS]. A specification of external syntax starts with an ampersand (&), and is followed by the name of the external code processor, followed by a parenthesis open, followed by the text to be processed by the external code processor, followed by a parenthesis close.
The code to be processed by the external code processor may extend over more than one line. When this is the case, any continuation lines must start with the ampersand (&) symbol.
The code to be processed by the external code processor may only contain printable graphic characters (see the metalanguage symbol graphic).
Currently, the only external code processor is SQL (ANSI X3.135).
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents text to be processed by an external code processor.
The code to be processed by the external code processor may extend over more than one line. When this is the case, any continuation lines must start with the ampersand (&) symbol.
The code to be processed by the external code processor may only contain printable graphic characters (see the metalanguage symbol graphic).
Approved for addition in a future M[UMPS] language standard.
Empty strings and blank lines are also permitted.
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 13-Sep-2014, 17:32:47.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)