History: BPFK Section: MEX

Preview of version: 30

Proposed Definitions And Examples

cmavo: bi'e (BIhE)

Proposed Definition

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.

Proposed Keywords

  • High priority operator
  • Precedence operator

Usage Examples

li ci su'i vo bi'e pi'i mu du li reci
3 + (4 × 5) = 23

Notes

This is distinct from the use of mathematical brackets {vei} and {ve'o}.






cmavo: fu'a (FUhA)

Proposed Definition

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).

Proposed Keywords

  • Reverse Polish Flag

See also

  • {pe'o} Forethought operator flag
  • {tu'o} Null operand
  • {ge'a} Null operator

Usage Examples

li fu'a reboi ci su'i du li mu
(RP) (2 3 +) = 5
li fu'a reboi ci pi'i voboi mu pi'i su'i du li rexa
(RP) (2 3 x) (4 5 x) + = 26
li fu'a ciboi muboi vu'u du li fu'a reboi tu'o va'a
(RP) (3 5 -) = (RP) (2 null) negative
li cinoki'oki'o du li fu'a biboi ciboi panoboi ge'a gei
30,000,000 = (RP) 8 (3 10 null) exp

Issues

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 to usage, it lacks symmetry with forethought equivalent and seems contrived. Perhaps {ku'e} could have its use extended from separating groups of operands in forethought mode to doing it in RP mode too.

Example li fu'a paboi ku'e biboi ciboi panoboi gei su'i du li cinoki'oki'opa
(RP) 1 (8 3 10 exp) + = 30,000,001







cmavo: jo'i (JOhI)

Proposed Definition

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.

Proposed Keywords

  • Vector flag

See also

  • {te'u} Mekso terminator for NAhU, NIhE, MOhE, MAhO, and JOhI

Usage Examples

li jo'i paboi reboi te'u su'i jo'i ciboi voboi du li jo'i voboi xaboi
vector (1, 2) + vector (3, 4) = vector (4, 6)

Notes

It is the only member of selma'o JOhI






cmavo: ku'e (KUhE)

Proposed Definition

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.

Proposed Keywords

  • Forethought operand terminator

See Also

  • {pe'o} Forethought operator flag

Usage Examples

li py. su'i va'a ny. ku'e su'i zy du li xy.
p + (negative n) + z = x







cmavo: ma'o (MAhO)


This flag converts letteral string or other mathematical expression (mex) operand into a mex operator. Its elidable terminator is {te'u}.

Proposed Keywords

  • Operand to Operator flag

Usage Examples

li zy du li ma'o fy.boi xy.
z = f(x)

Notes

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.






Proposed Definition of mo'e

mo'e (MOhE)
sumti to operand — convert sumti to mex operand; sample use in story arithmetic: 3 apples + 3 apples = what --
    • Keywords:

Examples of mo'e Usage







Proposed Definition of na'u

na'u (NAhU)
selbri to operator — convert selbri to mex operator; used to create less-used operators using le'avla, lujvo, etc. --
    • Keywords:

Examples of na'u Usage







Proposed Definition of ni'e

ni'e (NIhE)
selbri to operand — convert selbri to mex operand; used to create new non-numerical quantifiers; e.g. "herd" of oxen --
    • Keywords:

Examples of ni'e Usage







Proposed Definition of nu'a

nu'a (NUhA)
operator to selbri — convert mathematical expression (mex) operator to a selbri/tanru component --
    • Keywords:

Examples of nu'a Usage







Proposed Definition of pe'o

pe'o (PEhO)
fore mex operator — forethought flag for mathematical expression (mex) Polish (forethought) operator --
    • Keywords:

Examples of pe'o Usage







Proposed Definition of te'u

te'u (TEhU)
end mex converters — elidable terminator: end conversion between non-mex and mex; usually elidable --
    • Keywords:

Examples of te'u Usage







Proposed Definition of vei

vei (VEI)
left bracket — left (opening) mathematical bracket/parenthesis --
    • Keywords: open paren (programming lingo version)

Examples of vei Usage

  • li ny. du li ni'igi vei re su'i re {ve'o} gi vo
  • vei ci .a vo {ve'o} prenu cu klama le zarci
  • vei ga ci gi vo {ve'o} prenu cu klama le zarci







Proposed Definition of ve'o

ve'o (VEhO)
right bracket — right (closing) mathematical bracket/parenthesis --
    • Keywords: close paren (programming lingo version)

Examples of ve'o Usage

  • li te'o te'a {vei} pai pi'i ka'o ve'o su'i pa du li no
  • li ma'o i bu boi te'u {vei} xy pi'i ny ve'o ku'e na'u du de'o re vei ny te'a ci
  • fy du li cire su'i {vei} cy pi'i so fi'u mu ve'o

Notes

  • ve'o is an elidable terminator
  • vei and ve'o are necessary for any non-simple mekso used as a quantifier

Impact



History

Advanced
Information Version
Thu 13 of May, 2010 00:36 GMT RossOgilvie from 172.21.94.170 34
Sun 18 of Apr, 2010 14:28 GMT RossOgilvie from 220.239.170.184 33
Sun 18 of Apr, 2010 14:12 GMT RossOgilvie from 220.239.170.184 32
Sun 18 of Apr, 2010 14:10 GMT RossOgilvie from 220.239.170.184 31
Sun 18 of Apr, 2010 14:08 GMT RossOgilvie from 220.239.170.184 30
Sun 18 of Apr, 2010 13:57 GMT RossOgilvie from 220.239.170.184 29
Sun 18 of Apr, 2010 13:53 GMT RossOgilvie from 220.239.170.184 28
Sun 18 of Apr, 2010 13:51 GMT RossOgilvie from 220.239.170.184 27
Sun 18 of Apr, 2010 13:39 GMT RossOgilvie from 220.239.170.184 26
Sun 18 of Apr, 2010 12:55 GMT RossOgilvie from 220.239.170.184 25
Sun 18 of Apr, 2010 12:43 GMT RossOgilvie from 220.239.170.184 24
Sun 18 of Apr, 2010 12:41 GMT RossOgilvie from 220.239.170.184 23
Sat 17 of Apr, 2010 10:15 GMT RossOgilvie from 124.170.134.97 22
Fri 16 of Apr, 2010 15:18 GMT RossOgilvie from 220.239.170.184 21
Fri 16 of Apr, 2010 15:02 GMT RossOgilvie from 220.239.170.184 20
Fri 16 of Apr, 2010 14:50 GMT RossOgilvie from 220.239.170.184 19
Fri 16 of Apr, 2010 14:33 GMT RossOgilvie from 220.239.170.184 18
Fri 16 of Apr, 2010 14:33 GMT RossOgilvie from 220.239.170.184 17
Fri 16 of Apr, 2010 14:31 GMT RossOgilvie from 220.239.170.184 16
Fri 16 of Apr, 2010 14:05 GMT RossOgilvie from 220.239.170.184 15
Fri 16 of Apr, 2010 14:00 GMT RossOgilvie from 220.239.170.184 14
Fri 16 of Apr, 2010 01:55 GMT RossOgilvie from 172.21.91.165 13
Fri 16 of Apr, 2010 01:54 GMT RossOgilvie from 172.21.91.165 12
Fri 16 of Apr, 2010 01:53 GMT RossOgilvie from 172.21.91.165 11
Fri 16 of Apr, 2010 01:49 GMT RossOgilvie from 172.21.91.165 10
Fri 16 of Apr, 2010 01:45 GMT RossOgilvie from 172.21.91.165 working on bi'e 8
Fri 16 of Apr, 2010 01:32 GMT RossOgilvie from 172.21.91.165 7
Thu 15 of Apr, 2010 18:13 GMT seryf from 76.8.216.14 6
Thu 15 of Apr, 2010 18:12 GMT seryf from 76.8.216.14 5
Thu 15 of Apr, 2010 17:32 GMT seryf from 76.8.216.14 4
Thu 15 of Apr, 2010 07:05 GMT seryf from 76.8.216.14 3
Thu 15 of Apr, 2010 07:03 GMT seryf from 76.8.216.14 2
Wed 17 of Nov, 2004 02:43 GMT rlpowell from 64.81.49.171 1
  • 1
  • 2 (current)
  • »