https://svn.boost.org/trac10/ticket/971 <p> A significant number of changes were made to the boost.iostreams library on the RC_1_33_0 branch, but never merged into the trunk. </p> <p> There are also a few changes on the RC_1_34_0 branch that have not been merged to into the trunk. </p> <p> There has also been some work on the trunk, some of which is on one of those branches, a few cases of merges between one of those branches and the trunk, and I found at least one case of apparent merging with code rearrangement or other changes (at least, diff seemed to not match up the (similar by eye) changes). </p> <p> So basically there is a bit of a mess in the iostreams library. Here's what I think needs to happen: </p> <ul><li>changes that are presently only on the RC_1_33_0 or RC_1_34_0 branch should be merged to trunk </li></ul><ul><li>changes that are presently only on the RC_1_33_0 branch should be merged to the RC_1_34_0 branch. </li></ul><p> Attached is a gzip'ed tar file containing two patches, one for trunk and one for the RC_1_34_0 branch. </p> <ul><li>kab-iostreams-trunk.patch: This patch merges changes to the iostreams library from the RC_1_33_0 and the RC_1_34_0 branches to the trunk. It was generated relative to a cvs checkout of trunk at date -D 2007.05.14.22.34.09. </li></ul><ul><li>kab-iostreams-RC_1_34_0.patch: This patch brings the iostreams library to the same state as trunk + the above patch to trunk. It was generated relative to a cvs checkout of tag Version_1_34_0. </li></ul><p> These patches are both made relative to the boost root directory. To apply, cd to the root directory of the copy to be patched and </p> <blockquote> <p> patch -p1 &lt; &lt;path/to/patch&gt; </p> </blockquote> <p> The kab-iostreams-RC_1_34_0.patch has been tested on the following platforms by myself (linux) or John Maddock (other), with the indicated results: </p> <ul><li>linux-x86-gcc_4_1: debug mode: no failures in iostreams tests </li><li>linux-x86-gcc_4_1: release mode: no failures in iostreams tests </li><li>linux-ppc-gcc_3_4_4: debug mode: no failures in iostreams tests </li><li>msvc6, msvc7.0: one failure in iostreams tests, marked expected for RC_1_34_0 </li><li>msvc-7.1, msvc-8: no failures in iostreams tests </li><li>intel-8.1, intel-9: no failures in iostreams tests </li><li>gcc-3.4-cygwin: 3 failures in iostreams tests, all marked expected for RC_1_34_0 </li><li>borland-5.8.2: 1 failure in iostreams tests, marked expected for RC_1_34_0 </li><li>borland-5.6.4: 2 failures in iostreams tests, not a release compiler for RC_1_34_0, one failure marked expected in newer borland-5.8.2 compiler </li></ul><p> I've done some spot-checking of the documentation changes and haven't found any problems. </p> <p> The trunk patch has not bee tested, beyond verifying that the iostreams library is in the same state for sandboxes on trunk and the RC_1_34_0 branch after application of the appropriate patch. Since testing resources have been focused on the release branch for a while, I have no idea what state trunk might be in; for all I know, trunk doesn't actually build at the moment. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/971 Trac 1.4.3 Kim Barrett <kab@…> Fri, 18 May 2007 15:11:52 GMT https://svn.boost.org/trac10/ticket/971 https://svn.boost.org/trac10/ticket/971 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">kab-iostreams-patches.tgz</span> </li> </ul> Ticket Kim Barrett <kab@…> Fri, 18 May 2007 16:07:52 GMT https://svn.boost.org/trac10/ticket/971#comment:3 https://svn.boost.org/trac10/ticket/971#comment:3 <ul> <li><strong>version</strong> → <span class="trac-field-new">release 1.34.0</span> </li> </ul> Ticket Thomas Witt Tue, 22 May 2007 03:58:55 GMT https://svn.boost.org/trac10/ticket/971#comment:4 https://svn.boost.org/trac10/ticket/971#comment:4 <ul> <li><strong>milestone</strong> → <span class="trac-field-new">Boost 1.34.1</span> </li> </ul> Ticket John Maddock Wed, 23 May 2007 08:32:25 GMT https://svn.boost.org/trac10/ticket/971#comment:5 https://svn.boost.org/trac10/ticket/971#comment:5 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket