Re: [boost] [Review] xpressive

From: Scott Woods (scottw_at_[hidden])
Date: 2005-09-15 15:22:05

----- Original Message ----- 
From: "Eric Niebler" <eric_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Friday, September 16, 2005 5:10 AM
Subject: Re: [boost] [Review] xpressive

> > with STL, it's a wrinkle. Does processing of "what" always involve
> > "++what.begin()" only
> > because "what.complete()" fails to compete with tradition.
> 
> 
> I understand what you're saying, but I don't agree that it's that for 
> solely for legacy reasons. In practice, the only reason why you might 
> iterator over all sub-matches is to print them out. Otherwise, the 
> sub-matches are accessed randomly, because (for example) the 1st 
> sub-match is a date and the 3rd sub-match is an email address, and I'm 
> not interested in the 2nd. See?

For sure.

Interesting though; in the accesses listed you do not make
use of the zero'th element and yet they must all acknowledge its
presence.

Both approaches obviously work. I can only guess that recent
immersion in STL/concepts/boost has left me with some kind
of halo. Soon get rid of that! It's making me notice minutiae
such as non-zero-based use of a vector.

Xpressive is great (as are spirit and regex). The async I/O thing
was a tangent but hopefully useful beyond the acceptance of
your lib. Thanks to Chris and Felipe.

Cheers.