Re: plugin compiler

Hi there,

I dropped the python plans and started to implement the plugin compiler 
using plain c++ with flex and bison for the parser.

This has the advantage of not introducing any additional dependences 
(the files generated from bison and flex can be checked into arch and 
can be added to the dist).

I want to divide the plugin compiler into two parts, one that generates 
(language independent) interface files, and one that generates the code 
needed for a particular language from those files (only C and C++ are 
planned for now).

The first part will be called pluc and the second idlc. I think pluc 
should call idlc (or there should be a wrapper script) to make it 
user-friendly for plugin developers.

Regards,

Georg