Re: segmented fusion - a-ha!

Eric Niebler wrote:
> Since a generic segmented iterator would need to remember parents, it 
> won't be as light-weight as it could be. But I don't think this is a 
> very common usage pattern in Fusion. (Is it, Joel?) I've never needed 
> fusion::range<>. Better to optimize for the common case, IMO.

No, it is not.

> I admit, it's all pretty hand-wavey at this point. It would be wise to 
> begin our investigation of this approach there.

Yes. At least, I can say that I am happy with the current start
Eric has on this. For me, as far as Spirit-2 is concerned, being
able to work efficiently and in a straight-forward manner with
the algorithms is of utmost importance. Simplicity matters, because
I would like the users to fully grasp how the parsers themselves
work, the algorithms involved, etc., as much as I would like them
to write their own parsers from the building blocks.

That is, I would say, the spirit of spirit; characterized by
the quote from Bjarne:

"Examples of designs that meet most of the criteria for
"goodness" (easy to understand, flexible, efficient) are a
recursive descent parser, which is traditional procedural code.
Another example is the STL, which is a generic library of
containers and algorithms depending crucially on both
traditional procedural code and on parametric polymorphism."

Regards,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642