Until a separate BNF or other suitable grammar is defined and gets
kyle agreement, I can't see the value of Antrl.

How do you know it's even capable of parsing JAL?

What will you do about name munging? Perhaps the rules of scope in C
and JAL are not the same (they should NOT be).  Will you prefix each
name automatically with it's parent scope?

Blocks create anonymous scope. You need a naming scheme for each block
scope. AFAIK C has no equivalent scope. There is NO problem exporting
EVERYTHING as global scope in C, as long as the names are adjusted
first and the C code is not for humans but only for a compiler.

What if Kyle adopts some of the current suggestions (that are easy to
implement and will work even on 10F) for Block scope enhancement?

The only thing though for certain I heard is "coming soon" though is
literal string constants in expressions/parameters rather than
needing a separate const statement.

I recommend at least reading
Writing Interactive Compilers and Interpreters  (P. Brown)
Programming :Language Translation (P D Terry)

Terry explains the limitations of direct decent and LL parsing

See also http://www.devincook.com/GOLDParser/about/why-use-gold.htm

However real computer scientists will point out that Preprocessing /
Translating to C was depreciated over 20 years ago.




-- 
You received this message because you are subscribed to the Google Groups 
"jallib" 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/jallib?hl=en.

Reply via email to