@podperson: " just as most experienced programmers would prefer having to type explicit variable declarations over having to debug subtley mispelled variable names that don't throw compile errors (now there's a feature of C, or any number of languages, that BlitzBasic needs). " == Thats what I was refering to when I mentioned WAY BACK needing a full LALR parser -- adding strong typing and not having to specify type as var.type for typed variables :) But then you need to keep a symbol table and track scope during translation.
once you go that far, you could take the YACC spec for any language and fairly easily write a translator to BB :)
@Kram: I dont expect you to go that far.. I've been programming 30 years and have written a couple of translators.. one YACC based... and it can be quite a headache.... however, if you are that crazy:
java: http://www.devincook.com/goldparser/download/grammar/Java-Dmitry-Gazko.zip
VB.Net: http://www.devincook.com/goldparser/download/grammar/visual-basic.net.zip
both use the GOLD parser engine: http://www.devincook.com/goldparser/index.htm
which is available in many languages, or as DLL or .Net assembly :)
once you go that far, you could take the YACC spec for any language and fairly easily write a translator to BB :)
@Kram: I dont expect you to go that far.. I've been programming 30 years and have written a couple of translators.. one YACC based... and it can be quite a headache.... however, if you are that crazy:
java: http://www.devincook.com/goldparser/download/grammar/Java-Dmitry-Gazko.zip
VB.Net: http://www.devincook.com/goldparser/download/grammar/visual-basic.net.zip
both use the GOLD parser engine: http://www.devincook.com/goldparser/index.htm
which is available in many languages, or as DLL or .Net assembly :)