From: Stefan S. <se...@sy...> - 2004-04-07 02:35:06
|
Hi Grzegorz, Grzegorz Jakacki wrote: >>(I'm also getting a couple of failures in the test suite >> run on my RH9 machine where the parser has problems with >> GNU extensions (I believe), in this case the line is >> >> extern "C" __typeof(uselocale) __uselocale; >>) > > > This is high priority, however before I get down to it I need to separate > parser, because testing the whole monolith adds huge burden and slows down > anything I do to parser. I am working on the separation now. I just realize that the synopsis port of opencxx already contains a change to deal with this GNU extension. May be we should try to merge the appropriate parts back into 'mainline' ? Let me know if I can help... On an unrelated note: as you know I'm quite interested into the efford to separate the different opencxx layers. As I don't have any theoretical background in compiler / parser techniques, I'm wondering about the nature of all the ptree related business: As far as I understand only the very first steps are related to a parse tree proper. Already the construction of things like 'PtreeNamespaceAlias' nodes belongs into the 'syntax tree' domain, right ? I'm asking because I have some difficulties drawing a clear line as to what the AST I use in synopsis should look like. Right now I only manipulate declarations, but I can imagine at some point to be more flexible and provide scripting access to the parsed source code and thus similar to opencxx's goals provide some means to do meta programming. Any thoughts ? Regards, Stefan PS: for those who don't know what I'm talking about: http://synopsis.fresco.org |