M, mant, marker, mergeargument, mkeyword, mname, mnemonichar, mnemonicspace, mnemonicspacename, mnemonicspec, modaltype, modifierkey, MTERM, mumpsreturn, mval
Introduced in the 1994 ANSI GKS - M[UMPS] language binding.
This metalanguage symbol represents an array of which the elements meet a certain constraint.
v1 ::= M gksnam means: an array v1(1),v1(2),v1(3), ... of which the elements each contain a value that evaluates to a name that meets the constraints specified in the GKS standard.
Introduced in the 1977 ANSI M[UMPS] language standard.
This metalanguage symbol represents a mantissa. A mantissa looks like either one or more digits, optionally followed by a period followed by one or more digits, or a period followed by one or more digits.
This means that valid mantissas are:
123.456
.456
123
but not
.
1234.
Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
This metalanguage symbol represents a code that identifies a method of highlighting elements on a display. This metalanguage symbol occurs as an expression that evaluates either to one of "M,BULLET", "M,CHECK" or "M,DIAMOND", or to a value that identifies an external resource.
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents an occurrence of an argument of the MERGE command. Examples of valid arguments for the MERGE command appear in an earlier section. The argument of the MERGE command is either a name of a variable, followed by an equal sign (=), followed by a name of another variable, or an indirection operator (@) followed by an expression that evaluates to a list (separated by commas) of such arguments.
Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
This metalanguage symbol represents an expression that evalates to the value "M".
Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
This metalanguage symbol represents the name of a menu. Names of menus consist of alphabetic characters and digits and may start with a % sign.
For portability, the number of characters in the name of a menu is limited to 31 characters.
Introduced in the 1995 M[UMPS] Windowing Application Programmer's Interface.
This metalanguage symbol represents the ampersand character ("&").
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents the name of a mnemonicspace. A mnemonicspace is a library containing functions for controlling a specific class of device or file. Such a library may or may not be bound to another standard.
Currently the only known mnemonicspace is "X3.64", which is the ANSI standard that offers the VT-100 compatible terminal controls.
Approved for addition in a future ANSI M[UMPS] language standard.New mnemonicspaces are:
...
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents the syntax for names of mnemonicspaces. A name of a mnemonicspace must start with an identifier character (see the metalanguage symbol ident and may be followed by zero or more characters that are identifier characters, digits, periods (.) or hyphens (-).
Approved for addition in a future ANSI M[UMPS] language standard.The name of a mnemonicspace may also be a specification of a "portable mnemonicspace". Such a specification looks like a caret, followed by the name of a routine, optionally followed by another caret and the name of another routine. The name of the first routine in this context is the name of the routine that will be executed to process controlmnemonics in this mnemonicspace. If a second name of a routine is specified, and a routine of that name exists on the current environment, this is intended to be the a user-written routine to be used instead of the (default) first routine.
Introduced in the 1995 ANSI M[UMPS] language standard.
This metalanguage symbol represents the mnemonicspaces that may be in effect for a certain device or file. This specification is either an expression that evaluates to the name of one mnemonicspace or a list of such expressions (separated by commas) enclosed in parentheses.
Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
This metalanguage symbol represents a code for the extent to which a window with the MODAL window attribute defined disables other windows. This metalanguage symbol occurs as an expression that evaluates to either one of "ANCESTORS", "APPLICATION" or "PARENT" or to an implementation-specific value (starts with "Z").
Approved for inclusion in a future ANSI M[UMPS] Windowing Application Programmer's Interface.
This metalanguage symbol represents the name of a keyboard key that modifies the meaning of other keys. This symbol occurs as an expression that evaluates to one of the values "ALT", "ALTR", "COMMAND", "COMPOSE", "COMPOSER", "CTRL", "CTRLR", "OPTION", "SHIFT" or "SHIFTR".
Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
Application windows are the basic input/output mechanism of the MWAPI. Application windows can contain elements.
MTERM windows are terminal emulation windows that accept M[UMPS] input/output commands. The creation of MTERM windows is reserved.
Approved for inclusion in a future ANSI M[UMPS] language standard.
This metalanguage symbol represents the return value of the function $MUMPS. Such a value consists of three substrings, separated by semi-colons. The first substring is an integer numeric value, the second is an error code ("S" followed by a number), the third piece may be any descriptive text (not containing commas or semi-colons).
Approved for inclusion in a future ANSI M[UMPS] language standard.
This metalanguage symbol represents any value that has the data type MVAL, i.e. any string value.
This document is © Ed de Moel, 1995-2005.
It is part of a book by Ed de Moel that is published
under the title "M[UMPS] by Example" (ISBN 0-918118-42-5).
Printed copies of the book are no longer available.
This document describes the various metalanguage terms starting with the letter "M" that are used throughout the M[UMPS] standards, as well as some other terms that may not be obvious to all readers of the M[UMPS] language standards.
The information in this document is NOT authoritative
and subject to be modified at any moment.
Please consult the appropriate (draft) language standard for an
authoritative definition.
In this document, information is included that will
appear in
future standards.
The MDC cannot guarantee that these 'next'
standards will indeed appear.