> I just noticed a *very* annoying difference between interpreter and
> compiler:
...
> is this known? difficult to fix?
Compiler and "interpreter" are in fact two different compilers. IMHO
the correct way to avoid differences is to use single compiler. This
will take time.
Currently I am working on replacing various parsers that we have
by a single one. During that I looked at keywords -- set of
keyword recognized by parsers differ a lot. There is a group
of common keyword but, but beyond that:
Shoe recoginizes 'cross', 'of', 'structure' as keywords, but other
parsers do not. Compiler parser recognizes 'otherwise', 'when',
'exquo', 'div', 'suchthat', 'yield', 'leave', 'not', 'unless',
'until' as keywords, but the "interpreter" parser do not.
"Interpreter" parser treats 'break', 'default', 'define', 'do', 'export',
'free', 'inline', 'local', 'macro', 'rule' as keywords, but
the compiler parser do not.
Some changes are kind of obvious: compiler probably should treat
all words that are keywords for "interpreter" as keywords. We
should probably migrate from 'leave' to 'break'. But other
are less clear: I personally would add 'exquo' as keyword
(operator) also to "interpreter", but Martin seems to be
against this (my rationalle is that 'exquo' and 'quo' are
used in similar context, it is silly to have change betwieen
infix and prefix version when changing one to the other).
'div' is used very little, so we could probably drop it.
'otherwise', 'when', 'suchthat', 'yield', 'unless' are
unused so in principle we could drop them. But it makes
sense to reserve 'yield' for possible future use in
Aldor-like generators.
--
Waldek Hebisch
[email protected]
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
