----- Original Message ----- 
From: "Vincent Finn" <[EMAIL PROTECTED]>


> I had a look at the mailing list but it comes up as read-only for me for 
> some reason?
> I am logged in to Source Forge but haven't used it much
> 
> as for the news group I subscribed to it (it appears in the list of 
> available news groups) but when I try to access it I'm told it doesn't 
> exist on the server ??

Hmmm... I'm not sure why.

> >>>I have added 2 parsers to my code base and the compile time (VC6) has
> >>>gone from 10 mins to 30mins :-(
> >>
> > Yes, this is the next battle. How big are your grammars? How many productions?
> > Are you using subrules? Better yet, can I see your code?
> 
> I can send a stripped down code (it'll take a while to put it together 
> so it'll be next week some time)
> 3 question on that
> 1) Would you prefer a direct mail with it or an atachment to the NG?
> 2) Do you need tgz or is zip fine?
> 3) Is a VC project file fine to show the compile setting I am using?

Sure. No problem. A VC project file is Ok and zip is just fine.

> This is another developers code but I made the call to use Spirit so I 
> have to do the optimising !
> so please bear with me if it takes a while for me to split it off :(

I'd appreciate that a lot. This will help me fine tune Spirit and
will be very useful in targetting the points where optimization
is needed.

> > At the very least, yes, you can separate the parsers from the project.
> > How about writing some wrappers that *hides* the grammars in
> > *.cpp files? You can for example have an opaque API in a header
> > such as:
> > 
> >     bool parse(char const* source);
> 
> That seems obvious now that you say it
> I was thinking in terms of spliting spirit off which causes problems but 
> , as you say, all I need is to build a lib with my parser in so that 
> spirit is hidden.
> 
> Thanks for the quick response, Vin

Most welcome!

Regards,
Joel de Guzman
[EMAIL PROTECTED]
http://www.boost-consulting.com


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Reply via email to