The problem here is not so much one of parsing, but one of storing. Haskell has great support for discriminated unions. In C++, that support is there, but at considerably greater syntactical expense.
The problem here is not so much one of parsing, but one of storing. Haskell has great support for discriminated unions. In C++, that support is there, but at considerably greater syntactical expense.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
O_o
Will '*anychar_p' not just eat everything? Shouldn't it at least be '*(anychar_p - '=')'?
I haven't used Boost::Spirit in a while; I may be wrong.
Soma
I'm definitely going to have to take a look at this in my 'copious' spare time. I've got the libraries and documentation downloaded somewhere......
I've been programming in Haskell for a while, in part due to the hype. The fact is, it isn't that much more productive than C++ for the kind of stuff I do and somewhat less so due to the fact that the library support is not as great. C++ has a larger base and has been active for longer.
It's just too bad Python is so darn slow for number crunching (though numpy can be faster than Matlab I'm told).
No -- remember that spirit has a "skip parser" which discards whitespace by default. To force anychar_p to actually "eat everything" you would specify:Originally Posted by phantomotap
Code:lexeme_d[*anychar_p]
I was referring to cases such as one other post offered-namely 'var1=3.3' or similar.
Soma
Well, the grammar was never formally defined, so who knows.
