Indicates an operator has precedence over unmarked operators. When an operator is prefixed with this cmavo, it becomes automatically of higher precedence than other operators not so prefixed. If more than one operator has a bi'e prefix, grouping is to the right; multiple bi'e prefixes on a single operator are not allowed.
This is distinct from the use of mathematical brackets {vei} and {ve'o}.
Xorxes has a plan to replace this by expanding the use of {bo}
Marks the mekso expression as using Reverse Polish (RP) notation. RP notation is always marked by an explicit fu'a at the beginning of the expression. Operators acting in RP are required to have two operands (though {tu'o} and {ge'a} can assist when using unitary and ternary operators respectively).
(natural example: doi jbokaj li fu'a pa boi re su'i ci su'i)
It seems quite arbitrary that operators acting in reverse polish notation are required to have exactly 2 operands. Especially considering that in polish notation, operators are allowed to have as many operands as they like. It does not make semantic sense for all operators (for example the negation operator, used in the example usage above). Though there is a problem in determining which operands belong to which operator, and the solution currently is quite elegant for usage, it lacks symmetry with forethought equivalent and seems arbitrary.
Joins a sequence of simple operands or bracketed full expressions into a vector. A vector may have any number of components. It's corresponding terminator {te'u} is elidable.
It is the only member of selma'o JOhI
This is the elidable terminator of operators when they are acting in forethought mode. It serves to distinguish where the operands of one operator end and another begin.
This flag converts letteral string or other mathematical expression (mex) operand into a mex operator. Its elidable terminator is {te'u}.
The CLL has the following observation: There is a potential semantic ambiguity in ma'o fy. [te'u] if fy. is already in use as a variable: it comes to mean "the function whose value is always 'f' ". However, mathematicians do not normally use the same lerfu words or strings as both functions and variables, so this case should not arise in practice.
Converts a sumti to a mex operand. Intended to allow dimensions to be embedding into mex expressions. It is also used for "folk quantifiers", also known as collective nouns. It precedes the sumti. Its elidible terminator is {te'u}.
The cmavo "na'u" makes a selbri into an operator. In general, the first place of the selbri specifies the result of the operator, and the other unfilled places specify the operands. Its elidible terminator is {te'u}. It is also used to construct questions about operators.
'
This comment applies exclusively to CLL example 18.18.1. I'm not sure if it therefore belongs here. The CLL example of this seems to be needlessly complicated (using the value of pi/2 where the function is undefined). I've changed the example here slightly to avoid any disputes about validity.
The cmavo "ni'e" makes a selbri into an operand. The x1 place of the selbri generally represents a number, and therefore is often a ``ni'' abstraction. The "ni'e" makes that number available as a mekso operand. A common application is to make equations relating pure dimensions.
The cmavo "nu'a" is the inverse of {na'u}, and allows a mekso operator to be used as a normal selbri, with the first place being the result of applying the operator to the other places.
It's been pointed out by Xorxes that {me} could be expanded to do this. {nu'a} could be moved to ME for backwards compatibility. It has had (almost) no usage in the wild (corpora + mailing list) (literally 6 mentions on IRC). But it does have a nice symmetry with na'u
The optional flag that indicates a forethought mekso operator. Forethought mode is also known as Polish notation. When used in conjunction with {ku'e}, it acts like brackets around the function and its arguments.
When using forethought mekso, be sure that the operands really are operands: they cannot contain regular infix expressions unless parenthesized with {vei} and {ve'o}. Eg li + 2 x 3 4 parses as 2 + ( 3 x 4 ) and not ( 2 x 3 ) + 4.
This, like {sei}, attaches a commentary about the text. The purpose of this is to define a heirarchy of precedence for mex operators.
The format of a {ti'o} declaration has not been formally established, but presumably would take the form of mentioning a mekso operator and then giving it either an absolute numerical precedence on some pre-established scale, or else specifying relative precedences between new operators and existing operators. Typically only operators of selma'o VUhU would be given higher precedence, whereas operators created with {na'u}, {ni'e} or {ma'o} would remain at the lowest level of precedence.
If such a system was created, there would most likely be a predefined set of precedence levels that would match common mathematics conventions and which could easily be referenced. In such a system one would expect that multiplication would be of higher precedence than addition
This isn't really a definition; more a suggestion of what the intention of this cmavo should be. A good system needs to be worked out. I could find no mention of it in the mailing list.
An elidable terminator for several mex related {selma'o}, namely NAhU, NIhE, MOhE, MAhO, and JOhI. These {selma'o} are generally conversion tags.
This is the mathematical left bracket. Used to group mex expressions. For example, brackets are used to turn a mex expression into an operand for use by a forethought operator, or to place a mex expression in a subscript. The right bracket {ve'o} is elidable. {vei} and {ve'o} are necessary for any non-simple mekso used as a quantifier.
This is the mathematical right bracket. Used to group mex expressions. For example, brackets are used to turn a mex expression into an operand for use by a forethought operator, or to place a mex expression in a subscript. As a terminator, it is elidable. The corresponding left bracket is {vei}. {vei} and {ve'o} are necessary for any non-simple mekso used as a quantifier.
The write up above pretty much follows the CLL. However there has been at least one proposal (and I suspect there might be others) to reform the mex grammar to simplify it, mostly by merging selma'o. I myself am unhappy by the complexity of mex; specifically the limitations of {fu'a}, and the current uses of {tu'o} and {ge'a} (as noted above).
Also, the definition of {ti'o} is almost apologetic in its uselessness. As the CLL suggests, a working party needs to hammer out a standardised format for {ti'o}, put together a common convention precedence list for VUhU and publish it for reference. (In fact if such a list were published, then perhaps it should apply by default. The CLL suggests that the common convention for order of operations applies in mex already, and that would provide a sound way to implement this)
There is little impact from this, as mex is so underused. The only substantial work involving mex that I could find was
Fundamental Concepts Of Higher Algebra, by Nick Nicholas. Regardless, there is no recommendation to change the CLL definitions.