"eg"
Thomas Witt wrote:
Is there something amiss with the process when a fix that was in the releas for 1_33_1 (from september 2005) doesn't get into 1_34_0?
Flat out yes. For starters the iostreams maintainer is MIA.
[snip]
I wasnt the original reporter of this but I have filed this in the tracker:
Ticket #953
Thomas, I think the issue is much larger than just an outdated zlib.hpp... I just did a simple comparison between the 1.33.1 and 1.34.0 versions of the iostream library source files. (1.33.1 files from a zip when 1.33.1 was first released; 1.34.0 files from zip pulled down this morning.) There are several cases where the files in 1.33.1 are **newer** than the ones in 1.34.0... in many cases by several months: File | 1.33.1 Date | 1.34.0 Date iostreams/checked_operations.hpp | 11/15/2005 | 5/19/2005 iostreams/code_converter.hpp | 11/15/2005 | 6/3/2005 iostreams/compose.hpp | 11/15/2005 | 5/30/2005 iostreams/restrict.hpp | 11/15/2005 | 5/26/2005 iostreams/detail/resolve.hpp | 10/8/2005 | 5/21/2005 iostreams/detail/adapter/concept_adapter.hpp | 11/15/2005 | 5/19/2005 iostreams/detail/adapter/direct_adapter.hpp | 11/15/2005 | 5/19/2005 iostreams/detail/adapter/mode_adapter.hpp | 11/15/2005 | 5/19/2005 iostreams/detail/adapter/non_blocking_adapter.hpp | 11/15/2005 | 5/19/2005 iostreams/detail/adapter/range_adapter.hpp | 11/15/2005 | 5/19/2005 iostreams/detail/streambuf/direct_streambuf.hpp | 11/10/2005 | 7/15/2005 iostreams/device/file.hpp | 11/14/2005 | 8/24/2005 iostreams/device/file_descriptor.hpp | 11/15/2005 | 8/24/2005 iostreams/device/mapped_file.hpp | 11/28/2005 | 5/30/2005 iostreams/device/null.hpp | 11/15/2005 | 5/19/2005 iostreams/filter/aggregate.hpp | 8/29/2005 | 7/15/2005 iostreams/filter/gzip.hpp | 11/14/2005 | 6/8/2005 iostreams/filter/line.hpp | 8/29/2005 | 7/15/2005 iostreams/filter/zlib.hpp | 9/24/2005 | 7/21/2005 I know that you previously stated that the library maintainer was MIA and I don't know when/how the 1.34.0 development started but to an outsider (me) it looks like the iostreams library code was taken from an outdated location - maybe 1.33.0 or maybe before even then... I know that 1.34.0 has "shipped" but given that the entire iostream library looks like it might be based on the wrong version might warrant more immediate action than to wait for 1.34.1... Someone more knowledgable about the library should at least look into the differences in short order and give you an informed opinion as to what's been "lost" so that you can make a decision as to course of action (trigger 1.34.1, 1.34.0 addendum/notice regarding the true state of the library, whatever...). -Chris Woods