Aleksey Gurtovoy <agurtovoy@meta-comm.com> writes:
David Abrahams writes:
Thorsten Ottosen <nesotto@cs.aau.dk> writes:
Also, IIUC, this and other mentions of null terminated strings need to be removed now.
yes, when I get the time or when somebody volunteers (1.33 is out of the question).
If the code has changed, you have to change the docs before 1.33. Otherwise, you have to do the change after 1.33. I assumed that the former was the case.
the former is the case.
Does everybody think it's okay to release 1.33 docs with the false promise that Boost.Range includes special null-terminated string support? That seems very wrong to me, and so avoidable!
Seems very wrong to me as well, especially since the fix could be as easy as including a prominent one-sentence warning on the library's main page.
I'm a little confused now. According to what Thorsten wrote above, the code has changed so that null-terminated strings no longer get special treatment. However, according to what he wrote to me in private email, making the suggested change to the docs would make them inconsistent with the code. So I think he must've been confused above. IIUC he is planning to put a deprecation warning in the docs for 1.33.0 so that in 1.34.0 we can change the behavior. -- Dave Abrahams Boost Consulting www.boost-consulting.com