c++.announce - STLSoft 1.8.3 beta 4
- Matthew (101/101) Mar 20 2005 Download from http://stlsoft.org/downloads.html#stlsoft_1_8_3b4
- Pablo Aguilar (8/33) Mar 21 2005 Great!!!
- Matthew (8/44) Mar 21 2005 Yeah, it's time I addressed structural conformance and gave it its due r...
- christopher diggins (6/6) Mar 23 2005 The download through:
- Matthew (6/12) Mar 23 2005 It's there ok. (After I post something I always download it to make sure...
- christopher diggins (8/12) Mar 25 2005 DOH!
- Matthew (2/10) Mar 25 2005 We're all dumb-dumbs. ;)
Download from http://stlsoft.org/downloads.html#stlsoft_1_8_3b4 Diffs as follows at end of message (and in release notes). Noteworthy changes: - UNIXSTL's filesystem_traits has new fstat(), open(), close() and get_file_size() methods - UNIXSTL's readdir_sequence has the BREAKING CHANGE of value_type being redefined from struct dirent const * to char const *. To get the old behaviour, define UNIXSTL_READDIR_SEQUENCE_OLD_VALUE_TYPE There are also two new classes: - WinSTL's memory_mapped_file - UNIXSTL's memory_mapped_file And a whole new sub-project, PlatformSTL, which provides platform abstraction for structurally conformant UNIXSTL and WinSTL components. For example, #include <platformstl/memory_mapped_file.hpp> will introduce either unixstl::memory_mapped_file or winstl::memory_mapped_file into the platformstl namespace. All PlatformSTL headers include <platformstl/platformstl.hpp>, which will detect either UNIX (unix) or Win32 (WIN32) compilation, and define the corresponding symbol PLATFORMSTL_OS_IS_UNIX or PLATFORMSTL_OS_IS_WIN32. Note: PlatformSTL only contains mappings between components from the two operating systems that are structurally conformant. Examples are file_path_buffer, process_mutex, pipe, etc. Although the conformance is not necessarily 100% in all cases, it is high in all cases. For components where structural conformance is low, they are not included in PlatformSTL, and you'll have to use them 'manually', via direct inclusion of the winstl or unixstl headers, and explicit pre-processor discrimination. This is, of course, deliberate. PlatformSTL promises nothing it cannot deliver. Src-diffs: From 1.8.3 beta 3 => 1.8.3 beta 4 root-dir-1: H:\3Pty\stlsoft\1.8.3-beta3 root-dir-2: H:\3Pty\stlsoft\1.8.3-beta4 Items unchanged from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 350 Items changed from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 6 Items changed (major) from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 1 unixstl_readdir_sequence.h 2.0.3.66 => 3.0.1.67 ; 23rd February 2005 => 20th March 2005 Items changed (minor) from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 1 unixstl_filesystem_traits.h 2.2.1.52 => 2.3.1.53 ; 15th March 2005 => 20th March 2005 Items changed (revision) from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 3 inprogress\winstl\file_functions.hpp 1.0.3.3 => 1.0.4.4 ; 26th February 2005 => 20th March 2005 unixstl_pipe.h 2.0.4.15 => 2.0.5.16 ; 1st March 2005 => 21st March 2005 winstl_filesystem_traits.h 2.3.2.53 => 2.3.3.54 ; 14th March 2005 => 20th March 2005 Items changed (edit) from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 1 rangelib\basic_indirect_range_adaptor.hpp 2.0.3.15 => 2.0.3.16 ; 28th February 2005 => 19th March 2005 Items changed (unversioned) from H:\3Pty\stlsoft\1.8.3-beta3 to H:\3Pty\stlsoft\1.8.3-beta4: 0 Items deleted from H:\3Pty\stlsoft\1.8.3-beta3: 0 Items added to H:\3Pty\stlsoft\1.8.3-beta4: 33 H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\file_path_buffer.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\filesystem_traits.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\memory_mapped_file.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\module.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\path.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\performance_counter.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\pipe.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\platformstl.h H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\platformstl.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\process_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\spin_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\thread_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\platformstl\tss_index.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\file_path_buffer.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\filesystem_traits.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\memory_mapped_file.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\module.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\performance_counter.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\pipe.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\process_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\readdir_sequence.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\spin_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\unixstl\thread_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\file_path_buffer.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\filesystem_traits.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\memory_mapped_file.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\module.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\performance_counter.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\pipe.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\process_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\spin_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\thread_mutex.hpp H:\3Pty\stlsoft\1.8.3-beta4\inprogress\winstl\tss_index.hpp
Mar 20 2005
"Matthew" <admin stlsoft.dot.dot.dot.dot.org> wrote in message news:d1lpm9$2793$1 digitaldaemon.com...Download from http://stlsoft.org/downloads.html#stlsoft_1_8_3b4 And a whole new sub-project, PlatformSTL, which provides platform abstraction for structurally conformant UNIXSTL and WinSTL components. For example, #include <platformstl/memory_mapped_file.hpp> will introduce either unixstl::memory_mapped_file or winstl::memory_mapped_file into the platformstl namespace. All PlatformSTL headers include <platformstl/platformstl.hpp>, which will detect either UNIX (unix) or Win32 (WIN32) compilation, and define the corresponding symbol PLATFORMSTL_OS_IS_UNIX or PLATFORMSTL_OS_IS_WIN32. Note: PlatformSTL only contains mappings between components from the two operating systems that are structurally conformant. Examples are file_path_buffer, process_mutex, pipe, etc. Although the conformance is not necessarily 100% in all cases, it is high in all cases. For components where structural conformance is low, they are not included in PlatformSTL, and you'll have to use them 'manually', via direct inclusion of the winstl or unixstl headers, and explicit pre-processor discrimination. This is, of course, deliberate. PlatformSTL promises nothing it cannot deliver.Great!!! I'd been meaning to suggest this for a couple of days but kept forgetting to actually post about it... I haven't forgotten about the documentation, I'm just reading a lot of it before I decide to write something... Pablo
Mar 21 2005
"Matthew" <admin stlsoft.dot.dot.dot.dot.org> "Pablo Aguilar" <paguilarg hotmail.com> wrote in message news:d1n6s2$it0$1 digitaldaemon.com..."Matthew" <admin stlsoft.dot.dot.dot.dot.org> wrote in message news:d1lpm9$2793$1 digitaldaemon.com...Yeah, it's time I addressed structural conformance and gave it its due respect. (I'm actually writing a bit about it in the Extended STL draft at the mo, which is part of the reason why I'm moving on it now.)Download from http://stlsoft.org/downloads.html#stlsoft_1_8_3b4 And a whole new sub-project, PlatformSTL, which provides platform abstraction for structurally conformant UNIXSTL and WinSTL components. For example, #include <platformstl/memory_mapped_file.hpp> will introduce either unixstl::memory_mapped_file or winstl::memory_mapped_file into the platformstl namespace. All PlatformSTL headers include <platformstl/platformstl.hpp>, which will detect either UNIX (unix) or Win32 (WIN32) compilation, and define the corresponding symbol PLATFORMSTL_OS_IS_UNIX or PLATFORMSTL_OS_IS_WIN32. Note: PlatformSTL only contains mappings between components from the two operating systems that are structurally conformant. Examples are file_path_buffer, process_mutex, pipe, etc. Although the conformance is not necessarily 100% in all cases, it is high in all cases. For components where structural conformance is low, they are not included in PlatformSTL, and you'll have to use them 'manually', via direct inclusion of the winstl or unixstl headers, and explicit pre-processor discrimination. This is, of course, deliberate. PlatformSTL promises nothing it cannot deliver.Great!!! I'd been meaning to suggest this for a couple of days but kept forgetting to actually post about it...I haven't forgotten about the documentation, I'm just reading a lot of it before I decide to write something...No worries. I am a patient patient. :-) Cheers Matthew
Mar 21 2005
The download through: http://synesis.com.au/software/stlsoft/downloads.html for the beta 4 release appears to be corrupt. I can only download about 15% of the stated 1.1 megs. The resulting download can not be opened with winzip. - Christopher Diggins, http://www.ootl.org
Mar 23 2005
It's there ok. (After I post something I always download it to make sure it's there ok <g>) I just downloaded it again, and it worked fine. Try emptying your cache?? :-) "christopher diggins" <cdiggins videotron.ca> wrote in message news:d1s0cc$2iat$1 digitaldaemon.com...The download through: http://synesis.com.au/software/stlsoft/downloads.html for the beta 4 release appears to be corrupt. I can only download about 15% of the stated 1.1 megs. The resulting download can not be opened with winzip. - Christopher Diggins, http://www.ootl.org
Mar 23 2005
"Matthew" <admin stlsoft.dot.dot.dot.dot.org> wrote in message news:d1sn6u$ab0$1 digitaldaemon.com...It's there ok. (After I post something I always download it to make sure it's there ok <g>) I just downloaded it again, and it worked fine. Try emptying your cache?? :-)DOH! I am a dumb-dumb, thank you. -- Christopher Diggins Object Oriented Template Library (OOTL) http://www.ootl.org
Mar 25 2005
"christopher diggins" <cdiggins videotron.ca> wrote in message news:d217ik$2uog$1 digitaldaemon.com..."Matthew" <admin stlsoft.dot.dot.dot.dot.org> wrote in message news:d1sn6u$ab0$1 digitaldaemon.com...We're all dumb-dumbs. ;)It's there ok. (After I post something I always download it to make sure it's there ok <g>) I just downloaded it again, and it worked fine. Try emptying your cache?? :-)DOH! I am a dumb-dumb, thank you.
Mar 25 2005