Hi Matt, On May 17, 11:32 pm, mattschinkel <[email protected]> wrote: > > I see Antlr outputs a .c file (a runable program). Is that what JAT > is, just an output from Antlr? Did you compile the .c file into > jalparser.exe? >
I'm writing this from memory -- please read Joep's DOCX documentation file for exact / up-to-date information. Take a look at the various JAT-related files in SVN, especially those that seem to be 'makefile' or 'batch file' looking. Joep did the windows build/make files, and he uses Perl for some of it. I provided the makefile for Ubuntu, but it is possible that it is not quite as up-to-date as Joep's windows version. > Does modifying JAT only require knowledge of Antlr? Hardly. Antlr is a modern compiler-compiler tool. But there is much more work involved that must be done manually. That is why jat/source has 3000+ lines of C code (nearly all of which was written by Joep), which you'll need to understand as well. Perhaps the most important knowledge will be how JAL itself works -- parameter passing, etc. JAL isn't C, and C isn't JAL, but both are powerful yet different. > > Of course I need to know C so I can verify the final output. > Yes, and if you're wondering what sub-set of JAL is currently supported, then study the JAL test-cases in sources/tests. While there is a large fraction of JAL already supported, I'd warn you that if you don't see a test-case for a particular feature, it either doesn't exist or it has bugs. Try writing more test-cases for the missing feature, and see what happens, then try and fix them in JAT, without breaking any of the other test-cases. Rinse and Repeat... William -- 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.
