☜ | Library Element DefinitionsDraft MDC Standard | ☞ |
The definition of a libraryelement states which library the element belongs to, return value type, and full specification.
libraryelement names starting with a Z are reserved for implementors. libraryelement names starting with a Y are reserved for users. All other unused libraryelement names are reserved for future use.
A libraryelement definition is of the form:
libraryelementdef | ::= | libraryelement | ^ library | libraryresult | [ ( L libraryparam ) ] |
libraryparam | ::= | [ . ] | name | [ : [ libdatatype ] | [ : libraryopt ] ] |
libraryresult | ::= | [ : libdatatype ] |
libdatatype | ::= | │ │ │ │ │ │ │ │ │ |
BOOLEAN COMPLEX INTEGER MATRIX NAME REAL STRING Z[unspecified] |
│ │ │ │ │ │ │ │ │ |
libraryopt | ::= | │ │ │ |
o O |
│ │ │ |
If a libraryparam starts with a period then this parameter is passed by reference.
Z is the initial letter reserved for implementation specific libdatatypes. All other values for libdatatypes are reserved for future extensions to the standard.
Input and output values to libraryelements undergo the appropriate data interpretation below:
If no libdatatype is specified for a libraryparam or libraryresult then the libdatatype defaults to STRING.
If no libraryopt is specified then the libraryparam is mandatory. A libraryopt of O specifies that the libraryparam is optional.
Unless otherwise specified in their definitions, library elements are assumed to have the standard domain and range for their function, and no side effects. For each library element with a standard domain, all of its libraryparams can assume any valid values of their respective libdatatypes. Similarly, for each function with a standard range, the libraryresult and all of its output libraryparams can assume any valid values of their respective libdatatypes.
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, 16:27:23.
For comments, contact Ed de Moel (demoel@jacquardsystems.com)