>Fabio/Craig,
>
>This request gets my vote as well.
>
>See also my related plea for a single, very tiny, non-invasive hook into the compilation cycle: "Sedna - Pre-processor hook for all compilation events"
>http://www.levelextreme.com/wconnect/wc.dll?LevelExtreme~2,41,17,1020557
>
>I agree with the goal - continue to open up VFP so the community can provide solutions that Microsoft can't or won't.
>
>This is a win for all parties.
>
>Malcolm

I Agree.

But I enhance to a New baseclass:
CompilerListener

This has sense because VFP also compiles to runtime.

With this the inside parser of VFP can be exploited
rather than to owe him to refer it.

In fact, the transformation of a report in
data+ReportMatadata => Language/Bitmap
it is semantically equal to the compilation.
GrammarDatabase + ProgramMetadata => BinaryCode.

Naturally someone will say that can be done
with ProjectHook.BeforeBuild.
But so all enough twisted becomes
when is wanted to also apply it to runtime
on the commands COMPILE and EXECSCRIPT ()

Hi