spirit docs (was regex ease-of-use)
Subject: Re: [boost] Re: Regex ease-of-use ideas
Hmmph. I have to say that while I love what Spirit is doing, actually using it with confidence requires way too much use of the source, Luke. Reference docs are annoying to write, but neccessary.
Point well taken. Formal documentation is high on the TODO list.
It'd also be great to have documentation on what would need to be changed to Spirit to enable full backtracking and cut points. Dave
Dave Gomboc wrote:
It'd also be great to have documentation on what would need to be changed to Spirit to enable full backtracking and cut points.
Not sure what you mean by cut points, but if you are looking for a Spirit-like regex engine that does full backtracking, I'm building one. It's in boost-sandbox, and it's quite usable. Look for xpressive. No docs yet, sorry. -- Eric Niebler Boost Consulting www.boost-consulting.com
Eric Niebler wrote:
Dave Gomboc wrote:
It'd also be great to have documentation on what would need to be changed to Spirit to enable full backtracking and cut points.
Not sure what you mean by cut points, but if you are looking for a Spirit-like regex engine that does full backtracking, I'm building one. It's in boost-sandbox, and it's quite usable. Look for xpressive. No docs yet, sorry.
Not to mention that Eric, Hartmut and I are collaborating on making Eric's ideas available in Spirit. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
participants (3)
-
Dave Gomboc -
Eric Niebler -
Joel de Guzman