Re: Tools to "prettify" source code

"Ira D. Baxter" wrote:
>
> Our DMS Reengineering Toolkit parses arbitrary langauges ("domains"),
> builds ASTs (capturing all the lexical source information such as
> comments, number formats, etc.), can apply source-to-source
> transformations to the trees, and finally prettyprint the result.
> This is driven by a "domain definition" including a grammar and
> prettyprinting rules.


What approach(es) do you take towards comments? Many comment forms seem
to cause problems with pretty printing. For example


        if (expr) { /* first line of */
                doSomething(); /* of a multi-line comment */
        } /* split across multiple lines */


is this one comment or three? Which parse nodes is/are the comment/s
attached to?


Many Smalltalks have a pretty printer but I've yet to see one that
handled comments well.
--
_______________,,,^..^,,,____________________________
Eliot Miranda Smalltalk - Scene not herd

Return to the comp.compilers page.
Search the comp.compilers archives again.