compiling E: Phases of Transformations

[Monty Zukowski]

>>Actually something like #line would be very useful for parser generators as
>>well.  GCC's #line directive allows nesting so you can see the whole stack of
>>files which included other files, etc.
>>
>>Something like:
>>
>>Syntax Error at someheader.h:12
>>     included in main.c:8 ...

>I don't have anything like textual file inclusion, so I don't think I have
>*this kind* of nesting.

What about when you call antlr for quasi-parsers, or what about being able to
debug each stage of your transformations?  You know you will want to look at the
output of a particular pass to debug it, and you will want a way to identify the
line in that particular pass based on the kernel-E.

It could be external to the source, but needs to be thought about.

Monty