Difference between revisions of "Conformance Clause"

From FreeM Wiki
Jump to navigation Jump to search
 
Line 5: Line 5:
 
Routine buffers in <code>FREEM</code> dialect enable all nonstandard extensions.
 
Routine buffers in <code>FREEM</code> dialect enable all nonstandard extensions.
  
This article attempts to track missing and/or nonstandard features in FreeM. It is a work-in-progress.
+
This article has been superseded by <code>freem_conformance(1)</code> in the UNIX manual.
 
 
== Aliases ==
 
 
 
FreeM supports aliases for local variables that can reference either the root node or a subtree:
 
 
 
<pre>
 
USER> S X(3)="harps"
 
 
 
USER> S J=.X(3)
 
 
 
USER> S J(8)=17
 
 
 
USER> ZWR X
 
X(3)=harps
 
X(3,8)=17
 
</pre>
 
 
 
Aliases used in pass-by-reference can also reference entire subtrees instead of just the root node:
 
 
 
<pre>
 
USER> ZL TEST
 
 
 
USER> ZP
 
 
 
TEST ;
 
S X(3)=4
 
D SUBR(.X(3))
 
ZWR X
 
QUIT
 
;
 
SUBR(A) ;
 
S A(4)="thwack!"
 
QUIT
 
 
 
USER> D ^TEST
 
X(3)=4
 
X(3,4)=thwack!
 
</pre>
 
 
 
== Environments ==
 
 
 
In FreeM, the ''namespace'' is roughly equivalent to what the standard refers to as an ''environment''. However, FreeM uses the term ''environment'' to refer to a collection of namespaces and processes.
 
 
 
== Indirection ==
 
 
 
FreeM supports several forms of indirection that are nonstandard, as well as allowing indirection in several constructs where the standard prohibits it. Below is a list of some known instances of idiosyncratic indirection; please note that this list is by no means comprehensive:
 
 
 
* <code>FOR</code> loops in FreeM support argument indirection
 
* FreeM supports list indirection, such as <code>S X="1,2,3",ARGS="X,"","",2" W $P(@ARGS)</code>, which will output <code>2</code>
 
 
 
== MERGE ==
 
 
 
* <code>MERGE</code> should be implemented as <code>M[ERGE] postcond SP L mergeargument</code>, but is currently implemented as <code>M[ERGE] postcond SP mergeargument</code>
 
 
 
== KVALUE/KSUBSCRIPTS ==
 
 
 
* Only the inclusive forms of these commands are currently implemented
 
 
 
== Transaction Processing ==
 
 
 
* Restartable transactions are not complete
 
 
 
== Event Processing ==
 
 
 
* <code>ETRIGGER</code> is not yet 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>^$EVENT</code> SSVN is incomplete
 
* Environment-wide events defined in <code>^$SYSTEM</code> are nonstandard
 
 
 
== Globals ==
 
 
 
== Routines ==
 
* Dotted routine names are nonstandard
 
 
 
== Locking ==
 
* The first subscript of ^$LOCK collates according to the rules for global and local subscripts, not as an nref, as FreeM uses globals as backing store for SSVNs. If someone wants to write the code to make this conformant, the maintainer will accept it.
 
 
 
''The reason is that FreeM treats the <code>^$LOCK</code> subscript as a single, normal ASCII string, and has no concept of subscripts existing within it, so canonical numbers don't really sort correctly.'' - Serena
 
 
 
== Miscellaneous Language Features ==
 
* <code>ASSERT</code> is nonstandard
 
* <code>WITH</code> and <code>USING</code> are nonstandard
 
* <code>CONST</code> is nonstandard
 
* <code>MAP</code> is nonstandard
 
* <code>WATCH</code> is nonstandard
 
* <code>THROW</code> is nonstandard
 
* <code>$DIALECT</code> is nonstandard
 

Latest revision as of 22:50, 4 May 2025

Conformance Policy

FreeM attempts to comply with ANSI X11.1-1995 and the unpublished Millennium Draft Standard (MDS) from the M Development Committee, in routine buffers where the dialect setting is set to a particular version of the standard.

Routine buffers in FREEM dialect enable all nonstandard extensions.

This article has been superseded by freem_conformance(1) in the UNIX manual.