Re: [Boost-users] bug of boost algorithm library or boost asio?

Hi, I was able to reproduce the error with VS 2008 in both Win32 and x64 compilations. I think it boils down to the fact that the internal state of LINE_END_MARK is changed when LINE_END_MARK.end() is called (even though string::end() pretends to be const, but if you in the standard header "xutility" line 173 there is a C-style cast to get rid of the const). Tobias -- View this message in context: http://boost.2283326.n4.nabble.com/bug-of-boost-algorithm-library-or-boost-a... Sent from the Boost - Users mailing list archive at Nabble.com.