Difference between revisions of "Conformance Clause"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
* <code>ETRIGGER</code> is not yet implemented | * <code>ETRIGGER</code> is not yet implemented | ||
− | * Of the event classes defined in the MDS, only the <code>INTERRUPT</code> 'evclass' is implemented | + | * Of the event classes defined in the MDS, only the <code>INTERRUPT</code> ''evclass'' is implemented |
* The <code>TRIGGER</code> 'evclass' is nonstandard | * The <code>TRIGGER</code> 'evclass' is nonstandard | ||
* The <code>^$EVENT</code> SSVN is incomplete | * The <code>^$EVENT</code> SSVN is incomplete |
Revision as of 16:07, 4 August 2023
Contents
Conformance Policy
FreeM attempts to comply with ANSI X11.1-1995 and the unpublished Millennium Draft Standard (MDS) from the MUMPS Development Committee.
This article attempts to track missing and/or nonstandard features in the current main
branch of FreeM. It is a work-in-progress.
MERGE
MERGE
should be implemented asM[ERGE] postcond SP L mergeargument
, but is currently implemented asM[ERGE] postcond SP mergeargument
KVALUE/KSUBSCRIPTS
- Only the inclusive forms of these commands are currently implemented
Transaction Processing
- Restartable transactions are not complete
Event Processing
ETRIGGER
is not yet implemented- Of the event classes defined in the MDS, only the
INTERRUPT
evclass is implemented - The
TRIGGER
'evclass' is nonstandard - The
^$EVENT
SSVN is incomplete - Environment-wide events defined in
^$SYSTEM
are nonstandard
Globals
Routines
- Dotted routine names are nonstandard
Miscellaneous Language Features
ASSERT
is nonstandardWITH
andUSING
are nonstandardCONST
is nonstandardMAP
is nonstandard