Hi Guys, @JAT - just checked to see how comment is handled. The grammar file removes all comment (to the hidden channel - not sure if there is a trick access this anyway) except the ones needed for the translator. It should be easy to derive a grammar file that includes all comment as tokens in the source tree. And I can't recall there are many issues remaining with the grammar file, so this should be a pretty robust parser that could dump the output for further processing.
Having said that, there are a few issues to consider: - this would require a substantial change to the document generation code. - For me it took quite some effort to get up to speed with the grammar stuff and this speed is gone now. So any additional changes to the ones mentions or bugs will take substantial effort. - The parses put limitations on the grammar that JAL does not always obey. Until now I could create a work-around for each issue found, but we could get bitten seriously. Joep -- 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.
