Metalanguage, letter W

wattribute, wevclass, wident, windowtype, wname, writeargument


wattribute

Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.

This metalanguage symbol represents a code for a characteristic attribute of a window. This metalanguage symbol occurs as an expression that evaluates to either one of the values "ACTIVE", "BCOLOR", "COLOR", "DEFBUTTON", "DISPLAY", "EVENT", "FCOLOR", "FFACE", "FSIZE", "FSTYLE", "ICON", "ICONIFY", "ID", "ITITLE", "MENUBAR", "MIN", "MODAL", "NEXTG", "PARENT", "POS", "PRESOURCE", "RESIZE", "SCROLL", "SIZE", "SIZEMIN", "SIZEWIN", "TIED", "TITLE", "TYPE", "UNITS" or "VISIBLE", or to an implementation-specific value (starts with "Z"), or to an application-specific value (starts with "Y").

Modifed in a future ANSI M[UMPS] Windowing Application Programmer's Interface standard.

Added "PTYPE", "TBCOLOR" and "TFCOLOR" as possible values for window attribute codes.


wevclass

Approved for inclusion in a future ANSI M[UMPS] Language standard.

This metalanguage symbol represents the name of an event class. Possible class names may be "COMM" (events related to devices), "HALT" (events that are generated when processes terminate), "IPC" (events communicated by other processes), "INTERRUPT" (events that are generated when a process is interrupted in an implementation-specific fashion), "POWER" (events generated when loss of electrical power is imminent), "TIMER" (events that are generated when a timer's waiting time has elapsed), "USER" (events that are generated through the ETRIGGER command) and "WAPI" (events related to windowing).


wident

Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.

This metalanguage symbol represents a name in the context of any windowing activity. Such a name consists of alphabetic characters and digits and may start with a % sign.


windowtype

Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.

This metalanguage symbol represents a code that identifies the type of a window. This metalanguage symbol occurs as an expression that evaluates to either of the values "APPLICATION" or "MTERM", or to an implementation-specific value (starts with "Z").


wname

Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.

This metalanguage symbol represents a name of a window. Names of windows consist of alphabetic characters and digits and may start with a % sign.

For portability, the number of characters in the name of a window is limited to 31 characters.


writeargument

Introduced in the 1977 ANSI M[UMPS] language standard.

This metalanguage symbol represents an occurrence of an argument of the WRITE command. Examples of valid arguments for the WRITE command appear in an earlier section. The argument of the WRITE command is either one of a list described below, or an indirection operator (@) followed by an expression that evaluates to a list (separated by commas) of such arguments.

A directly specified WRITE argument can be a format specification, an expression, or an asterisk followed by an expression.

Addition in the 1995 ANSI M[UMPS] language standard.

A format specification can also be a reference to a device control function (see the metalanguage symbols mnemonicspace and controlmnemonic.


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 "W" 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.