John Maddock wrote:
I'm just clueless :-) Perhaps you can investigate? The problem happens
on GCC from Cygwin.
I believe there is a problem with std::getline which results in the line
ending with a \r on cygwin. There are probably other related errors as
well.
Wouldn't the most robust solution be to open the file in binary mode and
treat any of:
\n
\r\n
\r
\n\r
as line separators? Quickbook would then work irrespective of the text
file's provenance.
Of course this is all a theoretically needless complication ;-)
This is actually how QuickBook was designed-- at least in theory.
Spirit's eol parser can handle those \r\n combinations. I'll still
have to figure out however why it's not doing what it's supposed
to do. I'll try to isolate the problem.
Cheers,
--
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
