- Boost - lists.preview.boost.org

New boost webpage
by Marcin Kalicinski 18 Aug '05

18 Aug '05

Hi all, I know gazillion words have been said on the looks of the new webpage, but still I want to add my 2 pennies. Briefly, I think that links in the text look very ugly and... amateurish? If you insist on having them underlined I suggest you stick with more standard look, such as on OpenOffice.org webpage (and many others). This looks much more professional. Additionally, I'd rather have links in boxes on the right have the same style as links in the text. cheers, Marcin

21 61

Boost regression notification (2005-08-18)
by Douglas Gregor 18 Aug '05

18 Aug '05

<html> <head> <meta http-equiv="refresh" content="1; url=issues-email.txt"> </head> <body> Update in progress (building archive index, done in approximately 19 seconds), please wait... </body> </html>

1 0

Errors in warning texts when building boost 1.33
by Jurko Gospodneti� 18 Aug '05

18 Aug '05

Hi all. Not sure if anyone reported this or if it is fixed in the CVS but when you build the 1.33 boost release on a machine with none of the additional software needed to use the IOStreams zipping functionality the warning displayed (the first one) seems to have a typo... it seems to come out in one line instead of two and one of the bjam 'ECHO' commands gets displayed as well. Hope this helps, Jurko Gospodnetiæ

2 1

MSVC 7.1 warnings for lexical_cast.hpp
by Jurko Gospodneti� 18 Aug '05

18 Aug '05

Hi all. I was wandering if someone could disable the following warnings for the lexical_cast.hpp file when compiled with the MSVC 7.1 compiler: * 4511 - Copy constructor shall not be generated. * 4512 - Assignment operator could not be generated. * 4127 - Conditional expression is constant. They are reported at high warning reporting levels and easy to work around by preparing my own wrapper header that disables them but I would really like it if boost could do this out-of-the-box. Best regards, Jurko Gospodnetiæ

1 0

Re: [boost] Interest for a perl6-like-junctions-class?
by Martin Bonner 18 Aug '05

18 Aug '05

----Original Message---- From: Rob Stewart [mailto:stewart@sig.com] Sent: 18 August 2005 15:12 To: boost(a)lists.boost.org Cc: boost(a)lists.boost.org Subject: Re: [boost] Interest for a perl6-like-junctions-class? > > You can omit spaces to make it look right to you. I dislike > omitting spaces around operators. But semantically they're not operators, they're punctuators to create a user defined operator > So, without the internal > spaces, do you like any of them? > > if (any_of(...) <<some_predicate()>> 5)... // 1 Stands out visually, but that's ANOTHER overloading of >> and << > > if (any_of(...) <some_predicate()> 5)... // 2 This is going to get messy as you say with templates (which would FORCE a space in). > if (any_of(...) ^some_predicate()^ 5)... // 3 > > if (any_of(...) /some_predicate()/ 5)... // 4 These two are visually too light-weight for my taste. Why not: if (any_of(...) *some_predicate()* 5)... or if (any_of(...) %some_predicate()% 5)... ? -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

compile boost 1.3.3
by maurice 18 Aug '05

18 Aug '05

hi guys, I got problems with compiling the new release for MS Visual Studio 7.1 on winXP. I download the boost self extracting exe for win and the pre-build version of bjam for nt machines and I tried to build it with E:\boost_1_33_0>bjam -sVC71_ROOT="E:\programme\Microsoft Visual Studio .NET 2003 " -sTOOLS=vc-7_1 install to compile it bud I just become this output: ****************************************************** Building Boost.Iostreams with bzip2 support disabled. ECHO To enable bzip2, cons ult the Boost.Iostreams documentation ****************************************************** ****************************************************** Building Boost.Iostreams with zlib and gzip support disabled. To enable zlib and gzip, consult the Boost.Iostreams documentation ****************************************************** Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). Couldn't find utypes.h in F:\Dev\icu-3.2\include\unicode ...patience... ...patience... ...found 9922 targets... ...updating 1493 targets... MkDir1 bin spawn: No such file or directory

5 10

VC++ 7.1 compilation
by Shingade, Milind 18 Aug '05

18 Aug '05

Hello everybody: I am new to boost. I am familiar with VC++ and I am compiling VC++6.0 source code under VC++7.1 system. The project uses boost library and I am getting compiler errors in boost library. Please help me removing compiler errors from boost library. Regards, Milind

4 3

surveying async network io libraries
by Jose 18 Aug '05

18 Aug '05

Hi, Pardon my high level focus as I am new to the list. I have read all the multiple threads on this topic and I only want to confirm understanding of what libraries can be used now or in a few months, before a future boost library is available. Authors please jump to provide info on your release plans (if possible). I define the library as a c++ async network io library (at least linux ready now but multi-platform in the future) at the connector / acceptor level (or higher but never at the sockets level) that can be combined in different concurrency models (e.g. single-threaded or multi-threaded where the async network io can run in one or multiple threads). I'll just list a brief pro/con list for the 3 libraries I've found so far nanostreamer (downloaded from the boost vault) ========== pros - good introductory article.pdf - designed to make best use of c++ and boost (my newbie opinion!) - real world code examples, e.g. http server (although not fully developed) cons - no async network io available yet although it is planned (see event queue ext) asio (asio.sf.net) === pros - async network io ready (linux epoll as of 0.31) cons - basic real world code examples (but no http examples) - does not use boost threads netiphany (netiphany.sf.net and boost vault) ======= pros - simple usage (see rfc doc in the vault archive, by Don G) - focused on async network io (not sure how it can be combined with threads) cons - no implementation distributed yet (although mentioned and partially shown in the sf docs) Note that I've not included sockets wrappers or libraries that will not provide an async network io solution in the short term. Also worth checking the scheduler library in cryp.to and the CUJ dec 2002 article on a templated library for fast multiplexing although both of those don't seem to have active development. Thanks and regards Jose

13 33

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Martin Bonner 18 Aug '05

18 Aug '05

----Original Message---- From: Thorsten Ottosen [mailto:nesotto@cs.aau.dk] Sent: 17 August 2005 17:19 To: boost(a)lists.boost.org Subject: Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library > "Martin Bonner" <martin.bonner(a)pitechnology.com> wrote in message >> B) Under what circumstances is a std::container<clone_ptr<T> > >> better than a boost::ptr_container<T>? > > I won't discuss if it's better, Perhaps "better" is too loaded a word. What I meant is that both allow a user to implement a container of heterogeneous objects. The documentation needs to explain when the user should choose one over the other (they must offer different trade-offs). I was about to say "Just as the documentation compares and constrasts boost::any and boost::variant." However it turns out that it doesn't! It would be useful if it did. > but its certainly very different > in thefollowing sense: > > - ptr_container<T> discourages cloning of T objects and doesn't > require it > - vector<clone_ptr<T>> requires cloning of T objects (and hence > encourages > it) > > If T is an OO-type with virtual functions, I find that identity often > matters (performance and logical-wise) and hence that excessive > cloning is best avoided. I agree. I think that clone_ptr is designed for a rather small niche, and I can't see myself ever needing it ... but that doesn't mean it couldn't be useful to somebody. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

[Boost-bugs] [ boost-Bugs-1262967 ] Build process doesn't generate DLL import libs on Cygwin
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1262967, was opened at 2005-08-18 13:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262967&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Václav Haisman (wilx) Assigned to: Nobody/Anonymous (nobody) Summary: Build process doesn't generate DLL import libs on Cygwin Initial Comment: The Boost.Build process doesn't generate any import libraries for DLLs. This is the relevant part of my build script on Cygwin: build_opts="release <runtime-link>static/dynamic <threading>multi" ./tools/build/jam_src/bin.cygwinx86/bjam -d3 -sTOOLS=gcc -sBUILD="${build_opts}" -sPYTHON_VERSION="${python_ver}" --builddir=./build-gcc --stagedir=./stage-gcc --prefix="${install_dir}/usr" --sysconfdir="${install_dir}/etc" --libexecdir="${install_dir}/usr/sbin" --localstatedir="${install_dir}/var" --datadir="${install_dir}/usr/share" --mandir="${install_dir}/usr/share/man" --infodir="${install_dir}/usr/share/info" --without-test --layout=versioned install ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262967&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Documentation/site errors in 1.33
by Kirill Lapshin 18 Aug '05

18 Aug '05

Hello, First of all congratulations on new release, I've installed it and it looks good so far, albeit we are not using much of Boost functionality. Couple of typos/errors I spotted. First of all on main page, in 1.33 announcement, Program Options Library: * Option descriptions are now printed with word wrapping. * Command line parser can bypass unregistered options, _instread_ of throwing. I.e. "instread" should read "instead". Secondly, looks like Boost.Test library has been restructured quite heavily, but compilation page in online documentation has not been updated. For example unit testing framework compilation page states that framework consists of execution_monitor.cpp test_tools.cpp unit_test_parameters.cpp unit_test_log.cpp unit_test_main.cpp unit_test_monitor.cpp unit_test_result.cpp supplied_log_formatters.cpp unit_test_suite.cpp even though unit_test_result.cpp and supplied_log_formatters.cpp do not exist anymore. Proper list of files should be compiler_log_formatter execution_monitor framework plain_report_formatter progress_monitor results_collector results_reporter test_tools unit_test_log unit_test_main unit_test_monitor unit_test_parameters unit_test_suite xml_log_formatter xml_report_formatter Same applies to test execution monitor too. Regards, Kirill.

2 4

[range]possible error in iterator_range<range_result_iterator<const Container>::type >
by Larry Evans 17 Aug '05

17 Aug '05

The following code: <======================== template < class Container > void test_iter_range(Container& a_cont) { typedef typename range_result_iterator<Container>::type citer_type; typedef iterator_range<citer_type> riter_type; riter_type a_riter(a_cont.begin(),a_cont.end()); std::cout<<"a_riter.front="<<a_riter.front()<<"\n"; } >========================= Gives compile time error when Container is const. See test driver and compiler output in sandbox vault under cppljevans and in file iter_range_test.zip. Is this an error in the range lib or am I doing something wrong? TIA. -regards, Larry

2 1

Re: [boost] [1.33.0] VC 7.1 vs. SFINAE/type traits
by Mat Marcus 17 Aug '05

17 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas, On 8/16/05, Thomas Witt <witt(a)acm.org> wrote: >[snip] > > I can't say whether that is your problem, but code like this is > potentially dangerous. It'll break whenever you happen to "suck" in a > use of operator~ on an unnamed enum. And yes it tends to generate weird > error messages. Looking at the errors the unknown type in the is_enum > instantiation looks suspicious to me. > > I only have apples gcc 4 currently. A slightly modified example gives this: > > enum { foo, bar }; > > template <typename EnumType> > typename boost::enable_if<boost::is_enum<EnumType>, EnumType>::type > operator ~ (EnumType a); > > int main() > { > > int i = ~bar; > > std::stringstream t; > > } > > mat.cpp: In function 'int main()': > mat.cpp:14: error: '<anonymous enum>' is/uses anonymous type > mat.cpp:14: error: trying to instantiate 'template<class T> struct > boost::is_enum' > > Thomas Thanks for sending this fascinating example. After doing a bit of my own exploration with gcc 4.0 I must agree with you. If I understand the ramifications correctly, if gcc 4.0 correctly disallows instantiating templates upon unnamed enum types, then SFINAE cannot be safely used for operators that may also happen to exist for (anonymous) enums. In the example above, even if we replace is_enum with a more restricted metafunction, the problem will not go away, since any instantiation would seem to be prohibited. Worse still, though it is easy enough to avoid calling the operator with an anonymous enum, I must also avoid files that might use operators on other unrelated anonymous enums, lest the compiler try to illegally instantiate the metafunction. So the big question is, "Is there no known way of safely testing whether a type is an anonymous enum?" Thanks, Mat -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.2 (Build 2424) iQA/AwUBQwL96RIZBaoznf65EQKf6wCcDyhiiRlQBMQ5NBISeTiQ0rnVEuwAn1y6 D54sfcwOgIvouUhH6QWtzLgv =f75H -----END PGP SIGNATURE-----

6 11

Unit test failure in release mode VS2005 beta 2
by Paul A Bristow 17 Aug '05

17 Aug '05

Boost 1.33.0 Unit_test_example1 is OK in debug thus: ------ Rebuild All started: Project: unit_test_framework, Configuration: Debug Win32 ------ Deleting intermediate and output files for project 'unit_test_framework', configuration 'Debug|Win32' Compiling... xml_report_formatter.cpp xml_log_formatter.cpp unit_test_suite.cpp unit_test_parameters.cpp unit_test_monitor.cpp unit_test_main.cpp unit_test_log.cpp test_tools.cpp results_reporter.cpp results_collector.cpp progress_monitor.cpp plain_report_formatter.cpp framework.cpp i:\boost_1_33_0\boost\test\impl\framework.ipp(313) : warning C4244: 'initializing' : conversion from 'time_t' to 'unsigned int', possible loss of data execution_monitor.cpp compiler_log_formatter.cpp Generating Code... i:\boost_1_33_0\boost\lexical_cast.hpp(223) : warning C4701: potentially uninitialized local variable 'result' used Creating library... Creating browse information file... Microsoft Browse Information Maintenance Utility Version 8.00.50215 Copyright (C) Microsoft Corporation. All rights reserved. Build log was saved at "file://c:\temp\boost_test_library\Debug\BuildLog.htm" unit_test_framework - 0 error(s), 2 warning(s) ------ Rebuild All started: Project: unit_test_example1, Configuration: Debug Win32 ------ Deleting intermediate and output files for project 'unit_test_example1', configuration 'Debug|Win32' Compiling... unit_test_example1.cpp Compiling manifest to resources... Linking... LINK : .\Debug/unit_test_example1.exe not found or not built by the last incremental link; performing full link unit_test_framework.lib(compiler_log_formatter.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with 'Debug\unit_test_framework.lib' or at 'i:\boost_1_33_0\libs\test\build\msvc71_proj\Debug\vc80.pdb'; linking object as if no debug info ... many similar - needs to avoid incremental liking???? Embedding manifest... Build log was saved at "file://c:\temp\boost_test_library\Debug\BuildLog.htm" unit_test_example1 - 0 error(s), 15 warning(s) ========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ========== and runs as expected Running 1 test case... i:/boost_1_33_0/libs/test/example/unit_test_example1.cpp(17): error in "free_tes t_function": check 2 == 1 failed unknown location(0): fatal error in "free_test_function": memory access violatio n *** 1 failure detected (1 failure expected) in test suite "Unit test example 1" Press any key to continue . . . BUT in release >>>>>>>>>>>>>>>>> ------ Rebuild All started: Project: unit_test_framework, Configuration: Release Win32 ------ Deleting intermediate and output files for project 'unit_test_framework', configuration 'Release|Win32' Compiling... xml_report_formatter.cpp xml_log_formatter.cpp unit_test_suite.cpp unit_test_parameters.cpp unit_test_monitor.cpp unit_test_main.cpp unit_test_log.cpp test_tools.cpp results_reporter.cpp results_collector.cpp progress_monitor.cpp plain_report_formatter.cpp framework.cpp ..\..\..\..\boost/test/impl/framework.ipp(313) : warning C4244: 'initializing' : conversion from 'time_t' to 'unsigned int', possible loss of data execution_monitor.cpp ..\..\..\..\boost/test/impl/execution_monitor.ipp(214) : warning C4535: calling _set_se_translator() requires /EHa compiler_log_formatter.cpp Generating Code... Creating library... Build log was saved at "file://i:\boost_1_33_0\libs\test\build\msvc71_proj\Release\BuildLog.htm" unit_test_framework - 0 error(s), 2 warning(s) So library builds OK <<<<<<<<<<<<<<<< ------ Rebuild All started: Project: unit_test_example1, Configuration: Release Win32 ------ Deleting intermediate and output files for project 'unit_test_example1', configuration 'Release|Win32' Compiling... unit_test_example1.cpp Linking... msvcprt.lib(MSVCP80.dll) : error LNK2005: "public: __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@ABV01@@ Z) already defined in unit_test_example1.obj <snip> ... MSVCRT.lib(ti_inst.obj) : error LNK2005: "private: class type_info & __thiscall type_info::operator=(class type_info const &)" (??4type_info@@AAEAAV0@ABV0@@Z) already defined in LIBCMT.lib(typinfo.obj) LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library .\Release/unit_test_example1.exe : fatal error LNK1169: one or more multiply defined symbols found Build log was saved at "file://i:\boost_1_33_0\libs\test\build\msvc71_proj\Release\BuildLog.htm" unit_test_example1 - 33 error(s), 1 warning(s) ========== Rebuild All: 1 succeeded, 1 failed, 0 skipped ========== Suggestions? Thanks Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com

2 1

Boost regression notification (2005-08-17)
by Douglas Gregor 17 Aug '05

17 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-17T15:35:29Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 74 failures in 7 libraries: graph (11) iostreams (3) numeric/ublas (1) parameter (36) regex (1) serialization (21) wave (1) |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |numeric/ublas| test3: intel-8.1-linux |parameter| basics: borland-5_6_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux msvc macros: borland-5_6_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux msvc sfinae: borland-5_6_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux msvc unnamed: borland-5_6_4 cw-9_4 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport |regex| concept_check: gcc-3.2.3-linux |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_text_archive: gcc-3_4_3-sunos test_class_info_load_text_archive_dll: gcc-3_4_3-sunos test_class_info_load_text_warchive: gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: gcc-3_4_3-sunos test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_warchive: gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: gcc-3_4_3-sunos test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_shared_ptr_132_text_archive: gcc-3.2.3-linux |wave| testwave: gcc-3.3.6-linux

1 0

[1.33.0][Iostreams] Spelling mistake in documentation
by Paul 17 Aug '05

17 Aug '05

Hi, I assume someone has seen the couple of spelling mistakes in this paragraph, from the boost::iostreams tutorial page in the docs: <quote> Finally, I sould mention that the Iostremas library provides an easier way to read from an STL container: instances of boost::iterator_range can be added directly to filtering streams and stream buffers. So you could write: </quote> but i'd thought i'd mention it anyway. I searched the lists for 'sould' and didn't find any mention. see ya Paul

2 1

boost 1.33.0: Bug in property
by Philipp Thomas 17 Aug '05

17 Aug '05

boost_1_33_0/boost/pending/property.hpp has template <class Tag, class T, class Base = no_property> struct property : public Base { typedef Base next_type; typedef Tag tag_type; typedef T value_type; property() { } property(const T& v) : m_value(v) { } property(const T& v, const Base& b) : Base(b), m_value(v) { } // copy constructor and assignment operator will be generated by compiler T m_value; }; The bug here is that the empty ctor does not initialize m_value which leads to gcc 4.0.1 warning about m_value being used uninitialized. As our automatic build system rejects packages with such warnings I had to fix it :) This is the patch I'm using: --- boost/pending/property.hpp +++ boost/pending/property.hpp @@ -22,7 +22,7 @@ typedef Base next_type; typedef Tag tag_type; typedef T value_type; - property() { } + property() : m_value() { } property(const T& v) : m_value(v) { } property(const T& v, const Base& b) : Base(b), m_value(v) { } // copy constructor and assignment operator will be generated by compiler Philipp -- Philipp Thomas <pth(a)suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany

1 0

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Martin Bonner 17 Aug '05

17 Aug '05

----Original Message---- From: Axter [mailto:boost@axter.com] Sent: 17 August 2005 01:54 To: boost(a)lists.boost.org Subject: Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library > The documents state that the clone_ptr class is based on strict > pointer ownership logic. I am not familiar with that term, so it didn't help. > The above code is not using strict ownership logic, and instead the > object is created using a dumb pointer. But your example code has this problem. > I also think you're right in that I should add more to the > documentation Absolutely. I am sure that this code satisfied a real need that you had. What is not at all clear is whether that need is widespread enough to justify including the clone_ptr in boost. What is needed is some clear documentation including: - an explanation of what problems the class solves ("motivating examples"). Note this doesn't need to be very detailed as too why the problem exists at this point. I imagine most people on this list understand concepts like "slicing". - An overview of the class usage (including the restrictions on how the class may be used) - A description of the specification of the class and its members, including the concepts that the template parameters must model. (Don't worry too much about getting the English right. If the library does go into boost, plenty of people here can help with that later.) Finally you might like to consider the following: A) I can see how something like this might be useful to allow a copyable class which owns an object of a polymorphic type. However, under what circumstances is this better than providing a clone() member in the polymorphic type? B) Under what circumstances is a std::container<clone_ptr<T> > better than a boost::ptr_container<T>? -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

[regex] MipsPro warnings in boost/regex/pending/static_mutex.hpp (1.33.0)
by Richard Hadsell 17 Aug '05

17 Aug '05

The mipspro build of regex gives repeated warnings in static_mutex.hpp: mipspro-C++-action bin/boost/libs/regex/build/libboost_regex.so/mipspro/debug/cpp_regex_traits.o cc-1460 CC: WARNING File = /tmp_mnt/netDISKS/cgi/IRIX4/cgi/vendor/library/boost/boost_1_33_0/boost/regex/pending/static_mutex.hpp, Line = 69 Function function "boost::scoped_static_mutex_lock::locked" is redeclared "inline" after being called. inline bool scoped_static_mutex_lock::locked()const ^ I fixed it by declaring both 'operator void const*()' and 'bool locked()' inline in all 3 sections of the header: diff -u -r1.1 -r1.2 --- boost/regex/pending/static_mutex.hpp 2005/08/12 17:26:18 1.1 +++ boost/regex/pending/static_mutex.hpp 2005/08/16 16:49:44 1.2 @@ -52,8 +52,8 @@ public: scoped_static_mutex_lock(static_mutex& mut, bool lk = true); ~scoped_static_mutex_lock(); - operator void const*()const; - bool locked()const; + inline operator void const*()const; + inline bool locked()const; void lock(); void unlock(); private: @@ -99,8 +99,8 @@ public: scoped_static_mutex_lock(static_mutex& mut, bool lk = true); ~scoped_static_mutex_lock(); - operator void const*()const; - bool locked()const; + inline operator void const*()const; + inline bool locked()const; void lock(); void unlock(); private: @@ -154,8 +154,8 @@ public: scoped_static_mutex_lock(static_mutex& mut, bool lk = true); ~scoped_static_mutex_lock(); - operator void const*()const; - bool locked()const; + inline operator void const*()const; + inline bool locked()const; void lock(); void unlock(); private: -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

3 3

css patch (more/css_0/front.css)
by Janusz Piwowarski 17 Aug '05

17 Aug '05

Hello, I'm attaching the patch against unintentional(?) "Revision.." underlining (you can see it at boottom of htpp://boost.org page) BTW, Opera displays sans-serif as Verdana and it looks very well. Regards, Janusz

2 1

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Martin Bonner 17 Aug '05

17 Aug '05

----Original Message---- From: Jonathan Wakely [mailto:cow@compsoc.man.ac.uk] Sent: 17 August 2005 14:17 To: boost(a)lists.boost.org Subject: Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to theboost library > Axter wrote: > >> It does not need a clone member if you apply strict pointer >> ownership logic, which is what a clone pointer normally does. > > clone_ptr also needs the definitions of all derived classes to be > visible, whereas something like ptr_container that uses a clone() > member function only needs to see the definition of the base > class and can do everything through the base class' interface. I think it only needs the definition available for the constructor (which is where a class derived from his "copier" class is instantiated). [snip] > This would not be possible with std::vector<clone_ptr<Base> >: > > // pc.h > #include <boost/ptr_container/ptr_vector.hpp> > struct Base { > ~Base() {} > virtual Base* clone() = 0; > virtual void f() = 0; > }; > void fill(boost::ptr_vector<Base>&); > > // pc.cc > #include "pc.h" > #include <boost/bind.hpp> > #include <algorithm> > > int main() > { > boost::ptr_vector<Base> v; > fill(v); > std::for_each(v.begin(), v.end(), boost::bind(&Base::f, _1)); > return 0; > } > > The fill() function can now be implemented in another file and > populate the vector with any type derived from Base, without > recompiling pc.cc I think that is supported with clone_ptr. The file implementing fill would need the full definition of the derived type(s) of course, but that is less restrictive. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Martin Bonner 17 Aug '05

17 Aug '05

----Original Message---- From: Axter [mailto:boost@axter.com] Sent: 16 August 2005 03:39 To: boost(a)lists.boost.org Subject: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library > I'm proposing to add the clone_ptr class to the boost library. > > I've developed a clone_ptr class that performs a clone of an abstract > pointer without the need for a clone method. > > The clone_ptr is well suited for automatic deep copy of abstract > pointers, > and for use with STL containers. > > In addition to being able to perform clone operations, it also have > operators that performs comparison on the object being pointed to, > instead > of the pointer address. > This allows for correct sorting and comparison of clone_ptr's in an > STL > container. > See following link for more info: > http://code.axter.com/clone_ptr_introduction.htm I was interested in the example you give in the web page: class foo { clone_ptr < AbstractClass > m_MyAbstractClassPtr; public: foo(AbstractClass * abstractclassptr_):m_MyAbstractClassPtr(abstractclassptr_){} foo(const foo& Src) { //In the following line of code, the clone pointer will copy the // correct derived class without the need of a clone method m_MyAbstractClassPtr = Src.m_MyAbstractClassPtr; } }; That looked a very clever trick. I couldn't see how clone_ptr was going to copy the dynamic type of the argument to the constructor without any information about that dynamic type. Having looked at the code, I don't think it does. It would work if the constructor was declared: foo(DerivedClass*p): m_MyAbstractClassPtr(p) {} or even template <class Derived> foo(Derived *p):m_MyAbstractClassPtr(p) {} but even that will fail if the constructor is called via: Derived *p = new DerivedDerived; foo foo_obj(p); My basic concern is that while clone_ptr could be useful, it only works if people stick rigidly to certain rules. Those rules need to be made VERY clear, otherwise it provides a plentiful supply of rope. It would also be useful to have some documentation of what methods clone_ptr provides, and what effects they have. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

6 7

[Boost-bugs] [ boost-Bugs-1262038 ] boost:signals SIGSEV
by SourceForge.net 17 Aug '05

17 Aug '05

Bugs item #1262038, was opened at 2005-08-17 14:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262038&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: macchese (macchese) Assigned to: Nobody/Anonymous (nobody) Summary: boost:signals SIGSEV Initial Comment: hi all, I'm using boost-1_33 with $ g++ --v Reading specs from /usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/specs Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-clocale=gnu --disable-libunwind-exceptions --enable-languages=c,c++,ada,f77,objc,java --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-7mdk) and, just compiled the first example from http://www.boost.org/doc/html/signals/tutorial.html#id1280117 I obtain a segmentation fault. this is the trace from gdb [max@macchese temp]$ gdb ./unitest GNU gdb 6.3-3.1.102mdk (Mandrakelinux) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i586-mandrake-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) r Starting program: /home/max/src/temp/unitest Program received signal SIGSEGV, Segmentation fault. 0x0804bbdf in std::less<int>::operator() () (gdb) bt #0 0x0804bbdf in std::less<int>::operator() () #1 0x0804b901 in boost::signals::detail::any_bridge_compare<std::less<int>, int>::operator() () #2 0x0804b3d1 in boost::detail::function::function_obj_invoker2<boost::signals::detail::any_bridge_compare<std::less<int>, int>, bool, boost::any, boost::any>::invoke () #3 0xb7fdf7e0 in boost::function2<bool, boost::any, boost::any, std::allocator<boost::function_base> >::operator() ( this=0x8050030, a0={content = 0x80500c0}, a1={content = 0x8050080}) at function_template.hpp:576 #4 0xb7fe049e in std::_Rb_tree<boost::any, std::pair<boost::any const, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> > >, std::_Select1st<std::pair<boost::any const, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> > > >, boost::function2<bool, boost::any, boost::any, std::allocator<boost::function_base> >, std::allocator<std::pair<boost::any const,std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> > > >>::lower_bound (this=0x8050030, __k=@0xbffff1e0) at stl_tree.h:1154 #5 0xb7fdf6dd in std::map<boost::any, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> >, boost::function2<bool, boost::any, boost::any, std::allocator<boost::function_base> >,std::allocator<std::pair<boost::any const, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> > > > >::lower_bound (this=0x8050030, __x=@0xbffff1e0) at stl_map.h:540 #6 0xb7fdec09 in std::map<boost::any, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> >, boost::function2<bool, boost::any, boost::any, std::allocator<boost::function_base> >,std::allocator<std::pair<boost::any const, std::list<boost::signals::detail::connection_slot_pair, std::allocator<boost::signals::detail::connection_slot_pair> > > > >::operator[] (this=0x8050030, __k=@0xbffff1e0) at stl_map.h:336 #7 0xb7fdddad in boost::signals::detail::named_slot_map::clear (this=0x8050030) at /home/max/src/boost_1_33_0/libs/signals/build/../src/named_slot_map.cpp:81 #8 0xb7fddce7 in named_slot_map (this=0x8050030, compare=@0xbffff2d0) at /home/max/src/boost_1_33_0/libs/signals/build/../src/named_slot_map.cpp:74 #9 0xb7fe19bf in signal_base_impl (this=0x8050028, comp=@0xbffff2d0, combiner=@0xbffff2e0) at /home/max/src/boost_1_33_0/libs/signals/build/../src/signal_base.cpp:23 #10 0xb7fe23c0 in signal_base (this=0xbffff390, comp=@0xbffff2d0, combiner=@0xbffff2e0) at /home/max/src/boost_1_33_0/libs/signals/build/../src/signal_base.cpp:179 #11 0x0804a0cc in boost::signal0<void, boost::last_value<void>, int, std::less<int>, boost::function<void ()(), std::allocator<void> > >::signal0 () #12 0x08049921 in boost::signal<void ()(), boost::last_value<void>, int, std::less<int>, boost::function<void ()(), std::allocator<void> > >::signal () #13 0x08049601 in main () (gdb) I compiled the source (in attach) by: g++ main.cpp -o unitest -I/usr/local/include -I/usr/local/include/boost-1_33/ -L/usr/local/lib -lboost_signals-gcc-d I tryied also libboost_signals-gcc-mt-d with the same result. hope this help ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262038&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Bugs-1262030 ] there is not a signal category
by SourceForge.net 17 Aug '05

17 Aug '05

Bugs item #1262030, was opened at 2005-08-17 14:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262030&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: macchese (macchese) Assigned to: Nobody/Anonymous (nobody) Summary: there is not a signal category Initial Comment: I'm trying to submit a bug for the signals library, I'm wondering if there is a category or should use the "any" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1262030&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] patch to silence a MSVC++ warning in trim.hpp
by Martin Bonner 17 Aug '05

17 Aug '05

----Original Message---- From: Stefan Seefeld [mailto:seefeld@sympatico.ca] Sent: 17 August 2005 11:59 To: boost(a)lists.boost.org Subject: Re: [boost] patch to silence a MSVC++ warning in trim.hpp > Vadim Zeitlin wrote: >> Hello, >> >> when compiling <boost/algorithm/string/trim.hpp> with MSVC 7.1 at >> maximal warning level you get a warning 4512 ("assignment operator >> could not be generated") because of the const members in struct >> is_classifiedF from boost/algorithm/string/detail/classification.hpp. >> >> The trivial patch below fixes it. Notice that I didn't take the >> assignment operator in "#ifdef _MSC_VER" because I see no harm in >> doing this for all compilers but then no other compiler I know about >> gives such warning so it should be also safe to add the #ifdef if >> this is preferred. > > Wouldn't it be even better to provide a new baseclass > boost::nonassignable that is similar to boost::noncopyable ? That > makes things even more explicit. > That wouldn't help. If you derive from boost::noncopyable, you get warning 4512 (because MSVC is unable to generate an assignment operator). I think the best fix is for users to #pragma off the warning. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Axter 17 Aug '05

17 Aug '05

I'm proposing to add the clone_ptr class to the boost library. I've developed a clone_ptr class that performs a clone of an abstract pointer without the need for a clone method. The clone_ptr is well suited for automatic deep copy of abstract pointers, and for use with STL containers. In addition to being able to perform clone operations, it also have operators that performs comparison on the object being pointed to, instead of the pointer address. This allows for correct sorting and comparison of clone_ptr's in an STL container. See following link for more info: http://code.axter.com/clone_ptr_introduction.htm Also check out the boost vault (clone_ptr_Introduction.zip )

2 2

patch to silence a MSVC++ warning in trim.hpp
by Vadim Zeitlin 17 Aug '05

17 Aug '05

Hello, when compiling <boost/algorithm/string/trim.hpp> with MSVC 7.1 at maximal warning level you get a warning 4512 ("assignment operator could not be generated") because of the const members in struct is_classifiedF from boost/algorithm/string/detail/classification.hpp. The trivial patch below fixes it. Notice that I didn't take the assignment operator in "#ifdef _MSC_VER" because I see no harm in doing this for all compilers but then no other compiler I know about gives such warning so it should be also safe to add the #ifdef if this is preferred. *** classification.hpp.orig Wed Aug 17 10:19:50 2005 --- classification.hpp Wed Aug 17 10:19:46 2005 *************** *** 55,60 **** --- 55,64 ---- #endif private: + // prevent compiler from trying to generate this operator + // automatically (and failing because of const members) + is_classifiedF& operator=(const is_classifiedF&); + const std::ctype_base::mask m_Type; const std::locale m_Locale; }; Thanks in advance, VZ

2 1

"/usr/bin/objcopy" --set-section-flags .debug_str=contents, debug
by Neal Becker 17 Aug '05

17 Aug '05

just curious. Why do debug builds of boost on gcc use this? What does it mean? I'm just wondering. I've never seen it needed for any other build. g++ -g is all that I've ever seen used to build a debug version of anything. "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug

5 8

Re: [boost] [futures] request for comments
by Florian Schintke 17 Aug '05

17 Aug '05

> > You asked for comments, so here goes: I find the apparently > > copious use of implicit conversions disturbing. Especially > > disturbing is the fact that futures seem to have both > > incoming and outgoing implicit conversions. > > In direct discussions with Thorsten I strongly objected against having an > operator T(), he want's to see the commenst on this list anyway... > > [...] > > Regards Hartmut Hi, I am neither an C++ expert nor do I know the internal reasons why inmplicit conversion may be awkward, but as Thorsten I like the futures including the implicit conversion. In the following I try to explain my reasons for this. Futures can be used for asynchronous function calls, but futures could (with another implementation) also be used for lazy evaluation. >From the programmers point of view it is nice, if you can specify the behaviour of your code by just changing the declaration of your variables and do not have to change anything else. // select one of the following declarations // here the single call is visible (explanation see below) int f = fac(15); future<int> f = fac(15); future<int,lazy> f = fac(15); // ... do something else ... // ... later use f (maybe at multiple locations in the code) // without any syntactical change ... do_something(f); cout << f << endl; With this schema one could easily change the computational model from synchronous, asynchronous (concurrently) and lazy. Missing the implicit conversion one would have to change every use of f to f(). If f() is once evaluated (waited for the asynchronous call) f behaves like a normal variable. The function is not evaluated again if f is used again. Why should one have to write () at each usage of this variable? This would be misleading and suggest that something is called or evaluated every time (including side effects of fac()), wich is not the case. Florian -- Florian Schintke <schintke(a)zib.de>, http://www.zib.de/schintke/

1 0

[regex] bad_expression changed interface
by Lorenzo Bettini 17 Aug '05

17 Aug '05

Hi in 1.31 bad_expression was class bad_expression : public bad_pattern { public: bad_expression(const std::string& s) : bad_pattern(s) {} }; now in 1.33 it is class regex_error : public std::runtime_error { public: explicit regex_error(const std::string& s, regex_constants::error_type err, std::ptrdiff_t pos); explicit regex_error(boost::regex_constants::error_type err); boost::regex_constants::error_type code()const; std::ptrdiff_t position()const; }; typedef regex_error bad_pattern; // for backwards compatibility typedef regex_error bad_expression; // for backwards compatibility so I was wondering if there's a way to make throw boost::bad_expression("internal error"); compile on both versions of the library (this statement was reported not to compile with 1.33 by a user of one of my programs) many thanks in advance Lorenzo -- +-----------------------------------------------------+ | Lorenzo Bettini ICQ# lbetto, 16080134 | | PhD in Computer Science | | Dip. Sistemi e Informatica, Univ. di Firenze | | Florence - Italy (GNU/Linux User # 158233) | | Home Page : http://www.lorenzobettini.it | | http://music.dsi.unifi.it XKlaim language | | http://www.lorenzobettini.it/purple Cover Band | | http://www.gnu.org/software/src-highlite | | http://www.gnu.org/software/gengetopt | | http://www.lorenzobettini.it/software/gengen | | http://www.lorenzobettini.it/software/doublecpp | +-----------------------------------------------------+

2 2

Foreach and typeof
by Edward Diener 17 Aug '05

17 Aug '05

Did either foreach or typeof make it into Boost 1.33 ? I see nothing about either in the documentation and I had the impression that both passed the review and were to be in Boost 1.33. I guess they will be in the next release.

4 4

Re: [boost] Interest for a perl6-like-junctions-class?
by Rob Stewart 17 Aug '05

17 Aug '05

I posted another update to multivalues.zip. This one eliminates dependence on SFINAE, so it may compile on additional compilers. -- Rob Stewart stewart(a)sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;

1 0

[Test] 1.33 small typo error with MIPS Pro
by Kevin Wheatley 16 Aug '05

16 Aug '05

Under MIPS pro va_end() is a null macro and this then causes a warning, so I assume that the commas should be semi-colons. Kevin --- boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/test/impl/test_tools.ipp 2005-06-22 23:03:05.000000000 +0100 +++ boost_1_33_0/boost/test/impl/test_tools.ipp 2005-08-16 09:41:13.000000000 +0100 @@ -173,7 +173,7 @@ unit_test_log << "difference between " << arg1_descr << "{" << arg1_val << "}" << " and " << arg2_descr << "{" << arg2_val << "}" << ( tl == PASS ? " doesn't exceed " : " exceeds " ) - << toler_val << "%", + << toler_val << "%"; va_end( args ); @@ -196,7 +196,7 @@ unit_test_log << "absolute value of " << arg1_descr << "{" << arg1_val << "}" << ( tl == PASS ? " doesn't exceed " : " exceeds " ) - << toler_val, + << toler_val; va_end( args ); -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |

4 3

[1.33.0] VC 7.1 vs. SFINAE/type traits
by Mat Marcus 16 Aug '05

16 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In one of our projects, the following code produces some strange compilation errors under VC 7.1/boost 1.33.0. Can anyone suggest a workaround? - Mat #include <sstream> #include "boost/type_traits.hpp" #include "boost/utility/enable_if.hpp" template <typename EnumType> typename boost::enable_if<boost::is_enum<EnumType>, EnumType>::type operator ~ (EnumType a); std::stringstream t; -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.2 (Build 2424) iQA/AwUBQwIDTxIZBaoznf65EQKEyACgnVW7095czvJp1MMvNruggOxQfIQAn2Qs TAtl4P353L4rRplTeFJwW2kO =jqlu -----END PGP SIGNATURE-----

4 4

Boost::UTF
by Owen Anderson 16 Aug '05

16 Aug '05

Hello, I was looking on Google for a good means of dealing with UTF encoded text files, and I ran across the old postings about Alberto Barbati's UTF library for Boost. While I know that the old files are still around, is there any progress being made on this front? Or is this a dead-end? Because it's exactly what I was looking for! -Owen Anderson

7 6

boost 1.32: read_write_mutex assertion
by Slawomir Lisznianski 16 Aug '05

16 Aug '05

Hello, I'm using Boost.Threads read/write mutex with the writer scheduling priority. Under heavy load, from many threads, I'm getting the following assertion: <..>/boost/boost_1_32_0/libs/thread/src/read_write_mutex.cpp:190: void boost::deta il::thread::read_write_mutex_impl<Mutex>::do_write_lock() [with Mutex = boost::mutex]: Assertion `++loop_count == 1' failed. Abort (core dumped) The system is Linux kernel 2.4.21 (SMP) with 4 CPUs (Intel XEON MP) and g++ 3.2.3 20030502 (Red Hat Linux 3.2.3-42). Has anyone else experienced a similar problem? Thanks, Slawomir

1 0

Re: [boost] boost dll versions
by Martin Bonner 16 Aug '05

16 Aug '05

----Original Message---- From: David Abrahams [mailto:dave@boost-consulting.com] Sent: 16 August 2005 14:19 To: boost(a)lists.boost.org Subject: Re: [boost] boost dll versions >> While the breadth of support has helped boost gain wide acceptance, >> it is also the single biggest fault of the library as well. > > ?? Breadth of support has many benefits and only a few costs, and most > of those fall on the library maintainers. Library users (ahem, like > you) might pay for a slight reduction in velocity, but that's all. No, there are two further costs that library users pay: a) Features that are not implemented because they are too hard on older compilers. b) Features that use a less convenient syntax because supporting the more convenient syntax is too hard on older compilers. c) Features that are not implemented because the library maintainer has spent her limited time on maintaining support for older compilers. Having said that, it sure makes it easier to get buy-in to boost if it doesn't involve a compiler upgrade! -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

Can't upload to the sandbox?
by John Maddock 16 Aug '05

16 Aug '05

Trying to upload to the sandbox I get the following errors: Warning: fopen(userstats/johnmaddock.stat): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 785 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 797 Warning: fopen(stats/2005/08/month.stats): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 346 Warning: fwrite(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 348 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 350 Warning: fopen(stats/2005/08/16): failed to open stream: Read-only file system in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 275 Warning: fwrite(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 277 Warning: fclose(): supplied argument is not a valid stream resource in /home/groups/b/bo/boost-sandbox/htdocs/vault/include/functions.php on line 279 The uploaded file appears in the list, but can't be accessed. Anyone any ideas what's wrong? Thanks, John.

2 2

[regex] 1.33 missing include causes compile error... MIPS Pro 7.4.1
by Kevin Wheatley 16 Aug '05

16 Aug '05

cpp_regex_traits.hpp appears to be missing an include to define std::basic_istream<> ... cc-1070 CC: ERROR File = boost_1_33_0/boost/regex/v4/cpp_regex_traits.hpp, Line = 442 The indicated type is incomplete. std::basic_istream<charT> m_is; // stream for parsing numbers. ^ A template was detected during header processing. instantiation of class "boost::re_detail::cpp_regex_traits_implementation<char>" at line 945 instantiation of "std::string boost::cpp_regex_traits<char>::error_string(boost::regex_ constants::error_type) const" at line 171 of "boost_1_33_0/libs/regex/build/../src/posix_api.cpp" 1 error detected in the compilation of "boost_1_33_0/libs/regex/build/../src/posix_api.cpp". So the attatched patch adds a suitable include to get regex compiling Kevin -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself | --- boost_1_33_0_mipspro_7.4.1/include/boost-1_33/boost/regex/v4/cpp_regex_traits.hpp 2005-07-12 10:49:10.000000000 +0100 +++ boost_1_33_0/boost/regex/v4/cpp_regex_traits.hpp 2005-08-16 14:32:00.000000000 +0100 @@ -21,6 +21,8 @@ #include <boost/config.hpp> +#include <istream> + #ifndef BOOST_NO_STD_LOCALE #ifndef BOOST_RE_PAT_EXCEPT_HPP

2 1

[regex] MipsPro failure in boost/regex/v4/fileiter.hpp (1.33.0)
by Richard Hadsell 16 Aug '05

16 Aug '05

The mipspro build of regex fails in fileiter.cpp, because the header is missing an include: mipspro-C++-action bin/boost/libs/regex/build/libboost_regex.so/mipspro/debug/fileiter.o cc-1079 CC: ERROR File = /tmp_mnt/netDISKS/cgi/IRIX4/cgi/vendor/library/boost/boost_1_33_0/boost/regex/v4/fileiter.hpp, Line = 212 A type specifier is expected. typedef std::ptrdiff_t difference_type; ^ ... (2 similar places in the same file) The fix should be good for any compiler: diff -u -r1.1 -r1.2 --- boost/regex/v4/fileiter.hpp 2005/08/12 17:26:18 1.1 +++ boost/regex/v4/fileiter.hpp 2005/08/16 16:49:48 1.2 @@ -61,6 +61,7 @@ #elif defined(BOOST_REGEX_FI_POSIX_DIR) +#include <cstddef> #include <cstdio> #include <cctype> #include <iterator> P.S.: Thanks to Kevin Wheatley for reporting a similar problem in cpp_regex_traits.hpp, so that I didn't have to. -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

1 0

Boost regression notification (2005-08-16)
by Douglas Gregor 16 Aug '05

16 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-16T14:49:25Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 107 failures in 7 libraries: graph (11) iostreams (3) numeric/ublas (1) parameter (69) regex (1) serialization (21) wave (1) |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |numeric/ublas| test3: intel-8.1-linux |parameter| basics: borland-5_6_4 cw-8_3 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 macros: borland-5_6_4 cw-8_3 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_6_4 cw-8_3 cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-9_0 msvc vc-6_5 vc-6_5-stlport vc-7_0 unnamed: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 |regex| concept_check: gcc-3.2.3-linux |serialization| test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_text_archive: gcc-3_4_3-sunos test_class_info_load_text_archive_dll: gcc-3_4_3-sunos test_class_info_load_text_warchive: gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: gcc-3_4_3-sunos test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_warchive: gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: gcc-3_4_3-sunos test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc test_shared_ptr_132_text_archive: gcc-3.2.3-linux |wave| testwave: gcc-3.3.6-linux

1 0

Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library
by Eyal Farago 16 Aug '05

16 Aug '05

besides implementation issues regarding proper creation and destruction of a clone_ptr, it seems that you're trying to achieve few goals in one class. you're talking about the clone problem which is a complete problem on its own and then you're talking about pointers in stl containers and algorithms, and as a result you came out with a class that tries to solve both problems. these two problems are completeley unrelated, you can itroduce a simple adaptor that modifies an existing pointer type (smart or not...) into a comparable class (I've implemented one in a few minutes) and you can write a seperate class that takes care of clowning (possible or not, I don't know, follow the thread), then you can wrap it all together using a typedef and get a simpler, more flaxible and robust design. then you can readopt the entire thing using another adaptor... (*i.e. copy on write.) by the way, this is the approach taken by the iterator adaptors library, if you need a filter and transform iterator you simply apply a transform iterator adaptor to a filter iterator adaptor applied to the base iterator. eyal. -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org]On Behalf Of Martin Bonner Sent: Tuesday, August 16, 2005 12:17 PM To: 'boost(a)lists.boost.org' Subject: Re: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library ----Original Message---- From: Axter [mailto:boost@axter.com] Sent: 16 August 2005 03:39 To: boost(a)lists.boost.org Subject: [boost] Propose adding Clone Smart Pointer (clone_ptr) to the boost library > I'm proposing to add the clone_ptr class to the boost library. > > I've developed a clone_ptr class that performs a clone of an abstract > pointer without the need for a clone method. > > The clone_ptr is well suited for automatic deep copy of abstract > pointers, > and for use with STL containers. > > In addition to being able to perform clone operations, it also have > operators that performs comparison on the object being pointed to, > instead > of the pointer address. > This allows for correct sorting and comparison of clone_ptr's in an > STL > container. > See following link for more info: > http://code.axter.com/clone_ptr_introduction.htm I was interested in the example you give in the web page: class foo { clone_ptr < AbstractClass > m_MyAbstractClassPtr; public: foo(AbstractClass * abstractclassptr_):m_MyAbstractClassPtr(abstractclassptr_){} foo(const foo& Src) { //In the following line of code, the clone pointer will copy the // correct derived class without the need of a clone method m_MyAbstractClassPtr = Src.m_MyAbstractClassPtr; } }; That looked a very clever trick. I couldn't see how clone_ptr was going to copy the dynamic type of the argument to the constructor without any information about that dynamic type. Having looked at the code, I don't think it does. It would work if the constructor was declared: foo(DerivedClass*p): m_MyAbstractClassPtr(p) {} or even template <class Derived> foo(Derived *p):m_MyAbstractClassPtr(p) {} but even that will fail if the constructor is called via: Derived *p = new DerivedDerived; foo foo_obj(p); My basic concern is that while clone_ptr could be useful, it only works if people stick rigidly to certain rules. Those rules need to be made VERY clear, otherwise it provides a plentiful supply of rope. It would also be useful to have some documentation of what methods clone_ptr provides, and what effects they have. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434 _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] boost dll versions
by Martin Bonner 16 Aug '05

16 Aug '05

----Original Message---- From: Martin Bonner [mailto:martin.bonner@pitechnology.com] Sent: 16 August 2005 14:55 To: 'boost(a)lists.boost.org' Subject: Re: [boost] boost dll versions > No, there are two further costs [snip] ^^^ > a) [snip] > b) [snip] > c) [snip] Humph. That's why I usually use a computer to do my counting for me :-( -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

[Boost-bugs] [ boost-Bugs-1260961 ] VC7.1 operator << doesn't work for non-const objects
by SourceForge.net 16 Aug '05

16 Aug '05

Bugs item #1260961, was opened at 2005-08-16 20:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1260961&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Serge Sivkov (s-sivkov) Assigned to: Robert Ramey (ramey) Summary: VC7.1 operator << doesn't work for non-const objects Initial Comment: The manual says operators & and << are equals. In fact, operator << doesn't work for non-const objects, but operator & works. Yere is simple example: if i change string const gps_position g(35, 59, 24.567f); to gps_position g(35, 59, 24.567f); (function main() in demo.cpp) then i will see compilation error: --- c:\Boost\include\boost-1_33\boost\archive\detail\oserializer.hpp(566): error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] --- but for operator & (i.e. from oa << g; to oa & g; ) all works perfectly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1260961&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Test] small documentation bug
by Matt Hurd 16 Aug '05

16 Aug '05

I noticed that in http://www.boost.org/libs/test/doc/components/test_tools/reference/BOOST_CH… the second example uses incorrect syntax. I think it s/be BOOST_CHECK_PREDICATE( std::not_equal_to<int>(), (i)(17) ); Regards, Matt matthurd(a)acm.org

2 1

[shared_ptr] 1.33 minor warning fix for MIPS Pro 7.4.1
by Kevin Wheatley 16 Aug '05

16 Aug '05

--- boost_1_33_0_mipspro_7.4.1/include/boost-1_33/boost/shared_ptr.hpp 2005-04-02 13:00:14.000000000 +0100 +++ boost_1_33_0/boost/shared_ptr.hpp 2005-08-16 10:50:40.000000000 +0100 @@ -87,9 +87,16 @@ if(pe != 0) pe->_internal_weak_this._internal_assign(const_cast<Y*>(px), pn); } +#ifdef sgi +// Turn off: the last argument of the varargs function "sp_enable_shared_from_this" is unnamed +#pragma set woff 3506 +#endif inline void sp_enable_shared_from_this( shared_count const & /*pn*/, ... ) { } +#ifdef sgi +#pragma reset woff 3506 +#endif } // namespace detail -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |

1 0

Re: [boost] Any (La)TeX experts here?
by Christoph Ludwig 16 Aug '05

16 Aug '05

On Mon, Aug 15, 2005 at 04:03:30PM -0400, Daryle Walker wrote: > On 8/14/05 6:34 AM, "Christoph Ludwig" > <cludwig(a)cdc.informatik.tu-darmstadt.de> wrote: > > [SNIP my original] > > I am willing to have look at your problem. But I couldn't find the document in > > the Boost Sandbox. Can you post a link or send me the file in private mail? > > And can you be somewhat more specific which formulas you consider too big? > [TRUNCATE] > > They're in CVS, try looking at: > > <http://cvs.sourceforge.net/viewcvs.py/boost-sandbox/boost-sandbox/libs/math > /doc/HyperComplex.bib?rev=1.1&view=log> > > <http://cvs.sourceforge.net/viewcvs.py/boost-sandbox/boost-sandbox/libs/math > /doc/HyperComplex.tex?rev=1.1&view=log> ah, I read "in the Sandbox" and followed the first link on the Boost Homepage that mentioned the Sandbox. I didn't realize there's a link "Sandbox Files" and some lines below "Sandbox CVS". Now I recall that it was mentioned before, so I am not the first one who missed the difference. Any chance either one gets renamed to make references to "the Sandbox" unambiguous? > (The server and my browser barfed when I tried the links off the second > URL.) I could download and LaTex / BibTeX them without problems, thanks. > (Some of the) Problems I see: [...] I will look into them tonight. Some problems seem to be pretty straightforward to solve (e.g., for (2) there is the package xspace), whereas the overflow problems may require some "creative TeXing". Let's see what I can come up with. Regards Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html

1 0

policy_ptr?
by Peter Dimov 16 Aug '05

16 Aug '05

The recent lively thread in comp.lang.c++.moderated has sparked my interest in the policy_ptr proposal. Is the final version of the submission available? -- Peter Dimov http://www.pdimov.com

3 9

Boost 1.33.0 released
by Doug Gregor 15 Aug '05

15 Aug '05

Boost 1.33.0 ------------ New Libraries * Iostreams Library: Framework for defining streams, stream buffers and i/o filters, from Jonathan Turkanis. * Functional/Hash Library: A TR1 hash function object that can be extended to hash user defined types, from Daniel James. * Parameter Library: Write functions that accept arguments by name: especially useful when a function has more than one argument with a useful default value, since named arguments can be passed in any order. * Pointer Container Library: Containers for storing heap-allocated polymorphic objects to ease OO-programming, from Thorsten Ottosen. * Wave: Standards conformant implementation of the mandated C99/C++ preprocessor functionality packed behind an easy to use iterator interface, from Hartmut Kaiser. Updated Libraries * Assignment Library: Support for Pointer Container Library and new efficient functions ref_list_of() and cref_list_of() for generating anonymous ranges. * Bind Library: Bind expressions now support comparisons and negation. Example: bind(&X::name, _1) < bind(&X::name, _2). * Date-Time Library: o Added local time and time zone classes. o Added format-based Input/Output facets. o For a complete list of changes, see the library change history. * Graph Library: Introduced several new algorithms and improved existing algorithms: o Experimental Python bindings, from Doug Gregor and Indiana University. o floyd_warshall_all_pairs_shortest_paths, from Lauren Foutz and Scott Hill. o astar_search, from Kristopher Beevers and Jufeng Peng. o fruchterman_reingold_force_directed_layout, from Doug Gregor and Indiana University. o biconnected_components and articulation_points, from Jeremy Siek, Janusz Piwowarski, and Doug Gregor. o sequential_vertex_coloring has been updated, tested, and documented. o gursoy_atun_layout, from Jeremiah Willcock and Doug Gregor of Indiana University. o king_ordering, from D. Kevin McGrath of Indiana University. o cuthill_mckee ordering has been recast as an invocation of breadth_first_search and now supports graphs with multiple components. o dijkstra_shortest_paths now uses a relaxed heap as its priority queue, improving its complexity to O(V log V) and improving real-world performance for larger graphs. o read_graphviz now has a new, Spirit-based parser that works for all graph types and supports arbitrary properties on the graph, from Ron Garcia. The old, Bison-based GraphViz reader has been deprecated and will be removed in a future Boost release. write_graphviz also supports dynamic properties. o subgraph: get_property now refers to the subgraph property, not the root graph's property. o See the history for additional changes and bug fixes. * Multi-index Containers Library: o New hashed indices. o Added serialization support. o For a complete list of changes, see the library release notes. * Program Options Library: o Option descriptions are now printed with word wrapping. o Command line parser can bypass unregistered options, instead of throwing. o Removed support for "implicit" (optional) values. o New customization method 'command_line_parser::extra_style_parser'. Unlike 'additional_parser', allows the user to parse several tokens and return a vector of options, not just a single option. o Work with disabled exceptions. * Property Map Library: Introduced the dynamic properties class, which provides dynamically-typed access to a set of property maps. * Random Number Library: improved initialization for mersenne_twister, algorithm by Makoto Matsumoto and Takuji Nishimura, implemented for Boost by Jens Maurer. Note: All test vectors for mersenne_twisters constructed or seeded without parameters or with a single unsigned int parameter become invalid. * Range Library: Minor addition of convenience functions to iterator range like front(), back() and operator[](). * Regex Library: o Rewritten front end parser now supports (?imsx-imsx) constructs, plus lookbehind assertions and conditional expressions. o Thin wrapper classes improve integration with MFC/ATL code. o Full (optional) Unicode support via the ICU library. Refer to the regex history page for more information on these and other small changes. * Serialization Library: o DLL version. o Auto-linking. o Serialization of variants. o Improved seialization of shared pointers. * Signals Library: added slot blocking/unblocking, from Frantz Maerten. Huge improvements to signal invocation performance from Robert Zeh. Supported Compilers Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. * Apple GCC 3.x on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0 beta. Note: due to intermittent problems with Visual C++ 8.0 beta, and the presence of a variety of pre-release compiler builds, we are unable to guarantee compatibility until the final compiler is released. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

8 14

Re: [boost] Any (La)TeX experts here?
by Christoph Ludwig 15 Aug '05

15 Aug '05

On Sun, Aug 14, 2005 at 05:35:09AM -0400, Daryle Walker wrote: > I tried using LaTeX within some Doxygen comments I added to a header I'm > trying out in the Sandbox. Then I decided to practice with LaTeX directly. > I made a version of the quaternion PDF papers in LaTeX in the Sandbox as > "libs/math/doc/HyperComplex.tex" with a corresponding *.bib file. (Now we > can correct the information in the future.) When I turned it into a PDF, > some of the formulas were way too big. Does anyone know how to fix them? I am willing to have look at your problem. But I couldn't find the document in the Boost Sandbox. Can you post a link or send me the file in private mail? And can you be somewhat more specific which formulas you consider too big? (If you have any LaTeX questions then it's always worth a try to post to the newsgroup comp.text.tex. The regulars there react somewhat testy only if you didn't check the FAQ <url:http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes>.) Regards Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html

2 1

Boost regression notification (2005-08-15)
by Douglas Gregor 15 Aug '05

15 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-15T15:37:30Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. disjoint_sets functional concept_check io array any utility conversion tokenizer dynamic_bitset format integer pool crc Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 1387 failures in 57 libraries: algorithm/minmax (2) algorithm/string (7) any (2) array (5) assign (11) bind (16) concept_check (2) config (5) conversion (3) crc (1) date_time (67) disjoint_sets (1) dynamic_bitset (4) filesystem (8) format (4) function (18) functional (1) functional/hash (15) graph (44) integer (3) io (1) iostreams (31) iterator (20) lambda (15) logic (3) math (5) mpl (88) multi_array (15) multi_index (21) numeric/conversion (6) numeric/interval (15) numeric/ublas (10) optional (4) parameter (109) pool (1) preprocessor (14) program_options (14) property_map (2) ptr_container (12) random (1) range (9) rational (2) regex (39) serialization (459) signals (6) smart_ptr (9) spirit (111) static_assert (3) test (19) thread (16) timer (1) tokenizer (6) tuple (2) type_traits (67) utility (16) variant (12) wave (4) |algorithm/minmax| minmax: intel-win32-9_0 minmax_element: intel-win32-9_0 |algorithm/string| conv: intel-win32-9_0 find: intel-win32-9_0 predicate: intel-win32-9_0 regex: intel-win32-9_0 replace: intel-win32-9_0 split: intel-win32-9_0 trim: intel-win32-9_0 |any| any_test: intel-win32-9_0 any_to_ref_test: intel-win32-9_0 |array| array1: intel-win32-9_0 array2: intel-win32-9_0 array3: intel-win32-9_0 array4: intel-win32-9_0 array5: intel-win32-9_0 |assign| basic: intel-win32-9_0 email_example: intel-win32-9_0 list_inserter: intel-win32-9_0 list_of_workaround: intel-win32-9_0 multi_index_container: intel-win32-9_0 my_vector_example: intel-win32-9_0 ptr_list_inserter: intel-win32-9_0 ptr_list_of: intel-win32-9_0 static_list_of: intel-win32-9_0 std: intel-win32-9_0 tuple_list_of: intel-win32-9_0 |bind| bind_const_test: intel-win32-9_0 bind_cv_test: intel-win32-9_0 bind_dm2_test: intel-win32-9_0 bind_dm_test: intel-win32-9_0 bind_eq_test: intel-win32-9_0 bind_function_test: intel-win32-9_0 bind_lookup_problem_test: intel-win32-9_0 bind_not_test: intel-win32-9_0 bind_rel_test: intel-win32-9_0 bind_stateful_test: intel-win32-9_0 bind_test: intel-win32-9_0 mem_fn_derived_test: intel-win32-9_0 mem_fn_dm_test: intel-win32-9_0 mem_fn_eq_test: intel-win32-9_0 mem_fn_test: intel-win32-9_0 mem_fn_void_test: intel-win32-9_0 |concept_check| class_concept_check_test: intel-win32-9_0 concept_check_test: intel-win32-9_0 |config| abi_test: intel-win32-9_0 config_info: intel-win32-9_0 config_link_test: intel-win32-9_0 config_test: intel-win32-9_0 limits_test: intel-win32-9_0 |conversion| cast_test: intel-win32-9_0 implicit_cast: intel-win32-9_0 lexical_cast_test: intel-win32-9_0 |crc| crc_test: intel-win32-9_0 |date_time| testc_local_adjustor: intel-win32-9_0 testclock: intel-win32-9_0 testclocks: intel-win32-9_0 testconstrained_value: intel-win32-9_0 testcustom_time_zone: intel-win32-9_0 testdate: intel-win32-9_0 testdate_dll: intel-win32-9_0 testdate_duration: intel-win32-9_0 testdate_duration_dll: intel-win32-9_0 testdate_facet_new: intel-win32-9_0 testdate_facet_new_dll: intel-win32-9_0 testdate_input_facet: intel-win32-9_0 testdate_input_facet_dll: intel-win32-9_0 testdate_iterator: intel-win32-9_0 testdate_iterator_dll: intel-win32-9_0 testdst_rules: intel-win32-9_0 testdst_transition_day_rule: intel-win32-9_0 testduration: intel-win32-9_0 testfacet: intel-win32-9_0 testfacet_dll: intel-win32-9_0 testfiletime_functions: intel-win32-9_0 testformatters: intel-win32-9_0 testformatters_dll: intel-win32-9_0 testgenerators: intel-win32-9_0 testgenerators_dll: intel-win32-9_0 testgeneric_period: intel-win32-9_0 testgreg_cal: intel-win32-9_0 testgreg_cal_dll: intel-win32-9_0 testgreg_day: intel-win32-9_0 testgreg_day_dll: intel-win32-9_0 testgreg_duration_operators: intel-win32-9_0 testgreg_durations: intel-win32-9_0 testgreg_durations_dll: intel-win32-9_0 testgreg_month: intel-win32-9_0 testgreg_month_dll: intel-win32-9_0 testgreg_serialize: intel-win32-9_0 testgreg_serialize_xml: intel-win32-9_0 testgreg_wstream: intel-win32-9_0 testgreg_year: intel-win32-9_0 testgreg_year_dll: intel-win32-9_0 testgregorian_calendar: intel-win32-9_0 testint_adapter: intel-win32-9_0 testiterator: intel-win32-9_0 testlocal_adjustor: intel-win32-9_0 testlocal_time: intel-win32-9_0 testlocal_time_facet: intel-win32-9_0 testlocal_time_input_facet: intel-win32-9_0 testmicrosec_time_clock: intel-win32-9_0 testparse_date: intel-win32-9_0 testparse_time: intel-win32-9_0 testperiod: intel-win32-9_0 testperiod_dll: intel-win32-9_0 testposix_time_zone: intel-win32-9_0 teststreams: intel-win32-9_0 testtime: intel-win32-9_0 testtime_facet: intel-win32-9_0 testtime_formatters: intel-win32-9_0 testtime_input_facet: intel-win32-9_0 testtime_period: intel-win32-9_0 testtime_resolution_traits: intel-win32-9_0 testtime_serialize: intel-win32-9_0 testtime_serialize_std_config: intel-win32-9_0 testtime_serialize_xml: intel-win32-9_0 testtime_serialize_xml_std_config: intel-win32-9_0 testtime_wstream: intel-win32-9_0 testtz_database: intel-win32-9_0 testwrapping_int: intel-win32-9_0 |disjoint_sets| disjoint_set_test: intel-win32-9_0 |dynamic_bitset| dyn_bitset_unit_tests1: intel-win32-9_0 dyn_bitset_unit_tests2: intel-win32-9_0 dyn_bitset_unit_tests3: intel-win32-9_0 dyn_bitset_unit_tests4: intel-win32-9_0 |filesystem| convenience_test: intel-win32-9_0 default_name_check_test: intel-win32-9_0 fstream_test: intel-win32-9_0 large_file_support_test: intel-win32-9_0 operations_test: intel-win32-9_0 operations_test_dll: intel-win32-9_0 path_test: intel-win32-9_0 path_test_dll: intel-win32-9_0 |format| format_test1: intel-win32-9_0 format_test2: intel-win32-9_0 format_test3: intel-win32-9_0 format_test_wstring: intel-win32-9_0 |function| allocator_test: intel-win32-9_0 contains2_test: intel-win32-9_0 contains_test: intel-win32-9_0 function_30: intel-win32-9_0 function_arith_cxx98: intel-win32-9_0 function_arith_portable: intel-win32-9_0 function_n_test: intel-win32-9_0 function_ref_cxx98: intel-win32-9_0 function_ref_portable: intel-win32-9_0 lambda_test: intel-win32-9_0 lib_function_test: intel-win32-9_0 mem_fun_cxx98: intel-win32-9_0 mem_fun_portable: intel-win32-9_0 stateless_test: intel-win32-9_0 std_bind_cxx98: intel-win32-9_0 std_bind_portable: intel-win32-9_0 sum_avg_cxx98: intel-win32-9_0 sum_avg_portable: intel-win32-9_0 |functional| function_test: intel-win32-9_0 |functional/hash| hash_built_in_array_test: intel-win32-9_0 hash_custom_test: intel-win32-9_0 hash_deque_test: intel-win32-9_0 hash_float_test: intel-win32-9_0 hash_function_pointer_test: intel-win32-9_0 hash_list_test: intel-win32-9_0 hash_map_test: intel-win32-9_0 hash_number_test: intel-win32-9_0 hash_pointer_test: intel-win32-9_0 hash_range_test: intel-win32-9_0 hash_set_test: intel-win32-9_0 hash_string_test: intel-win32-9_0 hash_value_array_test: intel-win32-9_0 hash_vector_test: intel-win32-9_0 link_test: intel-win32-9_0 |graph| adj_list_cc: intel-win32-9_0 adj_matrix_cc: intel-win32-9_0 adjacency_matrix_test: intel-win32-9_0 astar_search_test: intel-win32-9_0 bellman-test: intel-win32-9_0 betweenness_centrality_test: intel-win32-9_0 bfs: intel-win32-9_0 bfs_cc: intel-win32-9_0 biconnected_components_test: intel-win32-9_0 bundled_properties: intel-win32-9_0 copy: intel-win32-9_0 cuthill_mckee_ordering: intel-win32-9_0 dag_longest_paths: intel-win32-9_0 dfs: intel-win32-9_0 dfs_cc: intel-win32-9_0 dijkstra_cc: intel-win32-9_0 dijkstra_heap_performance: intel-win32-9_0 edge_list_cc: intel-win32-9_0 filtered_graph_cc: intel-win32-9_0 floyd_warshall_test: intel-win32-9_0 graph: intel-win32-9_0 graph_concepts: intel-win32-9_0 graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-win32-9_0 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 gursoy_atun_layout_test: intel-win32-9_0 isomorphism: intel-win32-9_0 king_ordering: intel-win32-9_0 property_iter: intel-win32-9_0 relaxed_heap_test: intel-win32-9_0 reverse_graph_cc: intel-win32-9_0 sequential_vertex_coloring: intel-win32-9_0 subgraph: intel-win32-9_0 transitive_closure_test: intel-win32-9_0 vector_graph_cc: intel-win32-9_0 |integer| cstdint_test: intel-win32-9_0 integer_test: intel-win32-9_0 integer_traits_test: intel-win32-9_0 |io| ios_state_test: intel-win32-9_0 |iostreams| array_test: intel-win32-9_0 auto_close_test: intel-win32-9_0 buffer_size_test: intel-win32-9_0 bzip2_test: mingw-3_4_2 code_converter_test: intel-win32-9_0 component_access_test: intel-win32-9_0 compose_test: intel-win32-9_0 copy_test: intel-win32-9_0 counter_test: intel-win32-9_0 direct_adapter_test: intel-win32-9_0 example_test: intel-win32-9_0 file_descriptor_test: intel-win32-9_0 filtering_stream_test: intel-win32-9_0 finite_state_filter_test: intel-win32-9_0 flush_test: intel-win32-9_0 gzip_test: mingw-3_4_2 invert_test: intel-win32-9_0 line_filter_test: intel-win32-9_0 newline_test: intel-win32-9_0 null_test: intel-win32-9_0 pipeline_test: intel-win32-9_0 positioning_test: intel-win32-9_0 regex_filter_test: intel-win32-9_0 restrict_test: intel-win32-9_0 seekable_file_test: intel-win32-9_0 seekable_filter_test: intel-win32-9_0 stdio_filter_test: intel-win32-9_0 symmetric_filter_test: intel-win32-9_0 tee_test: intel-win32-9_0 wide_stream_test: intel-win32-9_0 zlib_test: mingw-3_4_2 |iterator| concept_tests: intel-win32-9_0 counting_iterator_test: intel-win32-9_0 filter_iterator_test: intel-win32-9_0 indirect_iter_member_types: intel-win32-9_0 indirect_iterator_test: intel-win32-9_0 interoperable: intel-win32-9_0 is_convertible_fail: intel-win32-9_0 is_lvalue_iterator: intel-win32-9_0 is_readable_iterator: intel-win32-9_0 iterator_adaptor_cc: intel-win32-9_0 iterator_adaptor_test: intel-win32-9_0 iterator_archetype_cc: intel-win32-9_0 iterator_facade: intel-win32-9_0 iterator_traits_test: intel-win32-9_0 permutation_iterator_test: intel-win32-9_0 pointee: intel-win32-9_0 reverse_iterator_test: intel-win32-9_0 transform_iterator_test: intel-win32-9_0 unit_tests: intel-win32-9_0 zip_iterator_test: intel-win32-9_0 |lambda| algorithm_test: intel-win32-9_0 bind_tests_advanced: intel-win32-9_0 bind_tests_simple: intel-win32-9_0 bind_tests_simple_f_refs: intel-win32-9_0 bll_and_function: intel-win32-9_0 constructor_tests: intel-win32-9_0 control_structures: intel-win32-9_0 exception_test: intel-win32-9_0 extending_rt_traits: intel-win32-9_0 is_instance_of_test: intel-win32-9_0 lambda_cast_test: intel-win32-9_0 member_pointer_test: intel-win32-9_0 operator_tests_simple: intel-win32-9_0 phoenix_control_structures: intel-win32-9_0 switch_construct: intel-win32-9_0 |logic| tribool_io_test: intel-win32-9_0 tribool_rename_test: intel-win32-9_0 tribool_test: intel-win32-9_0 |math| common_factor_test: intel-win32-9_0 octonion_test: intel-win32-9_0 quaternion_mult_incl_test: intel-win32-9_0 quaternion_test: intel-win32-9_0 special_functions_test: intel-win32-9_0 |mpl| advance: intel-win32-9_0 always: intel-win32-9_0 apply: intel-win32-9_0 apply_wrap: intel-win32-9_0 arithmetic: intel-win32-9_0 as_sequence: intel-win32-9_0 assert: intel-win32-9_0 at: intel-win32-9_0 back: intel-win32-9_0 bind: intel-win32-9_0 bitwise: intel-win32-9_0 bool: intel-win32-9_0 comparison: intel-win32-9_0 contains: intel-win32-9_0 copy: intel-win32-9_0 copy_if: intel-win32-9_0 count: intel-win32-9_0 count_if: intel-win32-9_0 deque: intel-win32-9_0 distance: intel-win32-9_0 empty: intel-win32-9_0 equal: intel-win32-9_0 erase: intel-win32-9_0 erase_range: intel-win32-9_0 eval_if: intel-win32-9_0 filter_view: intel-win32-9_0 find: intel-win32-9_0 find_if: intel-win32-9_0 fold: intel-win32-9_0 for_each: intel-win32-9_0 front: intel-win32-9_0 has_xxx: intel-win32-9_0 identity: intel-win32-9_0 if: intel-win32-9_0 index_of: intel-win32-9_0 inherit: intel-win32-9_0 insert: intel-win32-9_0 insert_range: intel-win32-9_0 int: intel-win32-9_0 integral_c: intel-win32-9_0 is_placeholder: intel-win32-9_0 is_sequence: intel-win32-9_0 iterator_tags: intel-win32-9_0 joint_view: intel-win32-9_0 lambda: intel-win32-9_0 lambda_args: intel-win32-9_0 largest_int: intel-win32-9_0 list: intel-win32-9_0 list_c: intel-win32-9_0 logical: intel-win32-9_0 lower_bound: intel-win32-9_0 map: intel-win32-9_0 max_element: intel-win32-9_0 min_max: intel-win32-9_0 msvc_is_class: intel-win32-9_0 multiset: intel-win32-9_0 next: intel-win32-9_0 no_has_xxx: intel-win32-9_0 numeric_ops: intel-win32-9_0 pair_view: intel-win32-9_0 partition: intel-win32-9_0 pop_front: intel-win32-9_0 push_front: intel-win32-9_0 quote: intel-win32-9_0 range_c: intel-win32-9_0 remove: intel-win32-9_0 remove_if: intel-win32-9_0 replace: intel-win32-9_0 replace_if: intel-win32-9_0 reverse: intel-win32-9_0 same_as: intel-win32-9_0 set: intel-win32-9_0 set_c: intel-win32-9_0 single_view: intel-win32-9_0 size: intel-win32-9_0 size_t: intel-win32-9_0 sizeof: intel-win32-9_0 sort: intel-win32-9_0 stable_partition: intel-win32-9_0 template_arity: intel-win32-9_0 transform: intel-win32-9_0 transform_view: intel-win32-9_0 unique: intel-win32-9_0 unpack_args: intel-win32-9_0 upper_bound: intel-win32-9_0 vector: intel-win32-9_0 vector_c: intel-win32-9_0 zip_view: intel-win32-9_0 |multi_array| access: intel-win32-9_0 assign: intel-win32-9_0 assign_to_array: intel-win32-9_0 compare: intel-win32-9_0 concept_checks: intel-win32-9_0 constructors: intel-win32-9_0 idxgen1: intel-win32-9_0 index_bases: intel-win32-9_0 iterators: intel-win32-9_0 range1: intel-win32-9_0 reshape: intel-win32-9_0 resize: intel-win32-9_0 slice: intel-win32-9_0 stl_interaction: intel-win32-9_0 storage_order: intel-win32-9_0 |multi_index| test_basic: intel-win32-9_0 test_capacity: intel-win32-9_0 test_comparison: intel-win32-9_0 test_composite_key: intel-win32-9_0 test_conv_iterators: intel-win32-9_0 test_copy_assignment: intel-win32-9_0 test_hash_ops: intel-win32-9_0 test_iterators: intel-win32-9_0 test_key_extractors: intel-win32-9_0 test_list_ops: intel-win32-9_0 test_modifiers: intel-win32-9_0 test_mpl_ops: intel-win32-9_0 test_observers: intel-win32-9_0 test_projection: intel-win32-9_0 test_range: intel-win32-9_0 test_safe_mode: intel-win32-9_0 test_serialization: intel-win32-9_0 test_set_ops: intel-win32-9_0 test_special_list_ops: intel-win32-9_0 test_special_set_ops: intel-win32-9_0 test_update: intel-win32-9_0 |numeric/conversion| bounds_test: intel-win32-9_0 converter_test: intel-win32-9_0 numeric_cast_test: intel-win32-9_0 traits_test: intel-win32-9_0 udt_example_0: intel-win32-9_0 udt_support_test: intel-win32-9_0 |numeric/interval| add: intel-win32-9_0 cmp: intel-win32-9_0 cmp_exn: intel-win32-9_0 cmp_exp: intel-win32-9_0 cmp_lex: intel-win32-9_0 cmp_set: intel-win32-9_0 cmp_tribool: intel-win32-9_0 det: intel-win32-9_0 fmod: intel-win32-9_0 integer: intel-win32-9_0 mul: intel-win32-9_0 overflow: intel-win32-9_0 pi: intel-win32-9_0 pow: intel-win32-9_0 test_float: intel-win32-9_0 |numeric/ublas| concepts: intel-win32-9_0 placement_new: intel-win32-9_0 test1: intel-win32-9_0 test2: intel-win32-9_0 test3: intel-8.1-linux intel-win32-9_0 intel-win32-9_0 test4: intel-win32-9_0 test5: intel-win32-9_0 test6: intel-win32-9_0 |optional| optional_test: intel-win32-9_0 optional_test_inplace: intel-win32-9_0 optional_test_ref: intel-win32-9_0 optional_test_tie: intel-win32-9_0 |parameter| basics: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 macros: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 sfinae: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 unnamed: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-6_5 vc-6_5-stlport vc-7_0 vc-7_1 vc-7_1 vc-7_1 unwrap_cv_reference: intel-win32-9_0 |pool| test_pool_alloc: intel-win32-9_0 |preprocessor| arithmetic: intel-win32-9_0 array: intel-win32-9_0 comparison: intel-win32-9_0 control: intel-win32-9_0 debug: intel-win32-9_0 facilities: intel-win32-9_0 iteration: intel-win32-9_0 list: intel-win32-9_0 logical: intel-win32-9_0 repetition: intel-win32-9_0 selection: intel-win32-9_0 seq: intel-win32-9_0 slot: intel-win32-9_0 tuple: intel-win32-9_0 |program_options| cmdline_test: intel-win32-9_0 cmdline_test_dll: intel-win32-9_0 options_description_test: intel-win32-9_0 options_description_test_dll: intel-win32-9_0 parsers_test: intel-win32-9_0 parsers_test_dll: intel-win32-9_0 positional_options_test: intel-win32-9_0 positional_options_test_dll: intel-win32-9_0 unicode_test: intel-win32-9_0 unicode_test_dll: intel-win32-9_0 variable_map_test: intel-win32-9_0 variable_map_test_dll: intel-win32-9_0 winmain: intel-win32-9_0 winmain_dll: intel-win32-9_0 |property_map| dynamic_properties_test: intel-win32-9_0 property_map_cc: intel-win32-9_0 |ptr_container| incomplete_type_test: intel-win32-9_0 indirect_fun: intel-win32-9_0 iterator_test: intel-win32-9_0 ptr_array: intel-win32-9_0 ptr_deque: intel-win32-9_0 ptr_list: intel-win32-9_0 ptr_map: intel-win32-9_0 ptr_set: intel-win32-9_0 ptr_vector: intel-win32-9_0 tree_test: intel-win32-9_0 tut1: intel-win32-9_0 view_example: intel-win32-9_0 |random| random_demo: intel-win32-9_0 |range| algorithm_example: intel-win32-9_0 array: intel-win32-9_0 const_ranges: intel-win32-9_0 iterator_pair: intel-win32-9_0 iterator_range: intel-win32-9_0 reversible_range: intel-win32-9_0 std_container: intel-win32-9_0 string: intel-win32-9_0 sub_range: intel-win32-9_0 |rational| rational_example: intel-win32-9_0 rational_test: intel-win32-9_0 |regex| bad_expression_test: intel-win32-9_0 captures_example: intel-win32-9_0 captures_test: intel-win32-9_0 collate_info: intel-win32-9_0 concept_check: gcc-3.2.3-linux intel-win32-9_0 credit_card_example: intel-win32-9_0 grep: intel-win32-9_0 icu_concept_check: intel-win32-9_0 icu_example: intel-win32-9_0 mfc_example: intel-win32-9_0 object_cache_test: intel-win32-9_0 partial_regex_grep: intel-win32-9_0 partial_regex_match: intel-win32-9_0 posix_api_check: intel-win32-9_0 posix_api_check_cpp: intel-win32-9_0 recursion_test: intel-win32-9_0 regex_config_info: intel-win32-9_0 regex_dll_config_info: intel-win32-9_0 regex_grep_example_1: intel-win32-9_0 regex_grep_example_2: intel-win32-9_0 regex_grep_example_3: intel-win32-9_0 regex_grep_example_4: intel-win32-9_0 regex_iterator_example: intel-win32-9_0 regex_match_example: intel-win32-9_0 regex_merge_example: intel-win32-9_0 regex_regress: intel-win32-9_0 regex_regress_dll: intel-win32-9_0 regex_replace_example: intel-win32-9_0 regex_search_example: intel-win32-9_0 regex_split_example_1: intel-win32-9_0 regex_split_example_2: intel-win32-9_0 regex_timer: intel-win32-9_0 regex_token_iterator_eg_1: intel-win32-9_0 regex_token_iterator_eg_2: intel-win32-9_0 static_mutex_test: intel-win32-9_0 unicode_iterator_test: intel-win32-9_0 wide_posix_api_check_c: intel-win32-9_0 wide_posix_api_check_cpp: intel-win32-9_0 |serialization| test_array_binary_archive: intel-win32-9_0 test_array_binary_archive_dll: intel-win32-9_0 test_array_text_archive: intel-win32-9_0 test_array_text_archive_dll: intel-win32-9_0 test_array_text_warchive: intel-win32-9_0 test_array_text_warchive_dll: intel-win32-9_0 test_array_xml_archive: intel-win32-9_0 test_array_xml_archive_dll: intel-win32-9_0 test_array_xml_warchive: intel-win32-9_0 test_array_xml_warchive_dll: intel-win32-9_0 test_binary_binary_archive: intel-win32-9_0 test_binary_binary_archive_dll: intel-win32-9_0 test_binary_text_archive: intel-win32-9_0 test_binary_text_archive_dll: intel-win32-9_0 test_binary_text_warchive: intel-win32-9_0 test_binary_text_warchive_dll: intel-win32-9_0 test_binary_xml_archive: intel-win32-9_0 test_binary_xml_archive_dll: intel-win32-9_0 test_binary_xml_warchive: intel-win32-9_0 test_binary_xml_warchive_dll: intel-win32-9_0 test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_text_archive: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_text_archive_dll: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_text_warchive: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_text_warchive_dll: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_xml_warchive: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_load_xml_warchive_dll: gcc-3_4_3-sunos intel-win32-9_0 test_class_info_save_binary_archive: intel-win32-9_0 test_class_info_save_binary_archive_dll: intel-win32-9_0 test_class_info_save_text_archive: intel-win32-9_0 test_class_info_save_text_archive_dll: intel-win32-9_0 test_class_info_save_text_warchive: intel-win32-9_0 test_class_info_save_text_warchive_dll: intel-win32-9_0 test_class_info_save_xml_archive: intel-win32-9_0 test_class_info_save_xml_archive_dll: intel-win32-9_0 test_class_info_save_xml_warchive: intel-win32-9_0 test_class_info_save_xml_warchive_dll: intel-win32-9_0 test_codecvt_null: intel-win32-9_0 test_const_pass: intel-win32-9_0 test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_contained_class_binary_archive: intel-win32-9_0 test_contained_class_binary_archive_dll: intel-win32-9_0 test_contained_class_text_archive: intel-win32-9_0 test_contained_class_text_archive_dll: intel-win32-9_0 test_contained_class_text_warchive: intel-win32-9_0 test_contained_class_text_warchive_dll: intel-win32-9_0 test_contained_class_xml_archive: intel-win32-9_0 test_contained_class_xml_archive_dll: intel-win32-9_0 test_contained_class_xml_warchive: intel-win32-9_0 test_contained_class_xml_warchive_dll: intel-win32-9_0 test_cyclic_ptrs_binary_archive: intel-win32-9_0 test_cyclic_ptrs_binary_archive_dll: intel-win32-9_0 test_cyclic_ptrs_text_archive: intel-win32-9_0 test_cyclic_ptrs_text_archive_dll: intel-win32-9_0 test_cyclic_ptrs_text_warchive: intel-win32-9_0 test_cyclic_ptrs_text_warchive_dll: intel-win32-9_0 test_cyclic_ptrs_xml_archive: intel-win32-9_0 test_cyclic_ptrs_xml_archive_dll: intel-win32-9_0 test_cyclic_ptrs_xml_warchive: intel-win32-9_0 test_cyclic_ptrs_xml_warchive_dll: intel-win32-9_0 test_delete_pointer_binary_archive: intel-win32-9_0 test_delete_pointer_binary_archive_dll: intel-win32-9_0 test_delete_pointer_text_archive: intel-win32-9_0 test_delete_pointer_text_archive_dll: intel-win32-9_0 test_delete_pointer_text_warchive: intel-win32-9_0 test_delete_pointer_text_warchive_dll: intel-win32-9_0 test_delete_pointer_xml_archive: intel-win32-9_0 test_delete_pointer_xml_archive_dll: intel-win32-9_0 test_delete_pointer_xml_warchive: intel-win32-9_0 test_delete_pointer_xml_warchive_dll: intel-win32-9_0 test_demo: intel-win32-9_0 test_demo_auto_ptr: intel-win32-9_0 test_demo_auto_ptr_dll: intel-win32-9_0 test_demo_dll: intel-win32-9_0 test_demo_exception: intel-win32-9_0 test_demo_exception_dll: intel-win32-9_0 test_demo_fast_archive: intel-win32-9_0 test_demo_fast_archive_dll: intel-win32-9_0 test_demo_pimpl: intel-win32-9_0 test_demo_pimpl_dll: intel-win32-9_0 test_demo_polymorphic: intel-win32-9_0 test_demo_polymorphic_dll: intel-win32-9_0 test_demo_portable_archive: intel-win32-9_0 test_demo_shared_ptr: intel-win32-9_0 test_demo_shared_ptr_dll: intel-win32-9_0 test_demo_xml: intel-win32-9_0 test_demo_xml_dll: intel-win32-9_0 test_demo_xml_load: intel-win32-9_0 test_demo_xml_load_dll: intel-win32-9_0 test_demo_xml_save: intel-win32-9_0 test_demo_xml_save_dll: intel-win32-9_0 test_deque_binary_archive: intel-win32-9_0 test_deque_binary_archive_dll: intel-win32-9_0 test_deque_text_archive: intel-win32-9_0 test_deque_text_archive_dll: intel-win32-9_0 test_deque_text_warchive: intel-win32-9_0 test_deque_text_warchive_dll: intel-win32-9_0 test_deque_xml_archive: intel-win32-9_0 test_deque_xml_archive_dll: intel-win32-9_0 test_deque_xml_warchive: intel-win32-9_0 test_deque_xml_warchive_dll: intel-win32-9_0 test_derived_binary_archive: intel-win32-9_0 test_derived_binary_archive_dll: intel-win32-9_0 test_derived_class_binary_archive: intel-win32-9_0 test_derived_class_binary_archive_dll: intel-win32-9_0 test_derived_class_ptr_binary_archive: intel-win32-9_0 test_derived_class_ptr_binary_archive_dll: intel-win32-9_0 test_derived_class_ptr_text_archive: intel-win32-9_0 test_derived_class_ptr_text_archive_dll: intel-win32-9_0 test_derived_class_ptr_text_warchive: intel-win32-9_0 test_derived_class_ptr_text_warchive_dll: intel-win32-9_0 test_derived_class_ptr_xml_archive: intel-win32-9_0 test_derived_class_ptr_xml_archive_dll: intel-win32-9_0 test_derived_class_ptr_xml_warchive: intel-win32-9_0 test_derived_class_ptr_xml_warchive_dll: intel-win32-9_0 test_derived_class_text_archive: intel-win32-9_0 test_derived_class_text_archive_dll: intel-win32-9_0 test_derived_class_text_warchive: intel-win32-9_0 test_derived_class_text_warchive_dll: intel-win32-9_0 test_derived_class_xml_archive: intel-win32-9_0 test_derived_class_xml_archive_dll: intel-win32-9_0 test_derived_class_xml_warchive: intel-win32-9_0 test_derived_class_xml_warchive_dll: intel-win32-9_0 test_derived_text_archive: intel-win32-9_0 test_derived_text_archive_dll: intel-win32-9_0 test_derived_text_warchive: intel-win32-9_0 test_derived_text_warchive_dll: intel-win32-9_0 test_derived_xml_archive: intel-win32-9_0 test_derived_xml_archive_dll: intel-win32-9_0 test_derived_xml_warchive: intel-win32-9_0 test_derived_xml_warchive_dll: intel-win32-9_0 test_diamond_binary_archive: intel-win32-9_0 test_diamond_binary_archive_dll: intel-win32-9_0 test_diamond_text_archive: intel-win32-9_0 test_diamond_text_archive_dll: intel-win32-9_0 test_diamond_text_warchive: intel-win32-9_0 test_diamond_text_warchive_dll: intel-win32-9_0 test_diamond_xml_archive: intel-win32-9_0 test_diamond_xml_archive_dll: intel-win32-9_0 test_diamond_xml_warchive: intel-win32-9_0 test_diamond_xml_warchive_dll: intel-win32-9_0 test_exported_binary_archive: intel-win32-9_0 test_exported_binary_archive_dll: intel-win32-9_0 test_exported_text_archive: intel-win32-9_0 test_exported_text_archive_dll: intel-win32-9_0 test_exported_text_warchive: intel-win32-9_0 test_exported_text_warchive_dll: intel-win32-9_0 test_exported_xml_archive: intel-win32-9_0 test_exported_xml_archive_dll: intel-win32-9_0 test_exported_xml_warchive: intel-win32-9_0 test_exported_xml_warchive_dll: intel-win32-9_0 test_inclusion: intel-win32-9_0 test_iterators: intel-win32-9_0 test_iterators_base64: intel-win32-9_0 test_list_binary_archive: intel-win32-9_0 test_list_binary_archive_dll: intel-win32-9_0 test_list_ptrs_binary_archive: intel-win32-9_0 test_list_ptrs_binary_archive_dll: intel-win32-9_0 test_list_ptrs_text_archive: intel-win32-9_0 test_list_ptrs_text_archive_dll: intel-win32-9_0 test_list_ptrs_text_warchive: intel-win32-9_0 test_list_ptrs_text_warchive_dll: intel-win32-9_0 test_list_ptrs_xml_archive: intel-win32-9_0 test_list_ptrs_xml_archive_dll: intel-win32-9_0 test_list_ptrs_xml_warchive: intel-win32-9_0 test_list_ptrs_xml_warchive_dll: intel-win32-9_0 test_list_text_archive: intel-win32-9_0 test_list_text_archive_dll: intel-win32-9_0 test_list_text_warchive: intel-win32-9_0 test_list_text_warchive_dll: intel-win32-9_0 test_list_xml_archive: intel-win32-9_0 test_list_xml_archive_dll: intel-win32-9_0 test_list_xml_warchive: intel-win32-9_0 test_list_xml_warchive_dll: intel-win32-9_0 test_map_binary_archive: intel-win32-9_0 test_map_binary_archive_dll: intel-win32-9_0 msvc test_map_text_archive: intel-win32-9_0 test_map_text_archive_dll: intel-win32-9_0 msvc test_map_text_warchive: intel-win32-9_0 test_map_text_warchive_dll: intel-win32-9_0 msvc test_map_xml_archive: intel-win32-9_0 test_map_xml_archive_dll: intel-win32-9_0 test_map_xml_warchive: intel-win32-9_0 test_map_xml_warchive_dll: intel-win32-9_0 test_mi_binary_archive: intel-win32-9_0 test_mi_binary_archive_dll: intel-win32-9_0 test_mi_text_archive: intel-win32-9_0 test_mi_text_archive_dll: intel-win32-9_0 test_mi_text_warchive: intel-win32-9_0 test_mi_text_warchive_dll: intel-win32-9_0 test_mi_xml_archive: intel-win32-9_0 test_mi_xml_archive_dll: intel-win32-9_0 test_mi_xml_warchive: intel-win32-9_0 test_mi_xml_warchive_dll: intel-win32-9_0 test_mult_archive_types: intel-win32-9_0 test_mult_archive_types_dll: intel-win32-9_0 test_multiple_ptrs_binary_archive: intel-win32-9_0 test_multiple_ptrs_binary_archive_dll: intel-win32-9_0 test_multiple_ptrs_text_archive: intel-win32-9_0 test_multiple_ptrs_text_archive_dll: intel-win32-9_0 test_multiple_ptrs_text_warchive: intel-win32-9_0 test_multiple_ptrs_text_warchive_dll: intel-win32-9_0 test_multiple_ptrs_xml_archive: intel-win32-9_0 test_multiple_ptrs_xml_archive_dll: intel-win32-9_0 test_multiple_ptrs_xml_warchive: intel-win32-9_0 test_multiple_ptrs_xml_warchive_dll: intel-win32-9_0 test_no_rtti_binary_archive: intel-win32-9_0 test_no_rtti_binary_archive_dll: intel-win32-9_0 test_no_rtti_text_archive: intel-win32-9_0 test_no_rtti_text_archive_dll: intel-win32-9_0 test_no_rtti_text_warchive: intel-win32-9_0 test_no_rtti_text_warchive_dll: intel-win32-9_0 test_no_rtti_xml_archive: intel-win32-9_0 test_no_rtti_xml_archive_dll: intel-win32-9_0 test_no_rtti_xml_warchive: intel-win32-9_0 test_no_rtti_xml_warchive_dll: intel-win32-9_0 test_non_default_ctor2_binary_archive: intel-win32-9_0 test_non_default_ctor2_binary_archive_dll: intel-win32-9_0 test_non_default_ctor2_text_archive: intel-win32-9_0 test_non_default_ctor2_text_archive_dll: intel-win32-9_0 test_non_default_ctor2_text_warchive: intel-win32-9_0 test_non_default_ctor2_text_warchive_dll: intel-win32-9_0 test_non_default_ctor2_xml_archive: intel-win32-9_0 test_non_default_ctor2_xml_archive_dll: intel-win32-9_0 test_non_default_ctor2_xml_warchive: intel-win32-9_0 test_non_default_ctor2_xml_warchive_dll: intel-win32-9_0 test_non_default_ctor_binary_archive: intel-win32-9_0 test_non_default_ctor_binary_archive_dll: intel-win32-9_0 test_non_default_ctor_text_archive: intel-win32-9_0 test_non_default_ctor_text_archive_dll: intel-win32-9_0 test_non_default_ctor_text_warchive: intel-win32-9_0 test_non_default_ctor_text_warchive_dll: intel-win32-9_0 test_non_default_ctor_xml_archive: intel-win32-9_0 test_non_default_ctor_xml_archive_dll: intel-win32-9_0 test_non_default_ctor_xml_warchive: intel-win32-9_0 test_non_default_ctor_xml_warchive_dll: intel-win32-9_0 test_non_intrusive_binary_archive: intel-win32-9_0 test_non_intrusive_binary_archive_dll: intel-win32-9_0 test_non_intrusive_text_archive: intel-win32-9_0 test_non_intrusive_text_archive_dll: intel-win32-9_0 test_non_intrusive_text_warchive: intel-win32-9_0 test_non_intrusive_text_warchive_dll: intel-win32-9_0 test_non_intrusive_xml_archive: intel-win32-9_0 test_non_intrusive_xml_archive_dll: intel-win32-9_0 test_non_intrusive_xml_warchive: intel-win32-9_0 test_non_intrusive_xml_warchive_dll: intel-win32-9_0 test_null_ptr_binary_archive: intel-win32-9_0 test_null_ptr_binary_archive_dll: intel-win32-9_0 test_null_ptr_text_archive: intel-win32-9_0 test_null_ptr_text_archive_dll: intel-win32-9_0 test_null_ptr_text_warchive: intel-win32-9_0 test_null_ptr_text_warchive_dll: intel-win32-9_0 test_null_ptr_xml_archive: intel-win32-9_0 test_null_ptr_xml_archive_dll: intel-win32-9_0 test_null_ptr_xml_warchive: intel-win32-9_0 test_null_ptr_xml_warchive_dll: intel-win32-9_0 test_nvp_binary_archive: intel-win32-9_0 test_nvp_binary_archive_dll: intel-win32-9_0 test_nvp_text_archive: intel-win32-9_0 test_nvp_text_archive_dll: intel-win32-9_0 test_nvp_text_warchive: intel-win32-9_0 test_nvp_text_warchive_dll: intel-win32-9_0 test_nvp_xml_archive: intel-win32-9_0 test_nvp_xml_archive_dll: intel-win32-9_0 test_nvp_xml_warchive: intel-win32-9_0 test_nvp_xml_warchive_dll: intel-win32-9_0 test_object_binary_archive: intel-win32-9_0 test_object_binary_archive_dll: intel-win32-9_0 test_object_text_archive: intel-win32-9_0 test_object_text_archive_dll: intel-win32-9_0 test_object_text_warchive: intel-win32-9_0 test_object_text_warchive_dll: intel-win32-9_0 test_object_xml_archive: intel-win32-9_0 test_object_xml_archive_dll: intel-win32-9_0 test_object_xml_warchive: intel-win32-9_0 test_object_xml_warchive_dll: intel-win32-9_0 test_optional_binary_archive: intel-win32-9_0 test_optional_binary_archive_dll: intel-win32-9_0 test_optional_text_archive: intel-win32-9_0 test_optional_text_archive_dll: intel-win32-9_0 test_optional_text_warchive: intel-win32-9_0 test_optional_text_warchive_dll: intel-win32-9_0 test_optional_xml_archive: intel-win32-9_0 test_optional_xml_archive_dll: intel-win32-9_0 test_optional_xml_warchive: intel-win32-9_0 test_optional_xml_warchive_dll: intel-win32-9_0 test_polymorphic_binary_archive: intel-win32-9_0 test_polymorphic_binary_archive_dll: intel-win32-9_0 test_polymorphic_text_archive: intel-win32-9_0 test_polymorphic_text_archive_dll: intel-win32-9_0 test_polymorphic_text_warchive: intel-win32-9_0 test_polymorphic_text_warchive_dll: intel-win32-9_0 test_polymorphic_xml_archive: intel-win32-9_0 test_polymorphic_xml_archive_dll: intel-win32-9_0 test_polymorphic_xml_warchive: intel-win32-9_0 test_polymorphic_xml_warchive_dll: intel-win32-9_0 test_primitive_binary_archive: intel-win32-9_0 test_primitive_binary_archive_dll: intel-win32-9_0 test_primitive_text_archive: intel-win32-9_0 test_primitive_text_archive_dll: intel-win32-9_0 test_primitive_text_warchive: intel-win32-9_0 test_primitive_text_warchive_dll: intel-win32-9_0 test_primitive_xml_archive: intel-win32-9_0 test_primitive_xml_archive_dll: intel-win32-9_0 test_primitive_xml_warchive: intel-win32-9_0 test_primitive_xml_warchive_dll: intel-win32-9_0 test_private_ctor: intel-win32-9_0 test_private_ctor_dll: intel-win32-9_0 test_recursion_binary_archive: intel-win32-9_0 test_recursion_binary_archive_dll: intel-win32-9_0 test_recursion_text_archive: intel-win32-9_0 test_recursion_text_archive_dll: intel-win32-9_0 test_recursion_text_warchive: intel-win32-9_0 test_recursion_text_warchive_dll: intel-win32-9_0 test_recursion_xml_archive: intel-win32-9_0 test_recursion_xml_archive_dll: intel-win32-9_0 test_recursion_xml_warchive: intel-win32-9_0 test_recursion_xml_warchive_dll: intel-win32-9_0 test_registered_binary_archive: intel-win32-9_0 test_registered_binary_archive_dll: intel-win32-9_0 test_registered_text_archive: intel-win32-9_0 test_registered_text_archive_dll: intel-win32-9_0 test_registered_text_warchive: intel-win32-9_0 test_registered_text_warchive_dll: intel-win32-9_0 test_registered_xml_archive: intel-win32-9_0 test_registered_xml_archive_dll: intel-win32-9_0 test_registered_xml_warchive: intel-win32-9_0 test_registered_xml_warchive_dll: intel-win32-9_0 test_reset_object_address: intel-win32-9_0 test_reset_object_address_dll: intel-win32-9_0 test_set_binary_archive: intel-win32-9_0 test_set_binary_archive_dll: intel-win32-9_0 test_set_text_archive: intel-win32-9_0 test_set_text_archive_dll: intel-win32-9_0 test_set_text_warchive: intel-win32-9_0 test_set_text_warchive_dll: intel-win32-9_0 test_set_xml_archive: intel-win32-9_0 test_set_xml_archive_dll: intel-win32-9_0 test_set_xml_warchive: intel-win32-9_0 test_set_xml_warchive_dll: intel-win32-9_0 test_shared_ptr_132_binary_archive: intel-win32-9_0 test_shared_ptr_132_binary_archive_dll: intel-win32-9_0 test_shared_ptr_132_text_archive: gcc-3.2.3-linux intel-win32-9_0 test_shared_ptr_132_text_archive_dll: intel-win32-9_0 test_shared_ptr_132_text_warchive: intel-win32-9_0 test_shared_ptr_132_text_warchive_dll: intel-win32-9_0 test_shared_ptr_132_xml_archive: intel-win32-9_0 test_shared_ptr_132_xml_archive_dll: intel-win32-9_0 test_shared_ptr_132_xml_warchive: intel-win32-9_0 test_shared_ptr_132_xml_warchive_dll: intel-win32-9_0 test_shared_ptr_binary_archive: intel-win32-9_0 test_shared_ptr_binary_archive_dll: intel-win32-9_0 test_shared_ptr_text_archive: intel-win32-9_0 test_shared_ptr_text_archive_dll: intel-win32-9_0 test_shared_ptr_text_warchive: intel-win32-9_0 test_shared_ptr_text_warchive_dll: intel-win32-9_0 test_shared_ptr_xml_archive: intel-win32-9_0 test_shared_ptr_xml_archive_dll: intel-win32-9_0 test_shared_ptr_xml_warchive: intel-win32-9_0 test_shared_ptr_xml_warchive_dll: intel-win32-9_0 test_simple_class_binary_archive: intel-win32-9_0 test_simple_class_binary_archive_dll: intel-win32-9_0 test_simple_class_ptr_binary_archive: intel-win32-9_0 test_simple_class_ptr_binary_archive_dll: intel-win32-9_0 test_simple_class_ptr_text_archive: intel-win32-9_0 test_simple_class_ptr_text_archive_dll: intel-win32-9_0 test_simple_class_ptr_text_warchive: intel-win32-9_0 test_simple_class_ptr_text_warchive_dll: intel-win32-9_0 test_simple_class_ptr_xml_archive: intel-win32-9_0 test_simple_class_ptr_xml_archive_dll: intel-win32-9_0 test_simple_class_ptr_xml_warchive: intel-win32-9_0 test_simple_class_ptr_xml_warchive_dll: intel-win32-9_0 test_simple_class_text_archive: intel-win32-9_0 test_simple_class_text_archive_dll: intel-win32-9_0 test_simple_class_text_warchive: intel-win32-9_0 test_simple_class_text_warchive_dll: intel-win32-9_0 test_simple_class_xml_archive: intel-win32-9_0 test_simple_class_xml_archive_dll: intel-win32-9_0 test_simple_class_xml_warchive: intel-win32-9_0 test_simple_class_xml_warchive_dll: intel-win32-9_0 test_smart_cast: intel-win32-9_0 test_split_binary_archive: intel-win32-9_0 test_split_binary_archive_dll: intel-win32-9_0 test_split_text_archive: intel-win32-9_0 test_split_text_archive_dll: intel-win32-9_0 test_split_text_warchive: intel-win32-9_0 test_split_text_warchive_dll: intel-win32-9_0 test_split_xml_archive: intel-win32-9_0 test_split_xml_archive_dll: intel-win32-9_0 test_split_xml_warchive: intel-win32-9_0 test_split_xml_warchive_dll: intel-win32-9_0 test_static_warning: intel-win32-9_0 test_tracking_binary_archive: intel-win32-9_0 test_tracking_binary_archive_dll: intel-win32-9_0 test_tracking_text_archive: intel-win32-9_0 test_tracking_text_archive_dll: intel-win32-9_0 test_tracking_text_warchive: intel-win32-9_0 test_tracking_text_warchive_dll: intel-win32-9_0 test_tracking_xml_archive: intel-win32-9_0 test_tracking_xml_archive_dll: intel-win32-9_0 test_tracking_xml_warchive: intel-win32-9_0 test_tracking_xml_warchive_dll: intel-win32-9_0 test_traits_pass: intel-win32-9_0 test_unregistered_binary_archive: intel-win32-9_0 test_unregistered_binary_archive_dll: intel-win32-9_0 test_unregistered_text_archive: intel-win32-9_0 test_unregistered_text_archive_dll: intel-win32-9_0 test_unregistered_text_warchive: intel-win32-9_0 test_unregistered_text_warchive_dll: intel-win32-9_0 test_unregistered_xml_archive: intel-win32-9_0 test_unregistered_xml_archive_dll: intel-win32-9_0 test_unregistered_xml_warchive: intel-win32-9_0 test_unregistered_xml_warchive_dll: intel-win32-9_0 test_utf8_codecvt: intel-win32-9_0 test_variant_binary_archive: intel-win32-9_0 test_variant_binary_archive_dll: intel-win32-9_0 test_variant_text_archive: intel-win32-9_0 test_variant_text_archive_dll: intel-win32-9_0 test_variant_text_warchive: intel-win32-9_0 test_variant_text_warchive_dll: intel-win32-9_0 test_variant_xml_archive: intel-win32-9_0 test_variant_xml_archive_dll: intel-win32-9_0 test_variant_xml_warchive: intel-win32-9_0 test_variant_xml_warchive_dll: intel-win32-9_0 test_vector_binary_archive: intel-win32-9_0 test_vector_binary_archive_dll: intel-win32-9_0 test_vector_text_archive: intel-win32-9_0 test_vector_text_archive_dll: intel-win32-9_0 test_vector_text_warchive: intel-win32-9_0 test_vector_text_warchive_dll: intel-win32-9_0 test_vector_xml_archive: intel-win32-9_0 test_vector_xml_archive_dll: intel-win32-9_0 test_vector_xml_warchive: intel-win32-9_0 test_vector_xml_warchive_dll: intel-win32-9_0 test_void_cast: intel-win32-9_0 test_void_cast_dll: intel-win32-9_0 |signals| dead_slot_test: intel-win32-9_0 deletion_test: intel-win32-9_0 ordering_test: intel-win32-9_0 signal_n_test: intel-win32-9_0 signal_test: intel-win32-9_0 trackable_test: intel-win32-9_0 |smart_ptr| atomic_count_test: intel-win32-9_0 get_deleter_test: intel-win32-9_0 intrusive_ptr_test: intel-win32-9_0 lw_mutex_test: intel-win32-9_0 shared_from_this_test: intel-win32-9_0 shared_ptr_basic_test: intel-win32-9_0 shared_ptr_test: intel-win32-9_0 smart_ptr_test: intel-win32-9_0 weak_ptr_test: intel-win32-9_0 |spirit| action_tests: intel-win32-9_0 action_tests_debug: intel-win32-9_0 ast_calc_tests: intel-win32-9_0 ast_calc_tests_debug: intel-win32-9_0 bug_000008: intel-win32-9_0 bug_fixes: intel-win32-9_0 bug_fixes_debug: intel-win32-9_0 char_strings_test: intel-win32-9_0 char_strings_test_debug: intel-win32-9_0 chset_tests: intel-win32-9_0 chset_tests_debug: intel-win32-9_0 closure_tests: intel-win32-9_0 closure_tests_debug: intel-win32-9_0 confix_tests: intel-win32-9_0 confix_tests_debug: intel-win32-9_0 directives_tests: intel-win32-9_0 directives_tests_debug: intel-win32-9_0 distinct_tests: intel-win32-9_0 distinct_tests_debug: intel-win32-9_0 epsilon_tests: intel-win32-9_0 epsilon_tests_debug: intel-win32-9_0 escape_char_parser_tests: intel-win32-9_0 escape_char_parser_tests_debug: intel-win32-9_0 exception_tests: intel-win32-9_0 exception_tests_debug: intel-win32-9_0 file_iterator_tests: intel-win32-9_0 file_iterator_tests_debug: intel-win32-9_0 fixed_size_queue_tests: intel-win32-9_0 fixed_size_queue_tests_debug: intel-win32-9_0 for_p_as_parser_tests: intel-win32-9_0 for_tests: intel-win32-9_0 for_tests_debug: intel-win32-9_0 fundamental_tests: intel-win32-9_0 fundamental_tests_debug: intel-win32-9_0 grammar_def_test: intel-win32-9_0 grammar_def_test_debug: intel-win32-9_0 grammar_mt_tests: intel-win32-9_0 grammar_multi_instance_tst: intel-win32-9_0 grammar_multi_instance_tst_debug: intel-win32-9_0 grammar_tests: intel-win32-9_0 grammar_tests_debug: intel-win32-9_0 group_match_bug: intel-win32-9_0 group_match_bug_debug: intel-win32-9_0 if_p_as_parser_tests: intel-win32-9_0 if_p_int_as_condition_test: intel-win32-9_0 if_p_int_as_condition_test_debug: intel-win32-9_0 if_tests: intel-win32-9_0 if_tests_debug: intel-win32-9_0 lazy_tests: intel-win32-9_0 lazy_tests_debug: intel-win32-9_0 loops_tests: intel-win32-9_0 loops_tests_debug: intel-win32-9_0 match_tests: intel-win32-9_0 match_tests_debug: intel-win32-9_0 multi_pass_compile_tests: intel-win32-9_0 multi_pass_tests: intel-win32-9_0 multi_pass_tests_debug: intel-win32-9_0 negated_eps_p_test: intel-win32-9_0 negated_eps_p_test_debug: intel-win32-9_0 numerics_tests: intel-win32-9_0 numerics_tests_debug: intel-win32-9_0 operators_tests: intel-win32-9_0 operators_tests_debug: intel-win32-9_0 owi_mt_tests: intel-win32-9_0 owi_st_tests: intel-win32-9_0 owi_st_tests_debug: intel-win32-9_0 parametric_tests: intel-win32-9_0 parametric_tests_debug: intel-win32-9_0 parser_context_test: intel-win32-9_0 parser_context_test_debug: intel-win32-9_0 parser_traits_tests: intel-win32-9_0 parser_traits_tests_debug: intel-win32-9_0 position_iterator_tests: intel-win32-9_0 position_iterator_tests_debug: intel-win32-9_0 primitives_tests: intel-win32-9_0 primitives_tests_debug: intel-win32-9_0 repeat_ast_tests: intel-win32-9_0 repeat_ast_tests_debug: intel-win32-9_0 rule_tests: intel-win32-9_0 rule_tests_debug: intel-win32-9_0 scanner_tests: intel-win32-9_0 scanner_tests_debug: intel-win32-9_0 scoped_lock_tests: intel-win32-9_0 scoped_lock_tests_debug: intel-win32-9_0 select_p_with_rule: intel-win32-9_0 select_p_with_rule_debug: intel-win32-9_0 sf_bug_720917: intel-win32-9_0 sf_bug_720917_debug: intel-win32-9_0 shortest_alternative_tests: intel-win32-9_0 shortest_alternative_tests_debug: intel-win32-9_0 subrule_tests: intel-win32-9_0 subrule_tests_debug: intel-win32-9_0 switch_problem: intel-win32-9_0 switch_problem_debug: intel-win32-9_0 switch_tests_eps_default: intel-win32-9_0 switch_tests_eps_default_debug: intel-win32-9_0 switch_tests_general_def: intel-win32-9_0 switch_tests_general_def_debug: intel-win32-9_0 switch_tests_single: intel-win32-9_0 switch_tests_single_debug: intel-win32-9_0 switch_tests_wo_default: intel-win32-9_0 switch_tests_wo_default_debug: intel-win32-9_0 symbols_add_null: intel-win32-9_0 symbols_add_null_debug: intel-win32-9_0 symbols_find_null: intel-win32-9_0 symbols_find_null_debug: intel-win32-9_0 symbols_tests: intel-win32-9_0 symbols_tests_debug: intel-win32-9_0 while_p_as_parser_tests: intel-win32-9_0 while_tests: intel-win32-9_0 while_tests_debug: intel-win32-9_0 |static_assert| static_assert_example_2: intel-win32-9_0 static_assert_example_3: intel-win32-9_0 static_assert_test: intel-win32-9_0 |test| algorithms_test: intel-win32-9_0 auto_unit_test_test: intel-win32-9_0 auto_unit_test_test_mult: intel-win32-9_0 basic_cstring_test: intel-win32-9_0 boost_check_equal_str: intel-win32-9_0 class_properties_test: intel-win32-9_0 custom_exception_test: intel-win32-9_0 errors_handling_test: intel-win32-9_0 fixed_mapping_test: intel-win32-9_0 foreach_test: intel-win32-9_0 ifstream_line_iterator_test: intel-win32-9_0 online_test: intel-win32-9_0 output_test_stream_test: intel-win32-9_0 parameterized_test_test: intel-win32-9_0 result_report_test: intel-win32-9_0 test_case_template_test: intel-win32-9_0 test_fp_comparisons: intel-win32-9_0 test_tools_test: intel-win32-9_0 token_iterator_test: intel-win32-9_0 |thread| test_barrier: intel-win32-9_0 test_barrier_lib: intel-win32-9_0 test_condition: intel-win32-9_0 test_condition_lib: intel-win32-9_0 test_mutex: intel-win32-9_0 test_mutex_lib: intel-win32-9_0 test_once: intel-win32-9_0 test_once_lib: intel-win32-9_0 test_read_write_mutex: intel-win32-9_0 test_read_write_mutex_lib: intel-win32-9_0 test_thread: intel-win32-9_0 test_thread_lib: intel-win32-9_0 test_tss: intel-win32-9_0 test_tss_lib: intel-win32-9_0 test_xtime: intel-win32-9_0 test_xtime_lib: intel-win32-9_0 |timer| timer_test: intel-win32-9_0 |tokenizer| examples: intel-win32-9_0 simple_example_1: intel-win32-9_0 simple_example_2: intel-win32-9_0 simple_example_3: intel-win32-9_0 simple_example_4: intel-win32-9_0 simple_example_5: intel-win32-9_0 |tuple| io_test: intel-win32-9_0 tuple_test_bench: intel-win32-9_0 |type_traits| add_const_test: intel-win32-9_0 add_cv_test: intel-win32-9_0 add_pointer_test: intel-win32-9_0 add_reference_test: intel-win32-9_0 add_volatile_test: intel-win32-9_0 aligned_storage_test: intel-win32-9_0 alignment_of_test: intel-win32-9_0 decay_test: intel-win32-9_0 extent_test: intel-win32-9_0 function_traits_test: intel-win32-9_0 has_nothrow_assign_test: intel-win32-9_0 has_nothrow_constr_test: intel-win32-9_0 has_nothrow_copy_test: intel-win32-9_0 has_trivial_assign_test: intel-win32-9_0 has_trivial_constr_test: intel-win32-9_0 has_trivial_copy_test: intel-win32-9_0 has_trivial_destructor_test: intel-win32-9_0 has_virtual_destructor_test: intel-win32-9_0 is_abstract_test: intel-win32-9_0 is_arithmetic_test: intel-win32-9_0 is_array_test: intel-win32-9_0 is_base_and_derived_test: intel-win32-9_0 is_base_of_test: intel-win32-9_0 is_class_test: intel-win32-9_0 is_compound_test: intel-win32-9_0 is_const_test: intel-win32-9_0 is_convertible_test: intel-win32-9_0 is_empty_test: intel-win32-9_0 is_enum_test: intel-win32-9_0 is_float_test: intel-win32-9_0 is_floating_point_test: intel-win32-9_0 is_function_test: intel-win32-9_0 is_fundamental_test: intel-win32-9_0 is_integral_test: intel-win32-9_0 is_member_func_test: intel-win32-9_0 is_member_obj_test: intel-win32-9_0 is_member_pointer_test: intel-win32-9_0 is_object_test: intel-win32-9_0 is_pod_test: intel-win32-9_0 is_pointer_test: intel-win32-9_0 is_polymorphic_test: intel-win32-9_0 is_reference_test: intel-win32-9_0 is_same_test: intel-win32-9_0 is_scalar_test: intel-win32-9_0 is_signed_test: intel-win32-9_0 is_stateless_test: intel-win32-9_0 is_union_test: intel-win32-9_0 is_unsigned_test: intel-win32-9_0 is_void_test: intel-win32-9_0 is_volatile_test: intel-win32-9_0 rank_test: intel-win32-9_0 remove_all_extents_test: intel-win32-9_0 remove_bounds_test: intel-win32-9_0 remove_const_test: intel-win32-9_0 remove_cv_test: intel-win32-9_0 remove_extent_test: intel-win32-9_0 remove_pointer_test: intel-win32-9_0 remove_reference_test: intel-win32-9_0 remove_volatile_test: intel-win32-9_0 tricky_abstract_type_test: intel-win32-9_0 tricky_add_pointer_test: intel-win32-9_0 tricky_function_type_test: intel-win32-9_0 tricky_incomplete_type_test: intel-win32-9_0 tricky_is_enum_test: intel-win32-9_0 tricky_partial_spec_test: intel-win32-9_0 type_with_alignment_test: intel-win32-9_0 udt_specialisations: intel-win32-9_0 |utility| addressof_test: intel-win32-9_0 assert_test: intel-win32-9_0 base_from_member_test: intel-win32-9_0 binary_search_test: intel-win32-9_0 call_traits_test: intel-win32-9_0 compressed_pair_test: intel-win32-9_0 current_function_test: intel-win32-9_0 iterators_test: intel-win32-9_0 next_prior_test: intel-win32-9_0 numeric_traits_test: intel-win32-9_0 operators_test: intel-win32-9_0 ref_ct_test: intel-win32-9_0 ref_test: intel-win32-9_0 result_of_test: intel-win32-9_0 shared_iterator_test: intel-win32-9_0 value_init_test: intel-win32-9_0 |variant| recursive_variant_test: intel-win32-9_0 variant_comparison_test: intel-win32-9_0 variant_reference_test: intel-win32-9_0 variant_test1: intel-win32-9_0 variant_test2: intel-win32-9_0 variant_test3: intel-win32-9_0 variant_test4: intel-win32-9_0 variant_test5: intel-win32-9_0 variant_test6: intel-win32-9_0 variant_test7: intel-win32-9_0 variant_test8: intel-win32-9_0 variant_visit_test: intel-win32-9_0 |wave| test_re2c_lexer: intel-win32-9_0 test_slex_lexer: intel-win32-9_0 testwave: gcc-3.3.6-linux intel-win32-9_0

1 0

Interesting Article for using Boost for Remote Call Framework
by Mottengte, Rajeev Kumar 15 Aug '05

15 Aug '05

Hi An interesting article on using boost for remote call framework. http://www.codeproject.com/threads/RMI_For_Cpp.asp Rgds Rajeev

9 12

boost-1.33 test srpm available (final?)
by Neal Becker 15 Aug '05

15 Aug '05

I have updated the boost-1.33 srpm. AFAIK, there are no outstanding issues with this package, and it is ready for distribuition. Please try it. http://nbecker.dyndns.org:8080/boost-1.33.0-9.src.rpm

1 0

What does "ll" stand for?
by Daryle Walker 15 Aug '05

15 Aug '05

This is for the "ll" function defined for quaternions and octonions. The function returns the 1-norm of its argument. Does anyone know what the "ll" name stands for? I finally figured out that "sup" (the infinity-norm) most likely stands for "supremum". (BTW, "abs" is the 2-norm. The "norm" function isn't actually in this system, despite the name!) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

4 4

dependency analyzer 'Nmdepend 0.1.0 released (uses Boost)
by Eddy Pronk 15 Aug '05

15 Aug '05

"Nmdepend is a lightweight “link-time” dependency analyzer for C++. It uses object files and libraries instead of source-code as input. It can help to manage package or “cross-directory” dependencies. Dependencies can be visualized in combination with Graphviz." http://nmdepend.sourceforge.net/ nmdepend uses Boost: - graph - filesystem - program_options Eddy Pronk

1 0

Passing around log levels
by Andy Schweitzer 15 Aug '05

15 Aug '05

Is there a way to pass log levels in a variable? The following code doesn't compile: void SomeClass::Dump(boost::logging::level_type eLevel, boost::logging::logger& rLog) { BOOST_SCOPEDLOGL(rLog, eLevel) << "Some Msg" << m_iSomeMemberVariable << endl; } Compiler says: "error C2039: 'eLevel' : is not a member of 'boost::logging::level'" I think the issue is that the levels are all const ints. This is kind of important in our application. We have lots of code that knows nothing about the environment, either the logs or the levels, and needs to be compiled into different places, so it can't have the log or the log level compiled in. I suppose we could change this code to return a string and do the actual logging where the level and log are known at compile time. But that would rule out "structural" drop in replacement. So far no problems passing the log itself around, but haven't tested extensively. Thanks, Andrew

1 0

Re: [boost] Call for interest for native unicode character and string support in boost
by Graham 15 Aug '05

15 Aug '05

>From: Rogier van Dalen <rogiervd(a)gmail.com> >Subject: Re: [boost] Call for interest for native unicode character > and string support in boost > >Great, this seems a good first step. Glad to see things moving. I'll >give my comments, but I hope Erik will step in so we can see what he's >got. > >> I welcome comments. >> >>I agree with the general idea. >>First, http://www.boost.org/more/lib_guide.htm#Guidelines has coding >>guidelines. In general, your code looks slightly C-ish. The Boost >>habit is to use the ".hpp" extension for C++ headers. You attached a >file "unicode.hpp" but talk about "Unicode.hpp": note that these are >different names. >I suggest we make a namespace "unicode" rather than prepending >everything with "uni". The enums had probably better be put in >structs. > >namespace unicode { > struct range { > enum type { > latin1_supplement, > latin_extended_a, > latin_extended_a, > ipa_extensions, > // ... > } > }; >} Yes - it should be namespaced - I had omitted it for clarity. I still think that the uni prefix might be useful to remind those programmers using 'using unicode' that these are Unicode functions - but I am happy to lose that argument. >The fact that I find "Hungarian notation" ugly and meaningless is >probably irrelevant, but it's not the way it's generally done in >Boost. >char32_t is not yet a part of the C++ standard, I believe. I'm not >sure, maybe we'd better call it "codepoint" anyway, and use #ifdef'ed >typedef's. >BOOL is not C++; it is spelled "bool". DWORD doesn't exist either; I >believe you mean uint16_t (sic) for the collation data, if I >understand correctly what the methods are doing. But I think collation >should not be in this header yet, but rather be inserted later, when >the string classes are defined. Oops - caught - I was attempting to write it in such a way that it could be used from C as well as C++ - hence BOOL not bool. DWORD is actually uint32_t. I believe collation must be here as there will be probably be several containers with Unicode characteristics and this is a good level for them to work on. >Case conversion should probably take output iterators. That'll get rid >of the complex/simple division. The methods should probably be >templated as well, and take ranges rather than counts. >template <class InputIterator, class Outputiterator> > lowercase (InputIterator first, InputIterator last, OutputIterator >result); >template <class InputIterator, class Outputiterator> > uppercase (InputIterator first, InputIterator last, OutputIterator >result); I like this but we will still need to have a complex/simple division. However using iterators the complex can do both, and the simple then becomes GetSimpleLowercase for case conversion without changing length, but it can again take an output iterator. >The break functions: >Couldn't these take iterators as well? For all use cases I can think >of, this would be a much easier version to use: >template <class InputIterator> > InputIterator advance_grapheme (InputIterator position, InputIterator >last); >(etc.) When I did my original coding I coding each of following: GetStartOfGrapheme GetPreviousGrapheme GetNextGrapheme I found that just be having IsStartOfGrapheme all these became really simple routines. I therefore believe extremely strongly that it is necessary to have StartOfGrapheme and that the others like GetNextGrapheme or advancegrapheme will then be simple/inline wrappers that use StartOfGrapheme. I also found that there was a coding hit if you have to test start and end iterator positions when processing the grapheme, hence I was passing in three DWORDs. Having said that, allowing inline versions that take iterators to call the core uint32_t/ [DWORD] functions would a good thing, and I would expect this to happen. >Finally, just thinking out loud: both the case mappings and collation >have default (non-locale-specific) and tailored modes. Shouldn't those >best be represented by classes rather than free functions, and >shouldn't there thus be a global variable "default" that provides >default operations, and other objects for locale-specific operations? Unicode case mappings are locale inspecific. I do not intend to handle any code page conversions at this stage - that can be added on later and should be handled separately in a separate discussion. Those conversions would not be Unicode conversions and I believe that discussion should be postponed for a later date. Yours, Graham

3 2

Re: [boost] Interest for a perl6-like-junctions-class?
by Rob Stewart 14 Aug '05

14 Aug '05

My last update to multivalues.zip was broken. I'd forgotten to remove an include directive and apparently, there was a missing include directive from a number of files. (I don't see how mine built, but there you have it.) -- Rob Stewart stewart(a)sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;

1 0

[1.33] Libraries are not listed
by Pavel Chikulaev 14 Aug '05

14 Aug '05

Hi, Libraries added in 1.33 (IOstreams, Parameter, Pointer Container and Wave (but not Boost.Functional.Hash) ) are not listed in /doc/html/libraries.html. Shouldn't library list be generated automatically? -- Pavel Chikulaev

2 1

1.33 release regression results -- 'extra compilers'
by Jeff Garland 14 Aug '05

14 Aug '05

Why are digital mars, como and other 'non-required' compilers in the regressions results page ( http://tinyurl.com/cdlxk )? I was expecting to see an all green condition and instead I see a bunch of failures we never really tried to resolve. I think we should remove these from the user pages.... Jeff

4 6

[Boost-bugs] [ boost-Bugs-1259176 ] path and directory_iterator doesn't handle windows root path
by SourceForge.net 14 Aug '05

14 Aug '05

Bugs item #1259176, was opened at 2005-08-14 11:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1259176&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: filesystem Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: path and directory_iterator doesn't handle windows root path Initial Comment: directory_iterator does not append '\' to a windows root path correctly. The following Code using namespace boost::filesystem; path p("C:",native); directory_iterator it(p); is_directory(it); throws an exception which says "boost::filesystem::is_directory "C:some_file.foo": The system cannot find the given file." If I use C:\ it works. If I use a non root directory like C:\some_directory it works too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1259176&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

soname for 1.33
by Neal Becker 14 Aug '05

14 Aug '05

The "official" Redhat/Fedora rpms for boost-1.32 had set soname as e.g.: libboost_date_time.so.1 instead of libboost_date_time.so.1.32 I wonder if I should do the same for 1.33? Does anyone know if the API is compatible from 1.32 to 1.33? Or, has Redhat made a mistake in doing this?

3 2

Boost regression notification (2005-08-14)
by Douglas Gregor 14 Aug '05

14 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-14T11:16:15Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. disjoint_sets tokenizer functional concept_check integer array utility pool crc Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 788 failures in 31 libraries: array (5) concept_check (2) config (3) crc (1) disjoint_sets (1) functional (1) graph (13) integer (3) iostreams (3) lambda (15) multi_array (1) multi_index (2) numeric/ublas (7) parameter (88) pool (1) rational (2) regex (4) serialization (361) signals (6) smart_ptr (8) spirit (116) static_assert (1) test (19) thread (16) timer (1) tokenizer (6) tuple (2) type_traits (67) utility (15) variant (12) wave (6) |array| array1: gcc-4.0.1-linux array2: gcc-4.0.1-linux array3: gcc-4.0.1-linux array4: gcc-4.0.1-linux array5: gcc-4.0.1-linux |concept_check| class_concept_check_test: gcc-4.0.1-linux concept_check_test: gcc-4.0.1-linux |config| config_info: gcc-4.0.1-linux config_test: gcc-4.0.1-linux limits_test: gcc-4.0.1-linux |crc| crc_test: gcc-4.0.1-linux |disjoint_sets| disjoint_set_test: gcc-4.0.1-linux |functional| function_test: gcc-4.0.1-linux |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 gursoy_atun_layout_test: gcc-3.2.3-linux relaxed_heap_test: gcc-3.2.3-linux |integer| cstdint_test: gcc-4.0.1-linux integer_test: gcc-4.0.1-linux integer_traits_test: gcc-4.0.1-linux |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |lambda| algorithm_test: gcc-4.0.1-linux bind_tests_advanced: gcc-4.0.1-linux bind_tests_simple: gcc-4.0.1-linux bind_tests_simple_f_refs: gcc-4.0.1-linux bll_and_function: gcc-4.0.1-linux constructor_tests: gcc-4.0.1-linux control_structures: gcc-4.0.1-linux exception_test: gcc-4.0.1-linux extending_rt_traits: gcc-4.0.1-linux is_instance_of_test: gcc-4.0.1-linux lambda_cast_test: gcc-4.0.1-linux member_pointer_test: gcc-4.0.1-linux operator_tests_simple: gcc-4.0.1-linux phoenix_control_structures: gcc-4.0.1-linux switch_construct: gcc-4.0.1-linux |multi_array| index_bases: gcc-3.2.3-linux |multi_index| test_basic: gcc-3.2.3-linux test_set_ops: gcc-3.4.4-linux |numeric/ublas| test3: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-9_0 |parameter| basics: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 macros: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 sfinae: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 unnamed: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-3_4_3-sunos gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 |pool| test_pool_alloc: gcc-4.0.1-linux |rational| rational_example: gcc-4.0.1-linux rational_test: gcc-4.0.1-linux |regex| captures_example: gcc-3.2.3-linux captures_test: gcc-3.2.3-linux concept_check: gcc-3.2.3-linux regex_regress_dll: gcc-3.4.4-linux |serialization| test_array_binary_archive: gcc-3.2.3-linux test_array_binary_archive_dll: gcc-3.2.3-linux test_array_text_archive_dll: gcc-3.2.3-linux test_array_text_warchive: gcc-3.2.3-linux test_array_text_warchive_dll: gcc-3.2.3-linux test_array_xml_archive: gcc-4.0.1-linux test_array_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_array_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux test_array_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_binary_binary_archive_dll: gcc-3.2.3-linux test_binary_text_archive_dll: gcc-3.2.3-linux test_binary_text_warchive: gcc-3.2.3-linux test_binary_text_warchive_dll: gcc-3.2.3-linux test_binary_xml_archive_dll: gcc-3.2.3-linux test_binary_xml_warchive: gcc-3.2.3-linux test_binary_xml_warchive_dll: gcc-3.2.3-linux test_class_info_load_binary_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_binary_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_text_archive: gcc-3_4_3-sunos test_class_info_load_text_archive_dll: gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_text_warchive: gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_text_warchive_dll: gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_xml_archive: cw-9_5-darwin gcc-3_4_3-sunos test_class_info_load_xml_archive_dll: cw-9_5-darwin gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_xml_warchive: gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_load_xml_warchive_dll: gcc-3.2.3-linux gcc-3_4_3-sunos test_class_info_save_binary_archive_dll: gcc-3.2.3-linux test_class_info_save_text_archive_dll: gcc-3.2.3-linux test_class_info_save_text_warchive: gcc-3.2.3-linux test_class_info_save_text_warchive_dll: gcc-3.2.3-linux test_class_info_save_xml_archive_dll: gcc-3.2.3-linux test_class_info_save_xml_warchive: gcc-3.2.3-linux test_class_info_save_xml_warchive_dll: gcc-3.2.3-linux test_codecvt_null: gcc-4.0.1-linux test_const_pass: gcc-4.0.1-linux test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_contained_class_binary_archive_dll: gcc-3.2.3-linux test_contained_class_text_archive_dll: gcc-3.2.3-linux test_contained_class_text_warchive: gcc-3.2.3-linux test_contained_class_text_warchive_dll: gcc-3.2.3-linux test_contained_class_xml_archive_dll: gcc-3.2.3-linux test_contained_class_xml_warchive: gcc-3.2.3-linux test_contained_class_xml_warchive_dll: gcc-3.2.3-linux test_cyclic_ptrs_binary_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_text_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_text_warchive: gcc-3.2.3-linux test_cyclic_ptrs_text_warchive_dll: gcc-3.2.3-linux test_cyclic_ptrs_xml_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_xml_warchive: gcc-3.2.3-linux test_cyclic_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_delete_pointer_binary_archive_dll: gcc-3.2.3-linux test_delete_pointer_text_archive_dll: gcc-3.2.3-linux test_delete_pointer_text_warchive: gcc-3.2.3-linux test_delete_pointer_text_warchive_dll: gcc-3.2.3-linux test_delete_pointer_xml_archive_dll: gcc-3.2.3-linux test_delete_pointer_xml_warchive: gcc-3.2.3-linux test_delete_pointer_xml_warchive_dll: gcc-3.2.3-linux test_demo: gcc-4.0.1-linux test_demo_auto_ptr: gcc-4.0.1-linux test_demo_auto_ptr_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_exception: gcc-4.0.1-linux test_demo_exception_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_fast_archive: gcc-4.0.1-linux test_demo_fast_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_pimpl: gcc-4.0.1-linux test_demo_pimpl_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_polymorphic: gcc-4.0.1-linux test_demo_polymorphic_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_portable_archive: gcc-4.0.1-linux test_demo_portable_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_shared_ptr: gcc-4.0.1-linux test_demo_shared_ptr_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml: gcc-4.0.1-linux test_demo_xml_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml_load: gcc-4.0.1-linux test_demo_xml_load_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml_save: gcc-4.0.1-linux test_demo_xml_save_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_deque_binary_archive_dll: gcc-3.2.3-linux test_deque_text_archive_dll: gcc-3.2.3-linux test_deque_text_warchive: gcc-3.2.3-linux test_deque_text_warchive_dll: gcc-3.2.3-linux test_deque_xml_archive_dll: gcc-3.2.3-linux test_deque_xml_warchive: gcc-3.2.3-linux test_deque_xml_warchive_dll: gcc-3.2.3-linux test_derived_binary_archive_dll: gcc-3.2.3-linux test_derived_class_binary_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_binary_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_text_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_text_warchive: gcc-3.2.3-linux test_derived_class_ptr_text_warchive_dll: gcc-3.2.3-linux test_derived_class_ptr_xml_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_xml_warchive: gcc-3.2.3-linux test_derived_class_ptr_xml_warchive_dll: gcc-3.2.3-linux test_derived_class_text_archive_dll: gcc-3.2.3-linux test_derived_class_text_warchive: gcc-3.2.3-linux test_derived_class_text_warchive_dll: gcc-3.2.3-linux test_derived_class_xml_archive_dll: gcc-3.2.3-linux test_derived_class_xml_warchive: gcc-3.2.3-linux test_derived_class_xml_warchive_dll: gcc-3.2.3-linux test_derived_text_archive_dll: gcc-3.2.3-linux test_derived_text_warchive: gcc-3.2.3-linux test_derived_text_warchive_dll: gcc-3.2.3-linux test_derived_xml_archive_dll: gcc-3.2.3-linux test_derived_xml_warchive: gcc-3.2.3-linux test_derived_xml_warchive_dll: gcc-3.2.3-linux test_diamond_binary_archive_dll: gcc-3.2.3-linux test_diamond_text_archive_dll: gcc-3.2.3-linux test_diamond_text_warchive: gcc-3.2.3-linux test_diamond_text_warchive_dll: gcc-3.2.3-linux test_diamond_xml_archive_dll: gcc-3.2.3-linux test_diamond_xml_warchive: gcc-3.2.3-linux test_diamond_xml_warchive_dll: gcc-3.2.3-linux test_exported_binary_archive_dll: gcc-3.2.3-linux test_exported_text_archive_dll: gcc-3.2.3-linux test_exported_text_warchive: gcc-3.2.3-linux test_exported_text_warchive_dll: gcc-3.2.3-linux test_exported_xml_archive_dll: gcc-3.2.3-linux test_exported_xml_warchive: gcc-3.2.3-linux test_exported_xml_warchive_dll: gcc-3.2.3-linux test_inclusion: gcc-4.0.1-linux test_iterators: gcc-4.0.1-linux test_iterators_base64: gcc-4.0.1-linux test_list_binary_archive_dll: gcc-3.2.3-linux test_list_ptrs_binary_archive_dll: gcc-3.2.3-linux test_list_ptrs_text_archive_dll: gcc-3.2.3-linux test_list_ptrs_text_warchive: gcc-3.2.3-linux test_list_ptrs_text_warchive_dll: gcc-3.2.3-linux test_list_ptrs_xml_archive_dll: gcc-3.2.3-linux test_list_ptrs_xml_warchive: gcc-3.2.3-linux test_list_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_list_text_archive_dll: gcc-3.2.3-linux test_list_text_warchive: gcc-3.2.3-linux test_list_text_warchive_dll: gcc-3.2.3-linux test_list_xml_archive_dll: gcc-3.2.3-linux test_list_xml_warchive: gcc-3.2.3-linux test_list_xml_warchive_dll: gcc-3.2.3-linux test_map_binary_archive_dll: gcc-3.2.3-linux msvc test_map_text_archive_dll: gcc-3.2.3-linux msvc test_map_text_warchive: gcc-3.2.3-linux test_map_text_warchive_dll: gcc-3.2.3-linux msvc test_map_xml_archive_dll: gcc-3.2.3-linux test_map_xml_warchive: gcc-3.2.3-linux test_map_xml_warchive_dll: gcc-3.2.3-linux test_mi_binary_archive_dll: gcc-3.2.3-linux test_mi_text_archive_dll: gcc-3.2.3-linux test_mi_text_warchive: gcc-3.2.3-linux test_mi_text_warchive_dll: gcc-3.2.3-linux test_mi_xml_archive_dll: gcc-3.2.3-linux test_mi_xml_warchive: gcc-3.2.3-linux test_mi_xml_warchive_dll: gcc-3.2.3-linux test_mult_archive_types: gcc-4.0.1-linux test_mult_archive_types_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_multiple_ptrs_binary_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_text_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_text_warchive: gcc-3.2.3-linux test_multiple_ptrs_text_warchive_dll: gcc-3.2.3-linux test_multiple_ptrs_xml_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_xml_warchive: gcc-3.2.3-linux test_multiple_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_no_rtti_binary_archive_dll: gcc-3.2.3-linux test_no_rtti_text_archive_dll: gcc-3.2.3-linux test_no_rtti_text_warchive: gcc-3.2.3-linux test_no_rtti_text_warchive_dll: gcc-3.2.3-linux test_no_rtti_xml_archive_dll: gcc-3.2.3-linux test_no_rtti_xml_warchive: gcc-3.2.3-linux test_no_rtti_xml_warchive_dll: gcc-3.2.3-linux test_non_default_ctor2_binary_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_text_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_text_warchive: gcc-3.2.3-linux test_non_default_ctor2_text_warchive_dll: gcc-3.2.3-linux test_non_default_ctor2_xml_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_xml_warchive: gcc-3.2.3-linux test_non_default_ctor2_xml_warchive_dll: gcc-3.2.3-linux test_non_default_ctor_binary_archive_dll: gcc-3.2.3-linux test_non_default_ctor_text_archive_dll: gcc-3.2.3-linux test_non_default_ctor_text_warchive: gcc-3.2.3-linux test_non_default_ctor_text_warchive_dll: gcc-3.2.3-linux test_non_default_ctor_xml_archive_dll: gcc-3.2.3-linux test_non_default_ctor_xml_warchive: gcc-3.2.3-linux test_non_default_ctor_xml_warchive_dll: gcc-3.2.3-linux test_non_intrusive_binary_archive_dll: gcc-3.2.3-linux test_non_intrusive_text_archive_dll: gcc-3.2.3-linux test_non_intrusive_text_warchive: gcc-3.2.3-linux test_non_intrusive_text_warchive_dll: gcc-3.2.3-linux test_non_intrusive_xml_archive_dll: gcc-3.2.3-linux test_non_intrusive_xml_warchive: gcc-3.2.3-linux test_non_intrusive_xml_warchive_dll: gcc-3.2.3-linux test_null_ptr_binary_archive_dll: gcc-3.2.3-linux test_null_ptr_text_archive_dll: gcc-3.2.3-linux test_null_ptr_text_warchive: gcc-3.2.3-linux test_null_ptr_text_warchive_dll: gcc-3.2.3-linux test_null_ptr_xml_archive_dll: gcc-3.2.3-linux test_null_ptr_xml_warchive: gcc-3.2.3-linux test_null_ptr_xml_warchive_dll: gcc-3.2.3-linux test_nvp_binary_archive_dll: gcc-3.2.3-linux test_nvp_text_archive: gcc-3.2.3-linux test_nvp_text_archive_dll: gcc-3.2.3-linux test_nvp_text_warchive: gcc-3.2.3-linux test_nvp_text_warchive_dll: gcc-3.2.3-linux test_nvp_xml_archive_dll: gcc-3.2.3-linux test_nvp_xml_warchive: gcc-3.2.3-linux test_nvp_xml_warchive_dll: gcc-3.2.3-linux test_object_binary_archive_dll: gcc-3.2.3-linux test_object_text_archive_dll: gcc-3.2.3-linux test_object_text_warchive: gcc-3.2.3-linux test_object_text_warchive_dll: gcc-3.2.3-linux test_object_xml_archive_dll: gcc-3.2.3-linux test_object_xml_warchive: gcc-3.2.3-linux test_object_xml_warchive_dll: gcc-3.2.3-linux test_optional_binary_archive_dll: gcc-3.2.3-linux test_optional_text_archive_dll: gcc-3.2.3-linux test_optional_text_warchive: gcc-3.2.3-linux test_optional_text_warchive_dll: gcc-3.2.3-linux test_optional_xml_archive_dll: gcc-3.2.3-linux test_optional_xml_warchive: gcc-3.2.3-linux test_optional_xml_warchive_dll: gcc-3.2.3-linux test_polymorphic_binary_archive_dll: gcc-3.2.3-linux test_polymorphic_text_archive_dll: gcc-3.2.3-linux test_polymorphic_text_warchive: gcc-3.2.3-linux test_polymorphic_text_warchive_dll: gcc-3.2.3-linux test_polymorphic_xml_archive_dll: gcc-3.2.3-linux test_polymorphic_xml_warchive: gcc-3.2.3-linux test_polymorphic_xml_warchive_dll: gcc-3.2.3-linux test_primitive_text_archive_dll: gcc-3.2.3-linux test_primitive_text_warchive: gcc-3.2.3-linux test_primitive_text_warchive_dll: gcc-3.2.3-linux test_primitive_xml_archive_dll: gcc-3.2.3-linux test_primitive_xml_warchive: gcc-3.2.3-linux test_primitive_xml_warchive_dll: gcc-3.2.3-linux test_private_ctor: gcc-4.0.1-linux test_private_ctor_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_recursion_binary_archive_dll: gcc-3.2.3-linux test_recursion_text_archive_dll: gcc-3.2.3-linux test_recursion_text_warchive: gcc-3.2.3-linux test_recursion_text_warchive_dll: gcc-3.2.3-linux test_recursion_xml_archive_dll: gcc-3.2.3-linux test_recursion_xml_warchive: gcc-3.2.3-linux test_recursion_xml_warchive_dll: gcc-3.2.3-linux test_registered_binary_archive_dll: gcc-3.2.3-linux test_registered_text_archive_dll: gcc-3.2.3-linux test_registered_text_warchive: gcc-3.2.3-linux test_registered_text_warchive_dll: gcc-3.2.3-linux test_registered_xml_archive_dll: gcc-3.2.3-linux test_registered_xml_warchive: gcc-3.2.3-linux test_registered_xml_warchive_dll: gcc-3.2.3-linux test_reset_object_address: gcc-4.0.1-linux test_reset_object_address_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_set_binary_archive_dll: gcc-3.2.3-linux test_set_text_archive: gcc-3.2.3-linux test_set_text_archive_dll: gcc-3.2.3-linux test_set_text_warchive: gcc-3.2.3-linux test_set_text_warchive_dll: gcc-3.2.3-linux test_set_xml_archive_dll: gcc-3.2.3-linux test_set_xml_warchive: gcc-3.2.3-linux test_set_xml_warchive_dll: gcc-3.2.3-linux test_shared_ptr_132_binary_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_text_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_text_warchive: gcc-3.2.3-linux test_shared_ptr_132_text_warchive_dll: gcc-3.2.3-linux test_shared_ptr_132_xml_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_xml_warchive: gcc-3.2.3-linux test_shared_ptr_132_xml_warchive_dll: gcc-3.2.3-linux test_shared_ptr_binary_archive_dll: gcc-3.2.3-linux test_shared_ptr_text_archive_dll: gcc-3.2.3-linux test_shared_ptr_text_warchive: gcc-3.2.3-linux test_shared_ptr_text_warchive_dll: gcc-3.2.3-linux test_shared_ptr_xml_archive_dll: gcc-3.2.3-linux test_shared_ptr_xml_warchive: gcc-3.2.3-linux test_shared_ptr_xml_warchive_dll: gcc-3.2.3-linux test_simple_class_binary_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_binary_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_text_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_text_warchive: gcc-3.2.3-linux test_simple_class_ptr_text_warchive_dll: gcc-3.2.3-linux test_simple_class_ptr_xml_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_xml_warchive: gcc-3.2.3-linux test_simple_class_ptr_xml_warchive_dll: gcc-3.2.3-linux test_simple_class_text_archive_dll: gcc-3.2.3-linux test_simple_class_text_warchive: gcc-3.2.3-linux test_simple_class_text_warchive_dll: gcc-3.2.3-linux test_simple_class_xml_archive_dll: gcc-3.2.3-linux test_simple_class_xml_warchive: gcc-3.2.3-linux test_simple_class_xml_warchive_dll: gcc-3.2.3-linux test_smart_cast: gcc-4.0.1-linux test_split_binary_archive_dll: gcc-3.2.3-linux test_split_text_archive_dll: gcc-3.2.3-linux test_split_text_warchive: gcc-3.2.3-linux test_split_text_warchive_dll: gcc-3.2.3-linux test_split_xml_archive_dll: gcc-3.2.3-linux test_split_xml_warchive: gcc-3.2.3-linux test_split_xml_warchive_dll: gcc-3.2.3-linux test_static_warning: gcc-4.0.1-linux test_tracking_binary_archive_dll: gcc-3.2.3-linux test_tracking_text_archive_dll: gcc-3.2.3-linux test_tracking_text_warchive: gcc-3.2.3-linux test_tracking_text_warchive_dll: gcc-3.2.3-linux test_tracking_xml_archive_dll: gcc-3.2.3-linux test_tracking_xml_warchive: gcc-3.2.3-linux test_tracking_xml_warchive_dll: gcc-3.2.3-linux test_traits_pass: gcc-4.0.1-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux test_unregistered_text_archive_dll: gcc-3.2.3-linux test_unregistered_text_warchive: gcc-3.2.3-linux test_unregistered_text_warchive_dll: gcc-3.2.3-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux test_unregistered_xml_warchive: gcc-3.2.3-linux test_unregistered_xml_warchive_dll: gcc-3.2.3-linux test_utf8_codecvt: gcc-4.0.1-linux test_variant_binary_archive_dll: gcc-3.2.3-linux test_variant_text_archive: gcc-3.4.4-linux test_variant_text_archive_dll: gcc-3.2.3-linux test_variant_text_warchive: gcc-3.2.3-linux test_variant_text_warchive_dll: gcc-3.2.3-linux test_variant_xml_archive_dll: gcc-3.2.3-linux test_variant_xml_warchive: gcc-3.2.3-linux test_variant_xml_warchive_dll: gcc-3.2.3-linux test_vector_binary_archive_dll: gcc-3.2.3-linux test_vector_text_archive_dll: gcc-3.2.3-linux test_vector_text_warchive: gcc-3.2.3-linux test_vector_text_warchive_dll: gcc-3.2.3-linux test_vector_xml_archive_dll: gcc-3.2.3-linux test_vector_xml_warchive: gcc-3.2.3-linux test_vector_xml_warchive_dll: gcc-3.2.3-linux test_void_cast: gcc-4.0.1-linux test_void_cast_dll: gcc-3.2.3-linux gcc-4.0.1-linux |signals| dead_slot_test: gcc-4.0.1-linux deletion_test: gcc-4.0.1-linux ordering_test: gcc-4.0.1-linux signal_n_test: gcc-4.0.1-linux signal_test: gcc-4.0.1-linux trackable_test: gcc-4.0.1-linux |smart_ptr| atomic_count_test: gcc-4.0.1-linux get_deleter_test: gcc-4.0.1-linux intrusive_ptr_test: gcc-4.0.1-linux shared_from_this_test: gcc-4.0.1-linux shared_ptr_basic_test: gcc-4.0.1-linux shared_ptr_test: gcc-4.0.1-linux smart_ptr_test: gcc-4.0.1-linux weak_ptr_test: gcc-4.0.1-linux |spirit| action_tests: gcc-3.3.6-linux gcc-4.0.1-linux action_tests_debug: gcc-3.2.3-linux gcc-4.0.1-linux ast_calc_tests: gcc-4.0.1-linux ast_calc_tests_debug: gcc-4.0.1-linux bug_000008: gcc-4.0.1-linux bug_fixes: gcc-4.0.1-linux bug_fixes_debug: gcc-4.0.1-linux char_strings_test: gcc-4.0.1-linux char_strings_test_debug: gcc-4.0.1-linux chset_tests: gcc-4.0.1-linux chset_tests_debug: gcc-4.0.1-linux closure_tests: gcc-4.0.1-linux closure_tests_debug: gcc-4.0.1-linux confix_tests: gcc-4.0.1-linux confix_tests_debug: gcc-4.0.1-linux directives_tests: gcc-4.0.1-linux directives_tests_debug: gcc-4.0.1-linux distinct_tests: gcc-4.0.1-linux distinct_tests_debug: gcc-4.0.1-linux epsilon_tests: gcc-4.0.1-linux epsilon_tests_debug: gcc-4.0.1-linux escape_char_parser_tests: gcc-4.0.1-linux escape_char_parser_tests_debug: gcc-4.0.1-linux exception_tests: gcc-4.0.1-linux exception_tests_debug: gcc-4.0.1-linux file_iterator_tests: gcc-4.0.1-linux file_iterator_tests_debug: gcc-4.0.1-linux fixed_size_queue_tests: gcc-4.0.1-linux fixed_size_queue_tests_debug: gcc-4.0.1-linux for_p_as_parser_tests: gcc-4.0.1-linux for_tests: gcc-4.0.1-linux for_tests_debug: gcc-4.0.1-linux fundamental_tests: gcc-4.0.1-linux fundamental_tests_debug: gcc-4.0.1-linux grammar_def_test: gcc-4.0.1-linux grammar_def_test_debug: gcc-4.0.1-linux grammar_mt_tests: gcc-4.0.1-linux grammar_multi_instance_tst: gcc-4.0.1-linux grammar_multi_instance_tst_debug: gcc-4.0.1-linux grammar_tests: gcc-4.0.1-linux grammar_tests_debug: gcc-4.0.1-linux group_match_bug: gcc-4.0.1-linux group_match_bug_debug: gcc-4.0.1-linux if_p_as_parser_tests: gcc-4.0.1-linux if_p_int_as_condition_test: gcc-4.0.1-linux if_p_int_as_condition_test_debug: gcc-4.0.1-linux if_tests: gcc-4.0.1-linux if_tests_debug: gcc-4.0.1-linux lazy_tests: gcc-4.0.1-linux lazy_tests_debug: gcc-4.0.1-linux loops_tests: gcc-4.0.1-linux loops_tests_debug: gcc-4.0.1-linux match_tests: gcc-4.0.1-linux match_tests_debug: gcc-4.0.1-linux multi_pass_compile_tests: gcc-4.0.1-linux multi_pass_tests: gcc-4.0.1-linux multi_pass_tests_debug: gcc-4.0.1-linux negated_eps_p_test: gcc-4.0.1-linux negated_eps_p_test_debug: gcc-4.0.1-linux numerics_tests: gcc-4.0.1-linux numerics_tests_debug: gcc-4.0.1-linux operators_tests: gcc-4.0.1-linux operators_tests_debug: gcc-4.0.1-linux owi_mt_tests: gcc-4.0.1-linux owi_st_tests: gcc-4.0.1-linux owi_st_tests_debug: gcc-4.0.1-linux parametric_tests: gcc-4.0.1-linux parametric_tests_debug: gcc-4.0.1-linux parser_context_test: gcc-4.0.1-linux parser_context_test_debug: gcc-4.0.1-linux parser_traits_tests: gcc-4.0.1-linux parser_traits_tests_debug: gcc-4.0.1-linux position_iterator_tests: gcc-4.0.1-linux position_iterator_tests_debug: gcc-4.0.1-linux primitives_tests: gcc-4.0.1-linux gcc-4.0.1-linux primitives_tests_debug: gcc-4.0.1-linux repeat_ast_tests: gcc-4.0.1-linux repeat_ast_tests_debug: gcc-4.0.1-linux rule_tests: gcc-4.0.1-linux rule_tests_debug: gcc-4.0.1-linux scanner_tests: gcc-4.0.1-linux scanner_tests_debug: gcc-4.0.1-linux scoped_lock_tests: gcc-4.0.1-linux scoped_lock_tests_debug: gcc-4.0.1-linux select_p_with_rule: gcc-4.0.1-linux select_p_with_rule_debug: gcc-4.0.1-linux sf_bug_720917: gcc-4.0.1-linux sf_bug_720917_debug: gcc-4.0.1-linux shortest_alternative_tests: gcc-4.0.1-linux shortest_alternative_tests_debug: gcc-4.0.1-linux subrule_tests: gcc-4.0.1-linux subrule_tests_debug: gcc-4.0.1-linux switch_problem: gcc-4.0.1-linux switch_problem_debug: gcc-4.0.1-linux switch_tests_eps_default: gcc-4.0.1-linux switch_tests_eps_default_debug: gcc-4.0.1-linux switch_tests_general_def: gcc-4.0.1-linux switch_tests_general_def_debug: gcc-4.0.1-linux switch_tests_single: gcc-4.0.1-linux switch_tests_single_debug: gcc-4.0.1-linux switch_tests_wo_default: gcc-4.0.1-linux switch_tests_wo_default_debug: gcc-4.0.1-linux symbols_add_null: gcc-4.0.1-linux symbols_add_null_debug: gcc-4.0.1-linux symbols_find_null: gcc-4.0.1-linux symbols_find_null_debug: gcc-4.0.1-linux symbols_tests: gcc-4.0.1-linux symbols_tests_debug: gcc-4.0.1-linux traverse_tests: gcc-4.0.1-linux traverse_tests_debug: gcc-4.0.1-linux while_p_as_parser_tests: gcc-4.0.1-linux while_tests: gcc-4.0.1-linux while_tests_debug: gcc-4.0.1-linux |static_assert| static_assert_example_2: gcc-4.0.1-linux |test| algorithms_test: gcc-4.0.1-linux auto_unit_test_test: gcc-4.0.1-linux auto_unit_test_test_mult: gcc-4.0.1-linux basic_cstring_test: gcc-4.0.1-linux boost_check_equal_str: gcc-4.0.1-linux class_properties_test: gcc-4.0.1-linux custom_exception_test: gcc-4.0.1-linux errors_handling_test: gcc-4.0.1-linux fixed_mapping_test: gcc-4.0.1-linux foreach_test: gcc-4.0.1-linux ifstream_line_iterator_test: gcc-4.0.1-linux online_test: gcc-4.0.1-linux output_test_stream_test: gcc-4.0.1-linux parameterized_test_test: gcc-4.0.1-linux result_report_test: gcc-4.0.1-linux test_case_template_test: gcc-4.0.1-linux test_fp_comparisons: gcc-4.0.1-linux test_tools_test: gcc-4.0.1-linux token_iterator_test: gcc-4.0.1-linux |thread| test_barrier: gcc-4.0.1-linux test_barrier_lib: gcc-4.0.1-linux test_condition: gcc-4.0.1-linux test_condition_lib: gcc-4.0.1-linux test_mutex: gcc-4.0.1-linux test_mutex_lib: gcc-4.0.1-linux test_once: gcc-4.0.1-linux test_once_lib: gcc-4.0.1-linux test_read_write_mutex: gcc-4.0.1-linux test_read_write_mutex_lib: gcc-4.0.1-linux test_thread: gcc-4.0.1-linux test_thread_lib: gcc-4.0.1-linux test_tss: gcc-4.0.1-linux test_tss_lib: gcc-4.0.1-linux test_xtime: gcc-4.0.1-linux test_xtime_lib: gcc-4.0.1-linux |timer| timer_test: gcc-4.0.1-linux |tokenizer| examples: gcc-4.0.1-linux simple_example_1: gcc-4.0.1-linux simple_example_2: gcc-4.0.1-linux simple_example_3: gcc-4.0.1-linux simple_example_4: gcc-4.0.1-linux simple_example_5: gcc-4.0.1-linux |tuple| io_test: gcc-4.0.1-linux tuple_test_bench: gcc-4.0.1-linux |type_traits| add_const_test: gcc-4.0.1-linux add_cv_test: gcc-4.0.1-linux add_pointer_test: gcc-4.0.1-linux add_reference_test: gcc-4.0.1-linux add_volatile_test: gcc-4.0.1-linux aligned_storage_test: gcc-4.0.1-linux alignment_of_test: gcc-4.0.1-linux decay_test: gcc-4.0.1-linux extent_test: gcc-4.0.1-linux function_traits_test: gcc-4.0.1-linux has_nothrow_assign_test: gcc-4.0.1-linux has_nothrow_constr_test: gcc-4.0.1-linux has_nothrow_copy_test: gcc-4.0.1-linux has_trivial_assign_test: gcc-4.0.1-linux has_trivial_constr_test: gcc-4.0.1-linux has_trivial_copy_test: gcc-4.0.1-linux has_trivial_destructor_test: gcc-4.0.1-linux has_virtual_destructor_test: gcc-4.0.1-linux is_abstract_test: gcc-4.0.1-linux is_arithmetic_test: gcc-4.0.1-linux is_array_test: gcc-4.0.1-linux is_base_and_derived_test: gcc-4.0.1-linux is_base_of_test: gcc-4.0.1-linux is_class_test: gcc-4.0.1-linux is_compound_test: gcc-4.0.1-linux is_const_test: gcc-4.0.1-linux is_convertible_test: gcc-4.0.1-linux is_empty_test: gcc-4.0.1-linux is_enum_test: gcc-4.0.1-linux is_float_test: gcc-4.0.1-linux is_floating_point_test: gcc-4.0.1-linux is_function_test: gcc-4.0.1-linux is_fundamental_test: gcc-4.0.1-linux is_integral_test: gcc-4.0.1-linux is_member_func_test: gcc-4.0.1-linux is_member_obj_test: gcc-4.0.1-linux is_member_pointer_test: gcc-4.0.1-linux is_object_test: gcc-4.0.1-linux is_pod_test: gcc-4.0.1-linux is_pointer_test: gcc-4.0.1-linux is_polymorphic_test: gcc-4.0.1-linux is_reference_test: gcc-4.0.1-linux is_same_test: gcc-4.0.1-linux is_scalar_test: gcc-4.0.1-linux is_signed_test: gcc-4.0.1-linux is_stateless_test: gcc-4.0.1-linux is_union_test: gcc-4.0.1-linux is_unsigned_test: gcc-4.0.1-linux is_void_test: gcc-4.0.1-linux is_volatile_test: gcc-4.0.1-linux rank_test: gcc-4.0.1-linux remove_all_extents_test: gcc-4.0.1-linux remove_bounds_test: gcc-4.0.1-linux remove_const_test: gcc-4.0.1-linux remove_cv_test: gcc-4.0.1-linux remove_extent_test: gcc-4.0.1-linux remove_pointer_test: gcc-4.0.1-linux remove_reference_test: gcc-4.0.1-linux remove_volatile_test: gcc-4.0.1-linux tricky_abstract_type_test: gcc-4.0.1-linux tricky_add_pointer_test: gcc-4.0.1-linux tricky_function_type_test: gcc-4.0.1-linux tricky_incomplete_type_test: gcc-4.0.1-linux tricky_is_enum_test: gcc-4.0.1-linux tricky_partial_spec_test: gcc-4.0.1-linux type_with_alignment_test: gcc-4.0.1-linux udt_specialisations: gcc-4.0.1-linux |utility| addressof_test: gcc-4.0.1-linux assert_test: gcc-4.0.1-linux base_from_member_test: gcc-4.0.1-linux binary_search_test: gcc-4.0.1-linux call_traits_test: gcc-4.0.1-linux compressed_pair_test: gcc-4.0.1-linux iterators_test: gcc-4.0.1-linux next_prior_test: gcc-4.0.1-linux numeric_traits_test: gcc-4.0.1-linux operators_test: gcc-4.0.1-linux ref_ct_test: gcc-4.0.1-linux ref_test: gcc-4.0.1-linux result_of_test: gcc-4.0.1-linux shared_iterator_test: gcc-4.0.1-linux value_init_test: gcc-4.0.1-linux |variant| recursive_variant_test: gcc-4.0.1-linux variant_comparison_test: gcc-4.0.1-linux variant_reference_test: gcc-4.0.1-linux variant_test1: gcc-4.0.1-linux variant_test2: gcc-4.0.1-linux variant_test3: gcc-4.0.1-linux variant_test4: gcc-4.0.1-linux variant_test5: gcc-4.0.1-linux variant_test6: gcc-4.0.1-linux variant_test7: gcc-4.0.1-linux variant_test8: gcc-4.0.1-linux variant_visit_test: gcc-4.0.1-linux |wave| test_re2c_lexer: gcc-3.2.3-linux gcc-4.0.1-linux test_slex_lexer: gcc-3.2.3-linux gcc-4.0.1-linux testwave: gcc-3.3.6-linux gcc-4.0.1-linux

1 0

[sandbox-vault]how to delete directory
by Larry Evans 14 Aug '05

14 Aug '05

How can I delete an empty directory I've previously created? I can delete a file, but not a directory, AFAICT. TIA.

2 1

Re: [boost] Interest for a perl6-like-junctions-class?
by Rob Stewart 14 Aug '05

14 Aug '05

I have posted an update to multivalues.zip (there was an earlier, minor update that I didn't mention). The new version contains the following changes relative to my last announcement: - user-defined predicates modeled after or derived from std::binary_function now work. The predicates must be CopyConstructible, copies must be equivalent and cheap to make, and there must be a nested type first_argument_type. The result type is assumed convertible to bool. - The library directory and namespace name is now "multivalue" (singular) - Changed items_of() to constrain the upper limit to the range length and the lower limit to be <= the upper limit. - Added percent_of() to between and exactly which computes the percentage based upon constraining the upper limit to 100%, constraining the lower limit to be <= the upper limit, and computing each to be N * length / 100, where N is the adjusted limit and length is the range length. - Added more_than and less_than with items_of() and percent_of() I am working on motivation, tutorial, and reference documentation. Do let me know if you have any comments on the current design, interface, or naming. -- Rob Stewart stewart(a)sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;

1 0

Any (La)TeX experts here?
by Daryle Walker 14 Aug '05

14 Aug '05

I tried using LaTeX within some Doxygen comments I added to a header I'm trying out in the Sandbox. Then I decided to practice with LaTeX directly. I made a version of the quaternion PDF papers in LaTeX in the Sandbox as "libs/math/doc/HyperComplex.tex" with a corresponding *.bib file. (Now we can correct the information in the future.) When I turned it into a PDF, some of the formulas were way too big. Does anyone know how to fix them? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

1 0

[Boost-bugs] [ boost-Bugs-1258697 ] vc71.mak broken build
by SourceForge.net 14 Aug '05

14 Aug '05

Bugs item #1258697, was opened at 2005-08-13 17:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1258697&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: config Group: None Status: Open Resolution: None Priority: 5 Submitted By: D Brown (key88sf) Assigned to: John Maddock (johnmaddock) Summary: vc71.mak broken build Initial Comment: In boost 1_33_0, it looks like /boost/regex/config/allocator.hpp is missing (was present in 1.32.0). This breaks the vc71.mak build immediately: Building Boost.Regex without ICU / Unicode support: Hint: set ICU_PATH on the nmake command line to point to your ICU installation if you have one. NMAKE : fatal error U1073: don't know how to make '../../../boost/regex/config/allocator.hpp' Stop. I'm building from the .zip sourcecode from SF.net. Perhaps other files are missing as well? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1258697&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

test boost-1.33.0-7.srpm available
by Neal Becker 13 Aug '05

13 Aug '05

A new SRPM is available. Please try it. Change from boost-1.33.0-6 includes: Builds 3 packages. Standard package includes just non-debug dlls. -devel package includes debug dlls, static libs, and header files -doc package includes html docs. Build tested on Fedora 4 linux x86_64 only. Please let me know of any success or failure. I'm wondering if the build should include standard CFLAGS defined by rpm per platform? At present, I'm thinking boost already is trying to handle this, so I'm leaving it out. Available here: http://nbecker.dyndns.org:8080/boost-1.33.0-7.src.rpm

1 0

[1.33] Even more libraries are not listed
by Pavel Chikulaev 13 Aug '05

13 Aug '05

Comparing \libs\libraries.htm and \doc\html\libraries.html I found that even more libraries are not listed: assign enable_if in_placed_factory min_max multi_index numeric/conversion Also, names in these two lists don't match (i.e. Thread and Threads and so on). Funnily, there is also retired library Compose in list at \doc\html\libraries.html and libraries are not alphabetical order. -- Pavel Chikulaev

1 0

alignment problem in proposed any alternative
by christopher diggins 13 Aug '05

13 Aug '05

In the boost::any alternative implementation being developed by Pablo Aguilar and myself (latest version at http://www.codeproject.com/cpp/dynamic_typing.asp ) we have run into a problem of alignment with no obvious answer. We are trying to do the following: struct any { void* table; void* object; ... template<typename T> any(const T& x) { table = any_detail::get_table<T>::get(); if (sizeof(T) <= sizeof(void*)) { if (new(&object) T(x) != &object) { throw runtime_error("can not align the data type ... pigs must be flying"); } } } else { object = new T(x); } } The question I have is whether in practice though are there are any compilers which have stricter alignment requirements on small types (<= sizeof(void*)) than a void pointer. In other words, is it possible with any known compiler to actually throw the runtime error ? Unfortunately there is another problem, I am not an expert in interepreting the standard, but AFAICT placement new is guaranteed to return a pointer to properly aligned memory (3.7.3.1 / 2) which I leverage to check that alignment occured. Apparently not every STL implementation does in fact do that (I believe at least dinkumware is guilty of that). Thanks in advance for your help! Christopher Diggins http://www.cdiggins.com

4 7

Boost regression notification (2005-08-13)
by Douglas Gregor 13 Aug '05

13 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-13T15:25:16Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. disjoint_sets tokenizer functional concept_check integer array utility pool crc Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 776 failures in 31 libraries: array (5) concept_check (2) config (3) crc (1) disjoint_sets (1) functional (1) graph (12) integer (3) iostreams (3) lambda (15) multi_array (1) multi_index (2) numeric/ublas (8) parameter (80) pool (1) rational (2) regex (4) serialization (357) signals (6) smart_ptr (8) spirit (116) static_assert (1) test (19) thread (16) timer (1) tokenizer (6) tuple (2) type_traits (67) utility (15) variant (12) wave (6) |array| array1: gcc-4.0.1-linux array2: gcc-4.0.1-linux array3: gcc-4.0.1-linux array4: gcc-4.0.1-linux array5: gcc-4.0.1-linux |concept_check| class_concept_check_test: gcc-4.0.1-linux concept_check_test: gcc-4.0.1-linux |config| config_info: gcc-4.0.1-linux config_test: gcc-4.0.1-linux limits_test: gcc-4.0.1-linux |crc| crc_test: gcc-4.0.1-linux |disjoint_sets| disjoint_set_test: gcc-4.0.1-linux |functional| function_test: gcc-4.0.1-linux |graph| graphviz_test: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-4.0.1-linux mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 gursoy_atun_layout_test: gcc-3.2.3-linux relaxed_heap_test: gcc-3.2.3-linux |integer| cstdint_test: gcc-4.0.1-linux integer_test: gcc-4.0.1-linux integer_traits_test: gcc-4.0.1-linux |iostreams| bzip2_test: mingw-3_4_2 gzip_test: mingw-3_4_2 zlib_test: mingw-3_4_2 |lambda| algorithm_test: gcc-4.0.1-linux bind_tests_advanced: gcc-4.0.1-linux bind_tests_simple: gcc-4.0.1-linux bind_tests_simple_f_refs: gcc-4.0.1-linux bll_and_function: gcc-4.0.1-linux constructor_tests: gcc-4.0.1-linux control_structures: gcc-4.0.1-linux exception_test: gcc-4.0.1-linux extending_rt_traits: gcc-4.0.1-linux is_instance_of_test: gcc-4.0.1-linux lambda_cast_test: gcc-4.0.1-linux member_pointer_test: gcc-4.0.1-linux operator_tests_simple: gcc-4.0.1-linux phoenix_control_structures: gcc-4.0.1-linux switch_construct: gcc-4.0.1-linux |multi_array| index_bases: gcc-3.2.3-linux |multi_index| test_basic: gcc-3.2.3-linux test_set_ops: gcc-3.4.4-linux |numeric/ublas| test3: cw-9_4 gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-9_0 mingw-3_4_2 |parameter| basics: cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 macros: cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 sfinae: cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 unnamed: cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.4-linux gcc-4.0.1-linux intel-8.1-linux intel-win32-8_1 intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 vc-7_1 |pool| test_pool_alloc: gcc-4.0.1-linux |rational| rational_example: gcc-4.0.1-linux rational_test: gcc-4.0.1-linux |regex| captures_example: gcc-3.2.3-linux captures_test: gcc-3.2.3-linux concept_check: gcc-3.2.3-linux regex_regress_dll: gcc-3.4.4-linux |serialization| test_array_binary_archive: gcc-3.2.3-linux test_array_binary_archive_dll: gcc-3.2.3-linux test_array_text_archive_dll: gcc-3.2.3-linux test_array_text_warchive: gcc-3.2.3-linux test_array_text_warchive_dll: gcc-3.2.3-linux test_array_xml_archive: gcc-4.0.1-linux test_array_xml_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_array_xml_warchive: gcc-3.2.3-linux gcc-4.0.1-linux test_array_xml_warchive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_binary_binary_archive_dll: gcc-3.2.3-linux test_binary_text_archive_dll: gcc-3.2.3-linux test_binary_text_warchive: gcc-3.2.3-linux test_binary_text_warchive_dll: gcc-3.2.3-linux test_binary_xml_archive_dll: gcc-3.2.3-linux test_binary_xml_warchive: gcc-3.2.3-linux test_binary_xml_warchive_dll: gcc-3.2.3-linux test_class_info_load_binary_archive: mingw-3_4_2 test_class_info_load_binary_archive_dll: gcc-3.2.3-linux mingw-3_4_2 test_class_info_load_text_archive: mingw-3_4_2 test_class_info_load_text_archive_dll: gcc-3.2.3-linux mingw-3_4_2 test_class_info_load_text_warchive: gcc-3.2.3-linux test_class_info_load_text_warchive_dll: gcc-3.2.3-linux test_class_info_load_xml_archive: mingw-3_4_2 test_class_info_load_xml_archive_dll: gcc-3.2.3-linux mingw-3_4_2 test_class_info_load_xml_warchive: gcc-3.2.3-linux test_class_info_load_xml_warchive_dll: gcc-3.2.3-linux test_class_info_save_binary_archive_dll: gcc-3.2.3-linux test_class_info_save_text_archive_dll: gcc-3.2.3-linux test_class_info_save_text_warchive: gcc-3.2.3-linux test_class_info_save_text_warchive_dll: gcc-3.2.3-linux test_class_info_save_xml_archive_dll: gcc-3.2.3-linux test_class_info_save_xml_warchive: gcc-3.2.3-linux test_class_info_save_xml_warchive_dll: gcc-3.2.3-linux test_codecvt_null: gcc-4.0.1-linux test_const_pass: gcc-4.0.1-linux test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_contained_class_binary_archive_dll: gcc-3.2.3-linux test_contained_class_text_archive_dll: gcc-3.2.3-linux test_contained_class_text_warchive: gcc-3.2.3-linux test_contained_class_text_warchive_dll: gcc-3.2.3-linux test_contained_class_xml_archive_dll: gcc-3.2.3-linux test_contained_class_xml_warchive: gcc-3.2.3-linux test_contained_class_xml_warchive_dll: gcc-3.2.3-linux test_cyclic_ptrs_binary_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_text_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_text_warchive: gcc-3.2.3-linux test_cyclic_ptrs_text_warchive_dll: gcc-3.2.3-linux test_cyclic_ptrs_xml_archive_dll: gcc-3.2.3-linux test_cyclic_ptrs_xml_warchive: gcc-3.2.3-linux test_cyclic_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_delete_pointer_binary_archive_dll: gcc-3.2.3-linux test_delete_pointer_text_archive_dll: gcc-3.2.3-linux test_delete_pointer_text_warchive: gcc-3.2.3-linux test_delete_pointer_text_warchive_dll: gcc-3.2.3-linux test_delete_pointer_xml_archive_dll: gcc-3.2.3-linux test_delete_pointer_xml_warchive: gcc-3.2.3-linux test_delete_pointer_xml_warchive_dll: gcc-3.2.3-linux test_demo: gcc-4.0.1-linux test_demo_auto_ptr: gcc-4.0.1-linux test_demo_auto_ptr_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_exception: gcc-4.0.1-linux test_demo_exception_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_fast_archive: gcc-4.0.1-linux test_demo_fast_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_pimpl: gcc-4.0.1-linux test_demo_pimpl_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_polymorphic: gcc-4.0.1-linux test_demo_polymorphic_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_portable_archive: gcc-4.0.1-linux test_demo_portable_archive_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_shared_ptr: gcc-4.0.1-linux test_demo_shared_ptr_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml: gcc-4.0.1-linux test_demo_xml_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml_load: gcc-4.0.1-linux test_demo_xml_load_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_demo_xml_save: gcc-4.0.1-linux test_demo_xml_save_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_deque_binary_archive_dll: gcc-3.2.3-linux test_deque_text_archive_dll: gcc-3.2.3-linux test_deque_text_warchive: gcc-3.2.3-linux test_deque_text_warchive_dll: gcc-3.2.3-linux test_deque_xml_archive: vc-7_1 test_deque_xml_archive_dll: gcc-3.2.3-linux vc-7_1 test_deque_xml_warchive: gcc-3.2.3-linux vc-7_1 test_deque_xml_warchive_dll: gcc-3.2.3-linux vc-7_1 test_derived_binary_archive_dll: gcc-3.2.3-linux test_derived_class_binary_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_binary_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_text_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_text_warchive: gcc-3.2.3-linux test_derived_class_ptr_text_warchive_dll: gcc-3.2.3-linux test_derived_class_ptr_xml_archive_dll: gcc-3.2.3-linux test_derived_class_ptr_xml_warchive: gcc-3.2.3-linux test_derived_class_ptr_xml_warchive_dll: gcc-3.2.3-linux test_derived_class_text_archive_dll: gcc-3.2.3-linux test_derived_class_text_warchive: gcc-3.2.3-linux test_derived_class_text_warchive_dll: gcc-3.2.3-linux test_derived_class_xml_archive_dll: gcc-3.2.3-linux test_derived_class_xml_warchive: gcc-3.2.3-linux test_derived_class_xml_warchive_dll: gcc-3.2.3-linux test_derived_text_archive_dll: gcc-3.2.3-linux test_derived_text_warchive: gcc-3.2.3-linux test_derived_text_warchive_dll: gcc-3.2.3-linux test_derived_xml_archive_dll: gcc-3.2.3-linux test_derived_xml_warchive: gcc-3.2.3-linux test_derived_xml_warchive_dll: gcc-3.2.3-linux test_diamond_binary_archive_dll: gcc-3.2.3-linux test_diamond_text_archive_dll: gcc-3.2.3-linux test_diamond_text_warchive: gcc-3.2.3-linux test_diamond_text_warchive_dll: gcc-3.2.3-linux test_diamond_xml_archive_dll: gcc-3.2.3-linux test_diamond_xml_warchive: gcc-3.2.3-linux test_diamond_xml_warchive_dll: gcc-3.2.3-linux test_exported_binary_archive_dll: gcc-3.2.3-linux test_exported_text_archive_dll: gcc-3.2.3-linux test_exported_text_warchive: gcc-3.2.3-linux test_exported_text_warchive_dll: gcc-3.2.3-linux test_exported_xml_archive_dll: gcc-3.2.3-linux test_exported_xml_warchive: gcc-3.2.3-linux test_exported_xml_warchive_dll: gcc-3.2.3-linux test_inclusion: gcc-4.0.1-linux test_iterators: gcc-4.0.1-linux test_iterators_base64: gcc-4.0.1-linux test_list_binary_archive_dll: gcc-3.2.3-linux test_list_ptrs_binary_archive_dll: gcc-3.2.3-linux test_list_ptrs_text_archive_dll: gcc-3.2.3-linux test_list_ptrs_text_warchive: gcc-3.2.3-linux test_list_ptrs_text_warchive_dll: gcc-3.2.3-linux test_list_ptrs_xml_archive_dll: gcc-3.2.3-linux test_list_ptrs_xml_warchive: gcc-3.2.3-linux test_list_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_list_text_archive_dll: gcc-3.2.3-linux test_list_text_warchive: gcc-3.2.3-linux test_list_text_warchive_dll: gcc-3.2.3-linux test_list_xml_archive_dll: gcc-3.2.3-linux test_list_xml_warchive: gcc-3.2.3-linux test_list_xml_warchive_dll: gcc-3.2.3-linux test_map_binary_archive_dll: gcc-3.2.3-linux msvc test_map_text_archive_dll: gcc-3.2.3-linux msvc test_map_text_warchive: gcc-3.2.3-linux test_map_text_warchive_dll: gcc-3.2.3-linux msvc test_map_xml_archive_dll: gcc-3.2.3-linux test_map_xml_warchive: gcc-3.2.3-linux test_map_xml_warchive_dll: gcc-3.2.3-linux test_mi_binary_archive_dll: gcc-3.2.3-linux test_mi_text_archive_dll: gcc-3.2.3-linux test_mi_text_warchive: gcc-3.2.3-linux test_mi_text_warchive_dll: gcc-3.2.3-linux test_mi_xml_archive_dll: gcc-3.2.3-linux test_mi_xml_warchive: gcc-3.2.3-linux test_mi_xml_warchive_dll: gcc-3.2.3-linux test_mult_archive_types: gcc-4.0.1-linux test_mult_archive_types_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_multiple_ptrs_binary_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_text_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_text_warchive: gcc-3.2.3-linux test_multiple_ptrs_text_warchive_dll: gcc-3.2.3-linux test_multiple_ptrs_xml_archive_dll: gcc-3.2.3-linux test_multiple_ptrs_xml_warchive: gcc-3.2.3-linux test_multiple_ptrs_xml_warchive_dll: gcc-3.2.3-linux test_no_rtti_binary_archive_dll: gcc-3.2.3-linux test_no_rtti_text_archive_dll: gcc-3.2.3-linux test_no_rtti_text_warchive: gcc-3.2.3-linux test_no_rtti_text_warchive_dll: gcc-3.2.3-linux test_no_rtti_xml_archive_dll: gcc-3.2.3-linux test_no_rtti_xml_warchive: gcc-3.2.3-linux test_no_rtti_xml_warchive_dll: gcc-3.2.3-linux test_non_default_ctor2_binary_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_text_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_text_warchive: gcc-3.2.3-linux test_non_default_ctor2_text_warchive_dll: gcc-3.2.3-linux test_non_default_ctor2_xml_archive_dll: gcc-3.2.3-linux test_non_default_ctor2_xml_warchive: gcc-3.2.3-linux test_non_default_ctor2_xml_warchive_dll: gcc-3.2.3-linux test_non_default_ctor_binary_archive_dll: gcc-3.2.3-linux test_non_default_ctor_text_archive_dll: gcc-3.2.3-linux test_non_default_ctor_text_warchive: gcc-3.2.3-linux test_non_default_ctor_text_warchive_dll: gcc-3.2.3-linux test_non_default_ctor_xml_archive_dll: gcc-3.2.3-linux test_non_default_ctor_xml_warchive: gcc-3.2.3-linux test_non_default_ctor_xml_warchive_dll: gcc-3.2.3-linux test_non_intrusive_binary_archive_dll: gcc-3.2.3-linux test_non_intrusive_text_archive_dll: gcc-3.2.3-linux test_non_intrusive_text_warchive: gcc-3.2.3-linux test_non_intrusive_text_warchive_dll: gcc-3.2.3-linux test_non_intrusive_xml_archive_dll: gcc-3.2.3-linux test_non_intrusive_xml_warchive: gcc-3.2.3-linux test_non_intrusive_xml_warchive_dll: gcc-3.2.3-linux test_null_ptr_binary_archive_dll: gcc-3.2.3-linux test_null_ptr_text_archive_dll: gcc-3.2.3-linux test_null_ptr_text_warchive: gcc-3.2.3-linux test_null_ptr_text_warchive_dll: gcc-3.2.3-linux test_null_ptr_xml_archive_dll: gcc-3.2.3-linux test_null_ptr_xml_warchive: gcc-3.2.3-linux test_null_ptr_xml_warchive_dll: gcc-3.2.3-linux test_nvp_binary_archive_dll: gcc-3.2.3-linux test_nvp_text_archive: gcc-3.2.3-linux test_nvp_text_archive_dll: gcc-3.2.3-linux test_nvp_text_warchive: gcc-3.2.3-linux test_nvp_text_warchive_dll: gcc-3.2.3-linux test_nvp_xml_archive_dll: gcc-3.2.3-linux test_nvp_xml_warchive: gcc-3.2.3-linux test_nvp_xml_warchive_dll: gcc-3.2.3-linux test_object_binary_archive_dll: gcc-3.2.3-linux test_object_text_archive_dll: gcc-3.2.3-linux test_object_text_warchive: gcc-3.2.3-linux test_object_text_warchive_dll: gcc-3.2.3-linux test_object_xml_archive_dll: gcc-3.2.3-linux test_object_xml_warchive: gcc-3.2.3-linux test_object_xml_warchive_dll: gcc-3.2.3-linux test_optional_binary_archive_dll: gcc-3.2.3-linux test_optional_text_archive_dll: gcc-3.2.3-linux test_optional_text_warchive: gcc-3.2.3-linux test_optional_text_warchive_dll: gcc-3.2.3-linux test_optional_xml_archive_dll: gcc-3.2.3-linux test_optional_xml_warchive: gcc-3.2.3-linux test_optional_xml_warchive_dll: gcc-3.2.3-linux test_polymorphic_binary_archive_dll: gcc-3.2.3-linux test_polymorphic_text_archive_dll: gcc-3.2.3-linux test_polymorphic_text_warchive: gcc-3.2.3-linux test_polymorphic_text_warchive_dll: gcc-3.2.3-linux test_polymorphic_xml_archive_dll: gcc-3.2.3-linux test_polymorphic_xml_warchive: gcc-3.2.3-linux test_polymorphic_xml_warchive_dll: gcc-3.2.3-linux test_primitive_text_archive_dll: gcc-3.2.3-linux test_primitive_text_warchive: gcc-3.2.3-linux test_primitive_text_warchive_dll: gcc-3.2.3-linux test_primitive_xml_archive_dll: gcc-3.2.3-linux test_primitive_xml_warchive: gcc-3.2.3-linux test_primitive_xml_warchive_dll: gcc-3.2.3-linux test_private_ctor: gcc-4.0.1-linux test_private_ctor_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_recursion_binary_archive_dll: gcc-3.2.3-linux test_recursion_text_archive_dll: gcc-3.2.3-linux test_recursion_text_warchive: gcc-3.2.3-linux test_recursion_text_warchive_dll: gcc-3.2.3-linux test_recursion_xml_archive_dll: gcc-3.2.3-linux test_recursion_xml_warchive: gcc-3.2.3-linux test_recursion_xml_warchive_dll: gcc-3.2.3-linux test_registered_binary_archive_dll: gcc-3.2.3-linux test_registered_text_archive_dll: gcc-3.2.3-linux test_registered_text_warchive: gcc-3.2.3-linux test_registered_text_warchive_dll: gcc-3.2.3-linux test_registered_xml_archive_dll: gcc-3.2.3-linux test_registered_xml_warchive: gcc-3.2.3-linux test_registered_xml_warchive_dll: gcc-3.2.3-linux test_reset_object_address: gcc-4.0.1-linux test_reset_object_address_dll: gcc-3.2.3-linux gcc-4.0.1-linux test_set_binary_archive_dll: gcc-3.2.3-linux test_set_text_archive: gcc-3.2.3-linux test_set_text_archive_dll: gcc-3.2.3-linux test_set_text_warchive: gcc-3.2.3-linux test_set_text_warchive_dll: gcc-3.2.3-linux test_set_xml_archive_dll: gcc-3.2.3-linux test_set_xml_warchive: gcc-3.2.3-linux test_set_xml_warchive_dll: gcc-3.2.3-linux test_shared_ptr_132_binary_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_text_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_text_warchive: gcc-3.2.3-linux test_shared_ptr_132_text_warchive_dll: gcc-3.2.3-linux test_shared_ptr_132_xml_archive_dll: gcc-3.2.3-linux test_shared_ptr_132_xml_warchive: gcc-3.2.3-linux test_shared_ptr_132_xml_warchive_dll: gcc-3.2.3-linux test_shared_ptr_binary_archive_dll: gcc-3.2.3-linux test_shared_ptr_text_archive_dll: gcc-3.2.3-linux test_shared_ptr_text_warchive: gcc-3.2.3-linux test_shared_ptr_text_warchive_dll: gcc-3.2.3-linux test_shared_ptr_xml_archive_dll: gcc-3.2.3-linux test_shared_ptr_xml_warchive: gcc-3.2.3-linux test_shared_ptr_xml_warchive_dll: gcc-3.2.3-linux test_simple_class_binary_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_binary_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_text_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_text_warchive: gcc-3.2.3-linux test_simple_class_ptr_text_warchive_dll: gcc-3.2.3-linux test_simple_class_ptr_xml_archive_dll: gcc-3.2.3-linux test_simple_class_ptr_xml_warchive: gcc-3.2.3-linux test_simple_class_ptr_xml_warchive_dll: gcc-3.2.3-linux test_simple_class_text_archive_dll: gcc-3.2.3-linux test_simple_class_text_warchive: gcc-3.2.3-linux test_simple_class_text_warchive_dll: gcc-3.2.3-linux test_simple_class_xml_archive_dll: gcc-3.2.3-linux test_simple_class_xml_warchive: gcc-3.2.3-linux test_simple_class_xml_warchive_dll: gcc-3.2.3-linux test_smart_cast: gcc-4.0.1-linux test_split_binary_archive_dll: gcc-3.2.3-linux test_split_text_archive_dll: gcc-3.2.3-linux test_split_text_warchive: gcc-3.2.3-linux test_split_text_warchive_dll: gcc-3.2.3-linux test_split_xml_archive_dll: gcc-3.2.3-linux test_split_xml_warchive: gcc-3.2.3-linux test_split_xml_warchive_dll: gcc-3.2.3-linux test_static_warning: gcc-4.0.1-linux test_tracking_binary_archive_dll: gcc-3.2.3-linux test_tracking_text_archive_dll: gcc-3.2.3-linux test_tracking_text_warchive: gcc-3.2.3-linux test_tracking_text_warchive_dll: gcc-3.2.3-linux test_tracking_xml_archive_dll: gcc-3.2.3-linux test_tracking_xml_warchive: gcc-3.2.3-linux test_tracking_xml_warchive_dll: gcc-3.2.3-linux test_traits_pass: gcc-4.0.1-linux test_unregistered_binary_archive_dll: gcc-3.2.3-linux test_unregistered_text_archive_dll: gcc-3.2.3-linux test_unregistered_text_warchive: gcc-3.2.3-linux test_unregistered_text_warchive_dll: gcc-3.2.3-linux test_unregistered_xml_archive_dll: gcc-3.2.3-linux test_unregistered_xml_warchive: gcc-3.2.3-linux test_unregistered_xml_warchive_dll: gcc-3.2.3-linux test_utf8_codecvt: gcc-4.0.1-linux test_variant_binary_archive_dll: gcc-3.2.3-linux test_variant_text_archive: gcc-3.4.4-linux test_variant_text_archive_dll: gcc-3.2.3-linux test_variant_text_warchive: gcc-3.2.3-linux test_variant_text_warchive_dll: gcc-3.2.3-linux test_variant_xml_archive_dll: gcc-3.2.3-linux test_variant_xml_warchive: gcc-3.2.3-linux test_variant_xml_warchive_dll: gcc-3.2.3-linux test_vector_binary_archive_dll: gcc-3.2.3-linux test_vector_text_archive_dll: gcc-3.2.3-linux test_vector_text_warchive: gcc-3.2.3-linux test_vector_text_warchive_dll: gcc-3.2.3-linux test_vector_xml_archive_dll: gcc-3.2.3-linux test_vector_xml_warchive: gcc-3.2.3-linux test_vector_xml_warchive_dll: gcc-3.2.3-linux test_void_cast: gcc-4.0.1-linux test_void_cast_dll: gcc-3.2.3-linux gcc-4.0.1-linux |signals| dead_slot_test: gcc-4.0.1-linux deletion_test: gcc-4.0.1-linux ordering_test: gcc-4.0.1-linux signal_n_test: gcc-4.0.1-linux signal_test: gcc-4.0.1-linux trackable_test: gcc-4.0.1-linux |smart_ptr| atomic_count_test: gcc-4.0.1-linux get_deleter_test: gcc-4.0.1-linux intrusive_ptr_test: gcc-4.0.1-linux shared_from_this_test: gcc-4.0.1-linux shared_ptr_basic_test: gcc-4.0.1-linux shared_ptr_test: gcc-4.0.1-linux smart_ptr_test: gcc-4.0.1-linux weak_ptr_test: gcc-4.0.1-linux |spirit| action_tests: gcc-3.3.6-linux gcc-4.0.1-linux action_tests_debug: gcc-3.2.3-linux gcc-4.0.1-linux ast_calc_tests: gcc-4.0.1-linux ast_calc_tests_debug: gcc-4.0.1-linux bug_000008: gcc-4.0.1-linux bug_fixes: gcc-4.0.1-linux bug_fixes_debug: gcc-4.0.1-linux char_strings_test: gcc-4.0.1-linux char_strings_test_debug: gcc-4.0.1-linux chset_tests: gcc-4.0.1-linux chset_tests_debug: gcc-4.0.1-linux closure_tests: gcc-4.0.1-linux closure_tests_debug: gcc-4.0.1-linux confix_tests: gcc-4.0.1-linux confix_tests_debug: gcc-4.0.1-linux directives_tests: gcc-4.0.1-linux directives_tests_debug: gcc-4.0.1-linux distinct_tests: gcc-4.0.1-linux distinct_tests_debug: gcc-4.0.1-linux epsilon_tests: gcc-4.0.1-linux epsilon_tests_debug: gcc-4.0.1-linux escape_char_parser_tests: gcc-4.0.1-linux escape_char_parser_tests_debug: gcc-4.0.1-linux exception_tests: gcc-4.0.1-linux exception_tests_debug: gcc-4.0.1-linux file_iterator_tests: gcc-4.0.1-linux file_iterator_tests_debug: gcc-4.0.1-linux fixed_size_queue_tests: gcc-4.0.1-linux fixed_size_queue_tests_debug: gcc-4.0.1-linux for_p_as_parser_tests: gcc-4.0.1-linux for_tests: gcc-4.0.1-linux for_tests_debug: gcc-4.0.1-linux fundamental_tests: gcc-4.0.1-linux fundamental_tests_debug: gcc-4.0.1-linux grammar_def_test: gcc-4.0.1-linux grammar_def_test_debug: gcc-4.0.1-linux grammar_mt_tests: gcc-4.0.1-linux grammar_multi_instance_tst: gcc-4.0.1-linux grammar_multi_instance_tst_debug: gcc-4.0.1-linux grammar_tests: gcc-4.0.1-linux grammar_tests_debug: gcc-4.0.1-linux group_match_bug: gcc-4.0.1-linux group_match_bug_debug: gcc-4.0.1-linux if_p_as_parser_tests: gcc-4.0.1-linux if_p_int_as_condition_test: gcc-4.0.1-linux if_p_int_as_condition_test_debug: gcc-4.0.1-linux if_tests: gcc-4.0.1-linux if_tests_debug: gcc-4.0.1-linux lazy_tests: gcc-4.0.1-linux lazy_tests_debug: gcc-4.0.1-linux loops_tests: gcc-4.0.1-linux loops_tests_debug: gcc-4.0.1-linux match_tests: gcc-4.0.1-linux match_tests_debug: gcc-4.0.1-linux multi_pass_compile_tests: gcc-4.0.1-linux multi_pass_tests: gcc-4.0.1-linux multi_pass_tests_debug: gcc-4.0.1-linux negated_eps_p_test: gcc-4.0.1-linux negated_eps_p_test_debug: gcc-4.0.1-linux numerics_tests: gcc-4.0.1-linux numerics_tests_debug: gcc-4.0.1-linux operators_tests: gcc-4.0.1-linux operators_tests_debug: gcc-4.0.1-linux owi_mt_tests: gcc-4.0.1-linux owi_st_tests: gcc-4.0.1-linux owi_st_tests_debug: gcc-4.0.1-linux parametric_tests: gcc-4.0.1-linux parametric_tests_debug: gcc-4.0.1-linux parser_context_test: gcc-4.0.1-linux parser_context_test_debug: gcc-4.0.1-linux parser_traits_tests: gcc-4.0.1-linux parser_traits_tests_debug: gcc-4.0.1-linux position_iterator_tests: gcc-4.0.1-linux position_iterator_tests_debug: gcc-4.0.1-linux primitives_tests: gcc-4.0.1-linux gcc-4.0.1-linux primitives_tests_debug: gcc-4.0.1-linux repeat_ast_tests: gcc-4.0.1-linux repeat_ast_tests_debug: gcc-4.0.1-linux rule_tests: gcc-4.0.1-linux rule_tests_debug: gcc-4.0.1-linux scanner_tests: gcc-4.0.1-linux scanner_tests_debug: gcc-4.0.1-linux scoped_lock_tests: gcc-4.0.1-linux scoped_lock_tests_debug: gcc-4.0.1-linux select_p_with_rule: gcc-4.0.1-linux select_p_with_rule_debug: gcc-4.0.1-linux sf_bug_720917: gcc-4.0.1-linux sf_bug_720917_debug: gcc-4.0.1-linux shortest_alternative_tests: gcc-4.0.1-linux shortest_alternative_tests_debug: gcc-4.0.1-linux subrule_tests: gcc-4.0.1-linux subrule_tests_debug: gcc-4.0.1-linux switch_problem: gcc-4.0.1-linux switch_problem_debug: gcc-4.0.1-linux switch_tests_eps_default: gcc-4.0.1-linux switch_tests_eps_default_debug: gcc-4.0.1-linux switch_tests_general_def: gcc-4.0.1-linux switch_tests_general_def_debug: gcc-4.0.1-linux switch_tests_single: gcc-4.0.1-linux switch_tests_single_debug: gcc-4.0.1-linux switch_tests_wo_default: gcc-4.0.1-linux switch_tests_wo_default_debug: gcc-4.0.1-linux symbols_add_null: gcc-4.0.1-linux symbols_add_null_debug: gcc-4.0.1-linux symbols_find_null: gcc-4.0.1-linux symbols_find_null_debug: gcc-4.0.1-linux symbols_tests: gcc-4.0.1-linux symbols_tests_debug: gcc-4.0.1-linux traverse_tests: gcc-4.0.1-linux traverse_tests_debug: gcc-4.0.1-linux while_p_as_parser_tests: gcc-4.0.1-linux while_tests: gcc-4.0.1-linux while_tests_debug: gcc-4.0.1-linux |static_assert| static_assert_example_2: gcc-4.0.1-linux |test| algorithms_test: gcc-4.0.1-linux auto_unit_test_test: gcc-4.0.1-linux auto_unit_test_test_mult: gcc-4.0.1-linux basic_cstring_test: gcc-4.0.1-linux boost_check_equal_str: gcc-4.0.1-linux class_properties_test: gcc-4.0.1-linux custom_exception_test: gcc-4.0.1-linux errors_handling_test: gcc-4.0.1-linux fixed_mapping_test: gcc-4.0.1-linux foreach_test: gcc-4.0.1-linux ifstream_line_iterator_test: gcc-4.0.1-linux online_test: gcc-4.0.1-linux output_test_stream_test: gcc-4.0.1-linux parameterized_test_test: gcc-4.0.1-linux result_report_test: gcc-4.0.1-linux test_case_template_test: gcc-4.0.1-linux test_fp_comparisons: gcc-4.0.1-linux test_tools_test: gcc-4.0.1-linux token_iterator_test: gcc-4.0.1-linux |thread| test_barrier: gcc-4.0.1-linux test_barrier_lib: gcc-4.0.1-linux test_condition: gcc-4.0.1-linux test_condition_lib: gcc-4.0.1-linux test_mutex: gcc-4.0.1-linux test_mutex_lib: gcc-4.0.1-linux test_once: gcc-4.0.1-linux test_once_lib: gcc-4.0.1-linux test_read_write_mutex: gcc-4.0.1-linux test_read_write_mutex_lib: gcc-4.0.1-linux test_thread: gcc-4.0.1-linux test_thread_lib: gcc-4.0.1-linux test_tss: gcc-4.0.1-linux test_tss_lib: gcc-4.0.1-linux test_xtime: gcc-4.0.1-linux test_xtime_lib: gcc-4.0.1-linux |timer| timer_test: gcc-4.0.1-linux |tokenizer| examples: gcc-4.0.1-linux simple_example_1: gcc-4.0.1-linux simple_example_2: gcc-4.0.1-linux simple_example_3: gcc-4.0.1-linux simple_example_4: gcc-4.0.1-linux simple_example_5: gcc-4.0.1-linux |tuple| io_test: gcc-4.0.1-linux tuple_test_bench: gcc-4.0.1-linux |type_traits| add_const_test: gcc-4.0.1-linux add_cv_test: gcc-4.0.1-linux add_pointer_test: gcc-4.0.1-linux add_reference_test: gcc-4.0.1-linux add_volatile_test: gcc-4.0.1-linux aligned_storage_test: gcc-4.0.1-linux alignment_of_test: gcc-4.0.1-linux decay_test: gcc-4.0.1-linux extent_test: gcc-4.0.1-linux function_traits_test: gcc-4.0.1-linux has_nothrow_assign_test: gcc-4.0.1-linux has_nothrow_constr_test: gcc-4.0.1-linux has_nothrow_copy_test: gcc-4.0.1-linux has_trivial_assign_test: gcc-4.0.1-linux has_trivial_constr_test: gcc-4.0.1-linux has_trivial_copy_test: gcc-4.0.1-linux has_trivial_destructor_test: gcc-4.0.1-linux has_virtual_destructor_test: gcc-4.0.1-linux is_abstract_test: gcc-4.0.1-linux is_arithmetic_test: gcc-4.0.1-linux is_array_test: gcc-4.0.1-linux is_base_and_derived_test: gcc-4.0.1-linux is_base_of_test: gcc-4.0.1-linux is_class_test: gcc-4.0.1-linux is_compound_test: gcc-4.0.1-linux is_const_test: gcc-4.0.1-linux is_convertible_test: gcc-4.0.1-linux is_empty_test: gcc-4.0.1-linux is_enum_test: gcc-4.0.1-linux is_float_test: gcc-4.0.1-linux is_floating_point_test: gcc-4.0.1-linux is_function_test: gcc-4.0.1-linux is_fundamental_test: gcc-4.0.1-linux is_integral_test: gcc-4.0.1-linux is_member_func_test: gcc-4.0.1-linux is_member_obj_test: gcc-4.0.1-linux is_member_pointer_test: gcc-4.0.1-linux is_object_test: gcc-4.0.1-linux is_pod_test: gcc-4.0.1-linux is_pointer_test: gcc-4.0.1-linux is_polymorphic_test: gcc-4.0.1-linux is_reference_test: gcc-4.0.1-linux is_same_test: gcc-4.0.1-linux is_scalar_test: gcc-4.0.1-linux is_signed_test: gcc-4.0.1-linux is_stateless_test: gcc-4.0.1-linux is_union_test: gcc-4.0.1-linux is_unsigned_test: gcc-4.0.1-linux is_void_test: gcc-4.0.1-linux is_volatile_test: gcc-4.0.1-linux rank_test: gcc-4.0.1-linux remove_all_extents_test: gcc-4.0.1-linux remove_bounds_test: gcc-4.0.1-linux remove_const_test: gcc-4.0.1-linux remove_cv_test: gcc-4.0.1-linux remove_extent_test: gcc-4.0.1-linux remove_pointer_test: gcc-4.0.1-linux remove_reference_test: gcc-4.0.1-linux remove_volatile_test: gcc-4.0.1-linux tricky_abstract_type_test: gcc-4.0.1-linux tricky_add_pointer_test: gcc-4.0.1-linux tricky_function_type_test: gcc-4.0.1-linux tricky_incomplete_type_test: gcc-4.0.1-linux tricky_is_enum_test: gcc-4.0.1-linux tricky_partial_spec_test: gcc-4.0.1-linux type_with_alignment_test: gcc-4.0.1-linux udt_specialisations: gcc-4.0.1-linux |utility| addressof_test: gcc-4.0.1-linux assert_test: gcc-4.0.1-linux base_from_member_test: gcc-4.0.1-linux binary_search_test: gcc-4.0.1-linux call_traits_test: gcc-4.0.1-linux compressed_pair_test: gcc-4.0.1-linux iterators_test: gcc-4.0.1-linux next_prior_test: gcc-4.0.1-linux numeric_traits_test: gcc-4.0.1-linux operators_test: gcc-4.0.1-linux ref_ct_test: gcc-4.0.1-linux ref_test: gcc-4.0.1-linux result_of_test: gcc-4.0.1-linux shared_iterator_test: gcc-4.0.1-linux value_init_test: gcc-4.0.1-linux |variant| recursive_variant_test: gcc-4.0.1-linux variant_comparison_test: gcc-4.0.1-linux variant_reference_test: gcc-4.0.1-linux variant_test1: gcc-4.0.1-linux variant_test2: gcc-4.0.1-linux variant_test3: gcc-4.0.1-linux variant_test4: gcc-4.0.1-linux variant_test5: gcc-4.0.1-linux variant_test6: gcc-4.0.1-linux variant_test7: gcc-4.0.1-linux variant_test8: gcc-4.0.1-linux variant_visit_test: gcc-4.0.1-linux |wave| test_re2c_lexer: gcc-3.2.3-linux gcc-4.0.1-linux test_slex_lexer: gcc-3.2.3-linux gcc-4.0.1-linux testwave: gcc-3.3.6-linux gcc-4.0.1-linux

2 1

User reports showing regressions...
by David Abrahams 13 Aug '05

13 Aug '05

...for newly added compilers! Boost.Python has apparently regressed for vc-8.0 How can that be? -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 4

[iostreams-1.33] bzip2.jam display message
by Yuval Ronen 13 Aug '05

13 Aug '05

There's a minor problem in libs/iostreams/build/bzip2.jam. There's no semicolon at the end of line 24, which causes the message to be displayed not quite right, when running bjam to build Boost. If this was already reported, then I apologize. Searching the archives revealed nothing. I guess I'm the only one who reads the messages at the beggining of the build ;-) Yuval

2 1

[1.33.0 zip version] Broken Images & Broken Links
by Pavel Chikulaev 13 Aug '05

13 Aug '05

Hi everyone, There is at least two bugs in zip version: 1) Corrupted image /libs/ptr_container/doc/cboost.gif (on site everythins is ok) Also it's an old logo, should that be img src in \libs\ptr_container\doc\ptr_container.html changed from /libs/ptr_container/doc/cboost.gif to /boost.png? As far as I know image is not corrupted in tar.bz2 version. 2) There is a broken link in /libs/program_options/doc/index.html which incorrectly redirects to ../../../doc/html/program_option.html instead of ../../../doc/html/program_options.html Same on site and another distributions. Can these things be changed until more people download it? -- With best regards, Pavel Chikulaev.

3 2

[iostreams] Typo in docs
by Caleb Epstein 12 Aug '05

12 Aug '05

In http://boost.org/libs/iostreams/doc/tutorial/container_sink.html "Finally, I should mention that the Iostremas library easier ways..." Note misspelling of Iostreams and the missing verb. "Offers" perhaps? -- Caleb Epstein caleb dot epstein at gmail dot com

2 1

[bind] Named placeholders and TR1
by Christopher Kohlhoff 12 Aug '05

12 Aug '05

Hi all, As part of the asio library I have been using named placeholders for the common arguments to callback functions. For example: asio::async_send_n(sock, buffer, length, boost::bind(mycallback, asio::arg::error, asio::arg::last_bytes_sent, asio::arg::total_bytes_sent)); rather than: asio::async_send_n(sock, buffer, length, boost::bind(mycallback, _1, _2, _3)); I find having named placeholders saves time and helps prevent errors to do with the ordering of the parameters (e.g. in the case of something like the last_bytes_sent/total_bytes_sent example where both are size_t, and so incorrect order will not be detected by the compiler). Unfortunately, from my reading of the TR1 bind doco at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1455.htm it simply defines the placeholders as: namespace std { namespace placeholders { extern unspecified _1; extern unspecified _2; extern unspecified _3; // implementation defined number of additional placeholders } } and it doesn't say anything about the type of the placeholders. Since the placeholders are CopyConstructible, it seems like I ought to be able to do something using a typedef (if there was one), e.g: std::placeholders::_1_t my_placeholder(std::placeholders::_1); Is there some TR1-compatible (and therefore portable) way of working around it that's eluding me (other than #define :). It seems a shame not to have such a feature, especially if over time more libraries use complex function objects in their interfaces. Cheers, Chris

3 3

1.33.0 is out the door...
by Douglas Gregor 12 Aug '05

12 Aug '05

... and so am I. I'll be checking e-mail periodically, but barring a release-related catastrophe I'll only be lurking for the next week or so. Doug

2 1

singleton and thread safety
by Jason Hise 12 Aug '05

12 Aug '05

I need to ensure that certain objects (specifically the policy bundles which manage singleton instances) are created in a thread-safe manner. First question: Can two threads both initialize the same static variable if they pass through the same function at the same time? Ex: void foo ( ) { static Thing t; } Can t's constructor be called twice by two threads executing foo? If so, I feel that I need to construct my policy bundles before execution enters main, a time when it is pretty much guaranteed that the application is operating in a single-threaded context. I thought that this would be simple to do: just write a class that calls the function with the static variable in its constructor and create a global instance of that class. However, the standard appears to say that initialization of such global variables can happen after main is entered, so long as it happens before the global variable is used. If the program starts spawning threads before the global variable is constructed I would still have the same problem. How can I ensure that initialization is performed before main is entered? If I cannot, is there some other way to make initialization of static variables thread-safe? I cannot lock a mutex to manage this, because the mutex lives inside the threading policy instance and the threading policy instance lives in the policy bundle that I am trying to create in the first place. -Jason

7 14

Re: [boost] Boost 1.33.0 released
by JOAQUIN LOPEZ MU?Z 12 Aug '05

12 Aug '05

----- Mensaje original ----- De: Doug Gregor <doug.gregor(a)gmail.com> Fecha: Viernes, Agosto 12, 2005 7:33 am Asunto: [boost] Boost 1.33.0 released > Boost 1.33.0 Congratulations and thank you for your efforts! Shouldn't a notice be posted to clc++ and clc++m? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Spelling error on the new boost.org home page
by Jeffrey Williams 12 Aug '05

12 Aug '05

On the new boost home page there is a spelling error in the section about what is new with the serialization library: "Improved seialization of shared pointers" Should be: "Improved serialization of shared pointers" Jeff

1 0

Minor inconcistencies on the website
by Arkadiy Vertleyb 12 Aug '05

12 Aug '05

FWIW: Formal review schedule/past review results, references FOREACH and TYPEOF libs not in the chronological order of acceptance. Also the link to the FOREACH macro in the file vault is not provided. Regards, Arkadiy

1 0

test boost-1.33 srpm
by Neal Becker 12 Aug '05

12 Aug '05

I placed my test boost-1.33 srpm here: http://nbecker.dyndns.org:8080/boost-1.33.0-6.src.rpm Basically, I modified the redhat 1.32 spec file: 1) Don't mess with soname 2) Autoconfigure icu support 3) Build all variants 4) Add my (little) patch for serializing mersenne_twister. Yes, I know it's not optimal, but it's simple and good enough for my purposes. Please comment.

3 3

[Config][auto_link] BOOST_LIB_TOOLSET override does not work as intended when multiple libraries are used
by Sean Huang 12 Aug '05

12 Aug '05

For example, if BOOST_LIB_TOOLSET is defined as "iw90" and both thread and signals libraries are used in a cpp file, compiler prints out the following: Linking to lib file: libboost_thread-iw90-mt-s-1_33.lib Linking to lib file: libboost_signals-iw-mt-s-1_33.lib The problem is caused by BOOST_LIB_TOOLSET being undefined at the end of auto_link.hpp. The second time auto_link.hpp is included (it has no include guards and is meant to be included multiple times) BOOST_LIB_TOOLSET is not defined anymore and a default value will be assigned. Does it really need to be undef'ed? Thanks, Sean

2 1

[1.33 RC2/regex] vc71.mak issues
by kalons＠yahoo.com 12 Aug '05

12 Aug '05

I had to make the following changes for this to build w/ VC7.1: Change line 38 to: MSVCDIR=$(VS71COMNTOOLS)..\..\VC7 Remove allocator.hpp and regex_library_include.hpp from line 57. -- --------------------------------------------------- Automate your software builds with Visual Build Pro http://www.visualbuild.com/

2 1

[test] basic_cstring_test errors
by Markus Schöpflin 12 Aug '05

12 Aug '05

basic_cstring_test currently fails to compile on the latest pre-release version of HP's cxx compiler. The following sample illustrates the problem: template <typename T> static void foo(T * t) { } template <typename T> void func() { foo((T *) 0); } // (*) int main() { func<int>(); return 0; } The call to foo at (*) doesn't find the declaration for foo because dependent name lookup for functions referred by an unqualified id only finds functions with external linkage. (See 14.6.4.2) A possible fix is to remove the static from the declaration of foo. Applied to basic_cstring_test, this would mean to remove the static from the declaration of test_string(). Markus

2 2

Merged from branch to trunk
by Douglas Gregor 12 Aug '05

12 Aug '05

I've just merged the changes on the RC_1_33_0 branch back to the trunk. There were no interesting conflicts to report. Doug

1 0

Confused about threading
by Neal Becker 12 Aug '05

12 Aug '05

I started out by trying to figure out if shared_ptr always uses threading. A quick look at the jamfiles did not suggest that threading was disabled when building single. Then I tried this: nm --demangle libboost_regex-d.a | grep -i thread [ lots of threading symbols ] OK, so why is the single threaded version of a library full of threading references? Is this a problem? Oh, this is gcc/linux system

2 1

[thread] assertion error when exiting app
by Felipe Magno de Almeida 12 Aug '05

12 Aug '05

Hi, I'm having an assertion failed when trying to finish my application. I use Boost.Thread to create one thread and use serialization and spirit that I know use threads either. It wasnt happening when using an earlier boost cvs version... And for some reason I'm not being able to debug it, when trying to the app finishes when reaching the MSVC. I'm using MSVC 7.1 and the assertion is: File: boost-path\libs\thread\build\..\src\tss_hooks.cpp Line: 131 Expression: attached_thread_count == 0 This application uses different threads to create and destroy objects throughout its lifetime(probably even the static/singleton objects). It is an COM object and is accessed through "RPC", where the creation of the singletons takes place... If anybody has any clue to what it could be, I would really appreciate. I'm going to update my boost to the RC2 and see what happens. Thanks in advance, Felipe. -- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."

2 5

regression on aix
by Toon Knapen 12 Aug '05

12 Aug '05

This week we upgraded our VisualAge compiler from 6.0.0.8 to 6.0.0.13 (because of problems with the preprocessor) which is the latest PTF (which is ibm speak for 'service pack'). We will thus also use this updated version to run the regression tests during the weekend (which are reported here: http://tinyurl.com/bms8v) However we will have *many* regressions because of compilation problems in some headers that are (indirectly) used in many places. For instance one problem is the gcc_3_2_wknd struct in mpl/has_xxx.hpp (see attached compiler error report). I fiddled around a bit with it and I do not understand why the compiler reports gcc_3_2_wknd to be an incomplete class. I also noted that defining gcc_3_2_wknd outside of the trait struct works. But this solution is also problematic from the moment the BOOST_MPL_HAS_XX_TRAIT_NAMED_DEF is used twice in which case the gcc_3_2_wknd will be defined twice ;-( Any suggestions are welcome! warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). ...patience... ...found 1200 targets... ...updating 444 targets... MkDir1 ../../../bin.v2/libs/mpl MkDir1 ../../../bin.v2/libs/mpl/test MkDir1 ../../../bin.v2/libs/mpl/test/largest_int.test MkDir1 ../../../bin.v2/libs/mpl/test/largest_int.test/vacpp MkDir1 ../../../bin.v2/libs/mpl/test/largest_int.test/vacpp/debug vacpp.compile.c++ ../../../bin.v2/libs/mpl/test/largest_int.test/vacpp/debug/largest_int.o **passed** ../../../bin.v2/libs/mpl/test/largest_int.test/vacpp/debug/largest_int.test MkDir1 ../../../bin.v2/libs/mpl/test/msvc_is_class.test MkDir1 ../../../bin.v2/libs/mpl/test/msvc_is_class.test/vacpp MkDir1 ../../../bin.v2/libs/mpl/test/msvc_is_class.test/vacpp/debug vacpp.compile.c++ ../../../bin.v2/libs/mpl/test/msvc_is_class.test/vacpp/debug/msvc_is_class.o **passed** ../../../bin.v2/libs/mpl/test/msvc_is_class.test/vacpp/debug/msvc_is_class.test MkDir1 ../../../bin.v2/libs/mpl/test/template_arity.test MkDir1 ../../../bin.v2/libs/mpl/test/template_arity.test/vacpp MkDir1 ../../../bin.v2/libs/mpl/test/template_arity.test/vacpp/debug vacpp.compile.c++ ../../../bin.v2/libs/mpl/test/template_arity.test/vacpp/debug/template_arity.o **passed** ../../../bin.v2/libs/mpl/test/template_arity.test/vacpp/debug/template_arity.test MkDir1 ../../../bin.v2/libs/mpl/test/advance.test MkDir1 ../../../bin.v2/libs/mpl/test/advance.test/vacpp MkDir1 ../../../bin.v2/libs/mpl/test/advance.test/vacpp/debug vacpp.compile.c++ ../../../bin.v2/libs/mpl/test/advance.test/vacpp/debug/advance.o "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-0062 (S) The incomplete class "gcc_3_2_wknd" must not be used as a qualifier. "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-0700 (I) The previous message was produced while processing "boost::mpl::aux::has_tag<iter<0>,struct mpl_::bool_<0> >::value". "../../../boost/mpl/aux_/has_tag.hpp", line 20.35: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::aux::has_tag<iter<0>,mpl_::bool_<0> >". "../../../boost/mpl/if.hpp", line 55.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<0>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<0> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<0>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<0>,mpl_::int_<10> >". "advance.cpp", line 35.2: 1540-0700 (I) The previous message was produced while processing "test35()". "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-1269 (S) The template argument for the non-type template parameter of type "bool" must be an integral constant expression. "../../../boost/mpl/if.hpp", line 63.68: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::aux::has_tag<iter<0>,mpl_::bool_<0> >". "../../../boost/mpl/if.hpp", line 55.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<0>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<0> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<0>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<0>,mpl_::int_<10> >". "advance.cpp", line 35.2: 1540-0700 (I) The previous message was produced while processing "test35()". "../../../boost/mpl/if.hpp", line 63.11: 1540-1122 (S) A non-type template parameter cannot have type "bool". "../../../boost/mpl/tag.hpp", line 33.7: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<0>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<0> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<0>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<0>,mpl_::int_<10> >". "advance.cpp", line 35.2: 1540-0700 (I) The previous message was produced while processing "test35()". "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-0062 (S) The incomplete class "gcc_3_2_wknd" must not be used as a qualifier. "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-0700 (I) The previous message was produced while processing "boost::mpl::aux::has_tag<iter<10>,struct mpl_::bool_<0> >::value". "../../../boost/mpl/aux_/has_tag.hpp", line 20.35: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::aux::has_tag<iter<10>,mpl_::bool_<0> >". "../../../boost/mpl/if.hpp", line 55.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<10>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<10> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<10>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<10>,mpl_::int_<-10> >". "advance.cpp", line 44.2: 1540-0700 (I) The previous message was produced while processing "test44()". "../../../boost/mpl/aux_/has_tag.hpp", line 20.1: 1540-1269 (S) The template argument for the non-type template parameter of type "bool" must be an integral constant expression. "../../../boost/mpl/if.hpp", line 63.68: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::aux::has_tag<iter<10>,mpl_::bool_<0> >". "../../../boost/mpl/if.hpp", line 55.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<10>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<10> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<10>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<10>,mpl_::int_<-10> >". "advance.cpp", line 44.2: 1540-0700 (I) The previous message was produced while processing "test44()". "../../../boost/mpl/if.hpp", line 63.11: 1540-1122 (S) A non-type template parameter cannot have type "bool". "../../../boost/mpl/tag.hpp", line 33.7: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::if_<boost::mpl::aux::has_tag<iter<10>,mpl_::bool_<0> >,boost::mpl::aux::tag_impl<iter<10> >,mpl_::void_>". "../../../boost/mpl/tag.hpp", line 31.57: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::tag<iter<10>,mpl_::void_>". "../../../boost/mpl/advance.hpp", line 56.8: 1540-0700 (I) The previous message was produced while processing "struct boost::mpl::advance<iter<10>,mpl_::int_<-10> >". "advance.cpp", line 44.2: 1540-0700 (I) The previous message was produced while processing "test44()". /usr/vacpp/bin/xlC -c -DBOOST_ALL_NO_LIB=1 -qNOOPTimize -qnoinline -g -qeh -qrtti -I"../../.." -o "../../../bin.v2/libs/mpl/test/advance.test/vacpp/debug/advance.o" "advance.cpp"

1 0

Re: [boost] New boost webpage
by Martin Bonner 12 Aug '05

12 Aug '05

----Original Message---- From: Andreas Huber [mailto:ahd6974-spamgroupstrap@yahoo.com] Sent: 09 August 2005 21:24 To: boost(a)lists.boost.org Subject: Re: [boost] New boost webpage > Aleksey Gurtovoy wrote: >> Beth Jacobson writes: >>> David Abrahams wrote: >>>> Beth, your proposals sound interesting... but they'd be a whole lot >>>> easier to evaluate if you'd just make up the page or CSS stuff >>>> required and post it where we can all get a look at it. >>>> >>> >>> Done. The test page is up at http://bajac.com/boost/ >> >> Could we please, please get this rolled in 1.33? IMO this is a huge >> improvement in terms of the page readability. > > That's also my opinion (I did like some tiny details of the old page > better but that could be taken care of for 1.34). > > Regards, I really like the new link colouring. It seems to me that embedding links in continous text in a way that is a) easy to ignore when you are reading the text and b) easy to find when you are looking for the link, is essentially a hard problem. I would argue that Beth has got about as close as we are going to get (although I believe Rene objects to underlines). It WOULD be really nice to get this in to 1.33, but on the other hand I am not sure we have a consensus yet AND it is awfully late in the day to be making /any/ changes to the release. Final question: How do we go about establishing if we have a consensus or not so that we can at least update the main boost website? (Even if we can't include in 1.33). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

9 12

[1.33.0] RC_1_33_0 branch is CLOSED
by Douglas Gregor 12 Aug '05

12 Aug '05

The 1.33.0 release branch is now closed. Doug

2 2

[RFC] Alternative any design
by Pablo Aguilar 12 Aug '05

12 Aug '05

[I got an error when sending, please excuse me if this shows up twice] Hi, First of all, thanks to everyone who's commented on the proposed any alternative. Given that the alignment issue doesn't seem to be easy to solve, I'm thinking of giving up on trying to align correctly, and just skip the "in place storing of value" optimization when it might be an issue. So I'm wondering, is the following a proper way to detect alignment problems? <code> typedef void* any_buffer_base_type; // could be customized int const ANY_BUFFER_SIZE = sizeof(any_buffer_base_type); union object_holder { char buffer[ANY_BUFFER_SIZE]; void* pointer; any_buffer_base_type alignment_dummy_; }; template<typename T> struct optimize { enum { T_size_ = sizeof(T) , base_size_ = sizeof(any_buffer_base_type) , size_ok_ = (T_size_ <= base_size_) , T_align_ = alignment_of<T>::value , base_align_= alignment_of<any_buffer_base_type>::value , align_ok_ = ((base_align_ % T_align_) == 0) , value = size_ok_ && align_ok_ }; }; </code> I looked at Optional's alignment tecnique, and couldn't come up with how to use it, given that the stored type for any changes at runtime. If there's something I missed about this, any help would be welcome. My current solution is to use the above shown code (assuming it works, of course!), and fall back on heap based storage when optimization is deemed not possible. The 2nd question I had to ask is, how should any's alignment type be specified, with a configuration macro or through a template parameter? I haven't posted an updated version, given that there's some issues (other than alignment) still requiring attention. Thanks in advance for any help you might provide, Pablo Aguilar

1 0

[RFC] Alternative any design
by Pablo Aguilar 12 Aug '05

12 Aug '05

Hi, First of all, thanks to everyone who's commented on the proposed any alternative. Given that the alignment issue doesn't seem to be easy to solve, I'm thinking of giving up on trying to align correctly, and just skip the "in place storing of value" optimization when it might be an issue. So I'm wondering, is the following a proper way to detect alignment problems? <code> typedef void* any_buffer_base_type; // could be customized int const ANY_BUFFER_SIZE = sizeof(any_buffer_base_type); union object_holder { char buffer[ANY_BUFFER_SIZE]; void* pointer; any_buffer_base_type alignment_dummy_; }; template<typename T> struct optimize { enum { T_size_ = sizeof(T) , base_size_ = sizeof(any_buffer_base_type) , size_ok_ = (T_size_ <= base_size_) , T_align_ = alignment_of<T>::value , base_align_= alignment_of<any_buffer_base_type>::value , align_ok_ = ((base_align_ % T_align_) == 0) , value = size_ok_ && align_ok_ }; }; </code> I looked at Optional's alignment tecnique, and couldn't come up with how to use it, given that the stored type for any changes at runtime. If there's something I missed about this, any help would be welcome. My current solution is to use the above shown code (assuming it works, of course!), and fall back on heap based storage when optimization is deemed not possible. The 2nd question I had to ask is, how should any's alignment type be specified, with a configuration macro or through a template parameter? I haven't posted an updated version, given that there's some issues (other than alignment) still requiring attention. Thanks in advance for any help you might provide, Pablo Aguilar

1 0

[wave] No dynamic lib?
by Neal Becker 12 Aug '05

12 Aug '05

I notice that 1.33.0-rc2 doesn't build dynamic libs for wave. Is this intentional?

2 3

Re: [boost] [thread] assertion error when exiting app
by Sean Huang 11 Aug '05

11 Aug '05

> I didnt understand your solution... > You call on_thread_exit in the end of the threads that are created > with boost::thread ? Even if there are, possibly, other(COM) threads > running? It has nothing to do with boost::thread. I call on_thread_exit on any threads that use boost::thread_specific_ptr. on_thread_exit can be called multiple times so this workaround works with boost::thread too. One thing important is you cannot use boost::thread_specific_ptr after the call. I would consider this as a hack not a solution. Sean

1 0

archive stuck?
by Gennadiy Rozental 11 Aug '05

11 Aug '05

I don't see this month messages here: http://lists.boost.org/boost/2005/08/date.php Gennadiy

3 4

Linker Error During Compilation of Function
by Mottengte, Rajeev Kumar 11 Aug '05

11 Aug '05

Hi I am getting linker errors during compilation of functions which is returning object of class boost::archive::text_iarchive. The error is "In Copy constructor 'boost::archive::basic_text_iprimitive<> ..... boost::scoped_ptr<T> is private. So I changed the scoped_ptr to public manually in the scoped_ptr.hpp file. After that I am getting an error undefined reference to boost::scoped_ptr<std::locale>. Can any body tell me how to resolve this problem. Rgds Rajeev

1 0

Re: [boost] alignment problem in proposed any alternative
by Martin Bonner 11 Aug '05

11 Aug '05

----Original Message---- From: christopher diggins [mailto:cdiggins@videotron.ca] Sent: 11 August 2005 14:00 To: boost(a)lists.boost.org Subject: Re: [boost] alignment problem in proposed any alternative [snip] > 3.9(2) says: > For any complete POD object type T, whether or not the object holds a > valid value of type T, the underlying > bytes (1.7) making up the object can be copied into an array of char > or unsigned char.36) If the content of the array of char or unsigned > char is copied back into the object, the object shall subsequently > hold its original value. > > This has nothing to do with void* and char*, but rather with all > POD's. > > This clearly implies char arrays are stringently aligned. Err, no it doesn't. It says that you can store the bits of a POD object into a char array, and then load the bits back into the same (correctly aligned) POD object. It does *NOT* say that you can use the address of the char array as if it were the address of the POD object. For example: #include <assert.h> int main() { long pod = 3141L; char pad; char c[sizeof(pod)]; memcpy( c, &pod, sizeof(pod) ); pod = 42L; memcpy( &pod, c, sizeof(pod) ); assert (pod == 3141L); // 3.9(2) requires this assert to pass. // nothing requires THIS assert to pass, and on some systems it fail // because c is not suitable aligned. assert ( *reinterpret_cast<long*>(&c[0]) == 3141L ); return 0; } -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

4 3

thread library mutexes in Windows 95
by Jorge Lodos 11 Aug '05

11 Aug '05

Hi I'm trying to use the the boost::thread::mutex class in a Windows 95 project. Since the generated .lib files for the thread library include InterlockedCompareExchange (used in try_mutex::call_once) I was left with the option of adding the mutex.cpp and the exceptions.cpp files to my project and compiling them separately. Building the program included at the end, MSCV 7.1 gives the following linker errors: Compiling... Mutex.cpp Linking... mutex1.obj : error LNK2019: unresolved external symbol "void __cdecl boost::call_once(void (__cdecl*)(void),long &)" (?call_once@boost@@YAXP6AXXZAAJ@Z) referenced in function "bool __cdecl `anonymous namespace'::has_TryEnterCriticalSection(void)" (?has_TryEnterCriticalSection@?A0x5deb84cd@@YA_NXZ) mutex1.obj : error LNK2019: unresolved external symbol "int __cdecl boost::xtime_get(struct boost::xtime *,int)" (?xtime_get@boost@@YAHPAUxtime@1@H@Z) referenced in function "private: bool __thiscall boost::timed_mutex::do_timedlock(struct boost::xtime const &)" (?do_timedlock@timed_mutex@boost@@AAE_NABUxtime@2@@Z) Debug/Mutex.exe : fatal error LNK1120: 2 unresolved externals call_once is called in try_mutex constructor, while xtime_get is called in timed_mutex::do_timedlock. Nor try_mutex or timed_mutex are used at all. This was confirmed by commenting out the whole implementation for both in mutex.cpp, in which case the program links without problems. Just commenting out the lines m_critical_section = has_TryEnterCriticalSection(); in the try_mutex constructor and boost::xtime_get(&cur, boost::TIME_UTC); in timed_mutex::do_timedlock makes the program link. I originally expected the linker will remove all try_mutex and timed_muted implementation but it does not. Can someone give any ideas on how to use boost::mutex in a MSCV 7.1 project for Windows 95 without having to modify the original files? Is there a reason for the linker not to remove all the code for try_mutex and timed_mutex? Thanks in advance. Best regards Jorge #define BOOST_THREAD_NO_LIB #include <boost/thread/mutex.hpp> // mutex.cpp and exceptions.cpp compiled with // BOOST_THREAD_NO_LIB preprocessor option. // This must be enforced, since they both #include // <boost/thread/detail/config.hpp> int main(int argc, char *argv[ ]) { boost::mutex mymutex; boost::mutex::scoped_lock scoped_lock(mymutex); }

1 0

Boost regression notification (2005-08-11)
by Douglas Gregor 11 Aug '05

11 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-11T14:40:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

[1.33 RC2/serialization] New failures on Intel 8.1
by Stefan Slapeta 11 Aug '05

11 Aug '05

Hi, the latest changes seem to cause new failures on Intel 8.1 ("internal failure...") that are once again related to the buggy debug info generation in this compiler version. After investigating, I'm afraid I can't offer anything but to mark them as expected :-( Stefan

2 1

Re: [boost] alignment problem in proposed any alternative
by felipe 11 Aug '05

11 Aug '05

> Date: Thu, 11 Aug 2005 09:00:20 -0400 > From: christopher diggins <cdiggins(a)videotron.ca> > Subject: Re: [boost] alignment problem in proposed any alternative > To: boost(a)lists.boost.org > Message-ID: <004c01c59e74$a17a7800$2b792518@heronnest> > Content-Type: text/plain; format=flowed; charset=iso-8859-1; > reply-type=original > ----- Original Message ----- > From: "felipe" <pbr(a)taric.es> > To: <boost(a)lists.boost.org> > Sent: Thursday, August 11, 2005 4:09 AM > Subject: Re: [boost] alignment problem in proposed any alternative > >> Nope, this is totally wrong! chars and arrays of type char are >> generally >> the least aligned objects. You can demonstrate that this doesn't work >> with something like this: >> >> void blah() >> { >> char c[/* some number */]; >> any<8> a((double)1.0); >> std::cout << &a << std::endl; >> } > That code is completely misleading, yhe question is not what the address > of > a is! > Well, let me clarify: /*############ BEGIN ########*/ #include <iostream> #include <boost/type_traits.hpp> template<int buffer_size> struct any { char c; // this offsets buffer by one-byte.. because for the // compiler, chars only need byte alignment char buffer[buffer_size]; // ... template<typename T> any(const T& x) { if (boost::is_pod<T>::value && (sizeof(T) <= buffer_size)) { memcpy(buffer, &x, sizeof(T)); } else { // new and stuff } } }; int main(int argc, char **argv) { any<8> blah((double)1.0); std::cout << (void *)&blah.buffer << std::endl; return 0; } /*##### END ########*/ Output of the program on Pentium/Win2k/Visual C++ 6.0: 0x22ef01 This is obviously NOT a good place for a double, unless you are going to memcpy everything, which would be a needlessly inefficient design. Right, the Pentium lets me slide (with some extra instructions to keep away idle cycles), but don't try it on an Alpha! Have you not read the articles by Alexandrescu in CUJ? These are pretty old and yet they explore all of this stuff. What you should do is make the buffer a union of a minimal size object (e.g. your char array) and a minimum alignment object (e.g. a double in the example above). The compiler then adjusts alignment for the latter, while guaranteeing space for the former. Another thing, your proposal shies away from objects with constructors, etc. Why? You can use the placement new operator and get a much cleaner implementation. You know, something like this: template<typename T> any(const T& x) { .. new(&buffer[0]) T(x); // instead of memcpy hope this helps -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

Self Contained Transportable Class :
by Mottengte, Rajeev Kumar 11 Aug '05

11 Aug '05

Hi I am trying to create a self contained transportable class which can be migrated to any machine by calling a member function in it. I am having the socket stream implementation which derives the transportable boost class. In the serialize function of the boost class, I am trying to get the string stream and trying to call network marshal function of the base class. How can I get the stream ( I am using a string stream ) from the archive class inside the serialize function. Rgds Rajeev

1 0

Re: [boost] alignment problem in proposed any alternative
by felipe 11 Aug '05

11 Aug '05

Nope, this is totally wrong! chars and arrays of type char are generally the least aligned objects. You can demonstrate that this doesn't work with something like this: void blah() { char c[/* some number */]; any<8> a((double)1.0); std::cout << &a << std::endl; } Tweak the size of c[] until you get &a % 8 != 0. Some compilers optimize stack layout, over-aligning data, but this is true only for SOME compilers on SOME processors with SOME optimization settings. (You can also experiment by defining an additional char variable before the buffer in your any. Where does &a.buffer lie?) I think you are misreading 3.9.2: it is talking about pointers, namely that void * and char * have the same storage and alignment requirements. On Wed, 10 Aug 2005 20:27:16 +0200, <boost-request(a)lists.boost.org> wrote: > From: "christopher diggins" <cdiggins(a)videotron.ca> > To: "Boost mailing list" <boost(a)lists.boost.org> > Sent: Wednesday, August 10, 2005 1:30 AM > Subject: [boost] alignment problem in proposed any alternative >> The question I have is whether in practice though are there are any >> compilers which have stricter alignment requirements on small types (<= >> sizeof(void*)) than a void pointer. In other words, is it possible with >> any >> known compiler to actually throw the runtime error ? > Now a moot point, see below. > >> Unfortunately there is another problem, I am not an expert in >> interepreting >> the standard, but AFAICT placement new is guaranteed to return a pointer >> to >> properly aligned memory (3.7.3.1 / 2) which I leverage to check that >> alignment occured. Apparently not every STL implementation does in fact >> do >> that (I believe at least dinkumware is guilty of that). > Apparently I am wrong about this! 18.4.1.3 provides an exception. (I > wonder > why I missed the exception 15 chapters later?) > Anyway it turns out we can guarantee alignment by simply using a char > buffer. According to 3.9/2 the following automatically has no alignment > problems: > template<int buffer_size> > struct any { > char buffer[buffer_size]; > ... > template<typename T> > any(const T& x) { > if (boost::is_pod<T>::value && (sizeof(T) <= buffer_size)) { > memcpy(buffer, &T, N); > } > else { > // new and stuff > } > } > } > Christopher Diggins -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

3 2

[1.33.0] Release candidate #2 is available
by Douglas Gregor 11 Aug '05

11 Aug '05

Boost 1.33.0 release candidate #2 is now available at the usual place: http://www.osl.iu.edu/~dgregor/boost-1.33.0/ Please build it, test it, and report back to the mailing list. If no major problems are found before August 9th, this release candidate will become Boost 1.33.0. Doug Gregor 1.33.0 Release Manager

12 19

Compilation error with regex only with -O3 on gcc
by robert kraus 11 Aug '05

11 Aug '05

Hi, when I compile with: -O0 to -O2 my programs compile and work fine, but when I switch to -O3 I get compilation errors (shortened, see below). Is this my fault (maybe I shouldnt use optimizations? thank you very much for your answers ido fedora core 4,gcc version: Target: i386-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,java,f95,ada --enable-java-awt=gtk --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --host=i386-redhat-linux Thread model: posix gcc version 4.0.1 20050727 (Red Hat 4.0.1-5) boost: boost-devel-1.32.0-6 Errors: Building file: ../src/Parser.cpp Invoking: GCC C++ Compiler g++ -DDEBUG -O3 -g3 -pedantic -Wall -c -fmessage-length=0 -osrc/Parser.o ../src/Parser.cpp /usr/include/boost/regex/v4/regex_compile.hpp: In member function ‘boost::re_detail::re_syntax_base* boost::reg_expression<charT, traits, Allocator>::compile_set_simple(boost::re_detail::re_syntax_base*, long unsigned int, bool) [with charT = char, traits = boost::regex_traits<char>, Allocator = std::allocator<char>]’: /usr/include/boost/regex/v4/regex_compile.hpp:1635: instantiated from ‘unsigned int boost::reg_expression<charT, traits, Allocator>::set_expression(const charT*, const charT*, boost::regex_constants::syntax_option_type) [with charT = char, traits = boost::regex_traits<char>, Allocator = std::allocator<char>]’ /usr/include/boost/regex/v4/basic_regex.hpp:238: instantiated from ‘unsigned int boost::reg_expression<charT, traits, Allocator>::set_expression(const charT*, boost::regex_constants::syntax_option_type) [with charT = char, traits = boost::regex_traits<char>, Allocator = std::allocator<char>]’ /usr/include/boost/regex/v4/regex_compile.hpp:110: instantiated from ‘boost::reg_expression<charT, traits, Allocator>::reg_expression(const charT*, boost::regex_constants::syntax_option_type, const Allocator&) [with charT = char, traits = boost::regex_traits<char>, Allocator = std::allocator<char>]’ /usr/include/boost/regex/v4/basic_regex.hpp:340: instantiated from ‘boost::basic_regex<charT, traits, Allocator>::basic_regex(const charT*, typename boost::reg_expression<charT, traits, Allocator>::flag_type, const Allocator&) [with charT = char, traits = boost::regex_traits<char>, Allocator = std::allocator<char>]’ ../src/Parser.cpp:16: instantiated from here __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

Re: [boost] [format] Inconsistency with printf
by martin.ecker＠tab.at 11 Aug '05

11 Aug '05

Sorry about the previous, empty e-mail. We were having mail server problems at my company. Below is the content of my original mail: Hello, The following sample program: #include <cstdio> #include <iostream> #include <limits> #include <boost/format.hpp> int main(int argc, char* argv[]) { std::cout << boost::format("%f") % std::numeric_limits<float >::infinity() << std::endl; std::printf("%f", std::numeric_limits<float>::infinity()); return 0; } produces 1.00000000000000000000000000....00000000000000000.#INF00 with Boost.Format, but 1.#INF00 with printf. Is this a bug or shouldn't I expect the same behavior from Boost.Format for special floating point values such as NaN and infinity? Note that using %g instead of %f, that is: std::cout << boost::format("%g") % std::numeric_limits<float>::infinity() << std::endl; prints the same thing as printf, i.e. 1.#INF00 This is using Boost 1.32.0 with MSVC 7.1 on Windows. Best Regards, Martin TAB Austria Haiderstraße 40 4052 Ansfelden Austria Phone: +43 7229 78040-218 Fax: +43 7229 78040-209 E-mail: martin.ecker(a)tab.at http://www.tab.at

1 0

Re: [boost] surveying async network io libraries
by Matthew Nourse 11 Aug '05

11 Aug '05

>On 8/10/05, Jose <jmalv04_at_[hidden]> wrote: > >The asio library really looks quite nice. It appears simple to use, >is 100% header-based, doesn't require the use of threads, and uses the >most scalable event demultiplexor supplied by the OS (epoll on Linux >in the 0.3x version and IOCP on Windows). Its a very nice little >library! Thanks for linking to it. I think I'm in love :-) I've been writing asio apps for a closed-source software company for the last 16 months. With asio, I've written: * a custom HTTP proxy that has been running in production non-stop since October last year * an HTTP<->XMPP gateway * a simple asio-based HTTP load test tool (so I can simulate 20,000 simultaneous HTTP "clients" from a single process) * a publish/subscribe server with a simple binary protocol- am still trying to performance tune other code so I can find the limits of this, so far 500 messages/sec doesn't cause any detectable CPU usage on a 3GHz P4. * A second custom HTTP proxy- this one does some authentication as well. The first application runs on Windows and the rest run on Debian Linux. They all share HTTP/networking code where applicable. All applications use boost::bind and boost::shared_ptr extensively and the publish/subscribe server uses boost::regex to figure out how to route requests. I am addicted to asio. I can't stop using it ;-). Matt

1 0

Interest for a perl6-like-junctions-class?
by FlSt＠gmx.de 11 Aug '05

11 Aug '05

Hi! The new Perl 6 has a nice feature called junctions. See http://www.perl.com/pub/a/2003/07/29/exegesis6.html?page=4 and http://www.metaperl.com/talks/p6-junctions/ for more information. I think this is a interesting way to save the time for writing loops in some situations. I've tried to implement this for C++ and uploaded a version with two examples into the Boost Sandbox File Vault (flos_super_position.zip). This version works for my purposes, but if you interested i would rework it and submit it to the boost library. Sincerely, Florian S.

13 95

shared_ptr and threads
by Timothy Ritchey 11 Aug '05

11 Aug '05

We are using shared_ptr extensively in our application, and seem to be having some threading issues. In particular, we have an Envelope class that is used to hold messages received over the network. We use Spirit to parse the message string and construct the Envelope object, then we pass is on to the EnvelopeController, which holds a thread pool to handle all of the Envelopes. These Envelopes are passed around as shared_ptr<Envelope> between these different components. In essense, we have one thread that is receiving the message from the network stack, parsing it, and passing it to the thread_pool, which is then using one (or more) additional threads to actually deal with the contents of the envelope. On a Uni-processor box, everything works great. All of our envelopes are being destroyed properly. On a multi-processor machine, none of the envelopes are getting destroyed. We are in a situation where two shared_ptrs to the same underlying object may go out of scope and need to decrement the ref count at the same time. Is the in the realm of "undefined behavior?" Am I using the shared_ptr incorrectly? Thanks for any advice. Thread 1 --------- { shared_ptr<Envelope> envelope(new Envelope(...)); ... [pass envelope to Thread 2] ... [envelope goes out of scope] } Thread 2 -------- void process(shared_ptr<Envelope> envelope) { [do work on envelope] [envelope goes out of scope] }

2 2

[Boost-bugs] [ boost-Bugs-1256121 ] 1.33 R1/R2's shared_ptr crashes due to inlining in CW PPC
by SourceForge.net 10 Aug '05

10 Aug '05

Bugs item #1256121, was opened at 2005-08-10 12:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1256121&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Peter Dimov (pdimov) Summary: 1.33 R1/R2's shared_ptr crashes due to inlining in CW PPC Initial Comment: Hello. My name is John Daub, email: hsoi(a)hsoi.com. I am using CodeWarrior Pro 9.5 on a dual G5/2GHz PowerMac (PPC). I believe the version of boost that I am using is 1.33 R1 as version.hpp says 1.33 and since 1.33 R2 was released only 2 days ago, I figure I must be using R1 (I didn't put boost into our CVS repository... someone else did that so I can't say what version of boost I have any more than that). However, I did check the 1.33 R2 and it seems to have the same problem. Going back to 1.32 however, I do not have the problem. It appears to be something introduced in 1.33. The problem stems from my use of the boost::shared_ptr class, and then ultimately how shared_ptr uses sp_counted_base to track the useCount. It seems boost 1.33 has introduced compiler and processor specific implementations of sp_counted_base. In the CodeWarrior PPC version (boost/detail/ sp_counted_base_cw_ppc.hpp) there are 3 inline functions: atomic_increment, atomic_decrement, atomic_conditional_increment. These 3 inline functions use inline assembly to do their work. That's fine. However, if you set the CW compiler to build with "don't inline", things work out fine. You can run and play and no problems. If however you set the CW compiler to "smart" inlining, then you will crash because these atomic functions don't work for some reason. FWIW, the other inlining options are set as follows: auto-inline is off, deferred inling is off, bottom-up inlining is on. You should be able to reproduce this yourself. I used my CW Pro 9.5 install and created a new project based upon the Mac OS C++ Stationery (the Mac OS Carbon, Standard Console, C++ Console Carbon, stationery). I added an access path to my boost library folder, and I added your own test file from boost-distro/libs/ smart_ptr/shared_ptr_test.cpp to the project. I changed nothing else about the project... just stock CodeWarrior stationery. If you ensure inlining is set to "don't inline", build, and it runs fine. If you then go back, change the setting to "smart" inlining, rebuild, and then run, you should see the console window comes up, some stuff appears in the window but quickly things crash. The problem is the useCount doesn't seem to increment, so when it later decrements, the count is off and things go wrong. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1256121&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Improved boost::any
by christopher diggins 10 Aug '05

10 Aug '05

I have developed a type very similar to boost::any which requires less memory and significantly reduces the number of allocations / deallocations. If anyone is interested I have posted a brief article about it at CodeProject http://www.codeproject.com/useritems/dynamic_typing.asp and I have uploaded the source to the vault ( http://boost-sandbox.sourceforge.net/vault/index.php ). Is there any interest? Christopher Diggins http://www.cdiggins.com

7 14

[Boost-bugs] [ boost-Bugs-1256069 ] 1.32.0 signals and shared_ptr mem-leak bug
by SourceForge.net 10 Aug '05

10 Aug '05

Bugs item #1256069, was opened at 2005-08-10 11:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1256069&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Peter Dimov (pdimov) Summary: 1.32.0 signals and shared_ptr mem-leak bug Initial Comment: The attached file shows a discrepancy with boost 1.31 and 1.32 when dealing with shared_ptr's and signals. The 1.32 behavior can cause memory leaks in certain conditions. camior(a)gmail.com David J. Sankel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1256069&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] New boost webpage
by Martin Bonner 10 Aug '05

10 Aug '05

----Original Message---- From: Beth Jacobson [mailto:bethj@bajac.com] Sent: 08 August 2005 21:27 To: boost(a)lists.boost.org Subject: Re: [boost] New boost webpage > Rob Stewart wrote: >> From: Aleksey Gurtovoy <agurtovoy(a)meta-comm.com> >> >>> They are blending with the text now, which is IMO a step back. >> >> >> They are more readable, however, and I find them sufficiently >> distinguished from the surrounding text. > > I just changed the link colors to their websafe versions. I can't see > any difference on my browser, but it may make things more consistent > across different browsers/OS's. It could be that you've been seeing > different colors. Hopefully this will fix that. I've just checked the site. I cannot see any difference between visited and unvisited links now (unless visited links are supposed to be paler). Can't we have a change of hue as well as lightness/saturation? -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

Boost regression notification (2005-08-10)
by Douglas Gregor 10 Aug '05

10 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-10T15:06:17Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

[Boost-bugs] [ boost-Bugs-1255637 ] 1.33RC2: archive_pointer_[o/i]serializer assert problem
by SourceForge.net 10 Aug '05

10 Aug '05

Bugs item #1255637, was opened at 2005-08-10 02:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1255637&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: 1.33RC2: archive_pointer_[o/i]serializer assert problem Initial Comment: Hello again, FYI .. i read the boost mailing list, so posting anwers there is ok for me ;-) I made some progress after reading "rationale" though some things still give headaches. I have polymorphic class hierarchy which gets serialized thru base ptrs (along with shared_ptr stuff). When using portable_binary_oarchive/iarchive (taken from boost example) an assert() triggers which raises some questions. oserializer.hpp: -------------- snip -------------- // sice true_type is valid, and this only gets made if the // pointer oserializer object has been created, this should never fail bpos_ptr = archive_pointer_oserializer<Archive>::find(* true_type); assert(NULL != bpos_ptr); if(NULL == bpos_ptr) boost::throw_exception( archive_exception(archive_exception::unregistered_class) ); -------------- snip -------------- "should never fail" seems to fail and i dont know why ;-( (long callstack omitted) > test_protocollayers.exe!boost::archive::detail::save_pointer_type<portable_binary_oarchive,xxx::ProtocolHeader const *>::polymorphic<xxx::ProtocolHeader>::save(portable_binary_oarchive & ar={...}, const xxx::ProtocolHeader & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x00000000) Line 416 C++ test_protocollayers.exe!boost::archive::detail::save_pointer_type<portable_binary_oarchive,xxx::ProtocolHeader const *>::save<xxx::ProtocolHeader>(portable_binary_oarchive & ar={...}, const xxx::ProtocolHeader & t={...}, const boost::archive::detail::basic_pointer_oserializer * bpos_ptr=0x00000000) Line 438 + 0x11 C++ test_protocollayers.exe!boost::archive::detail::save_pointer_type<portable_binary_oarchive,xxx::ProtocolHeader const *>::invoke(portable_binary_oarchive & ar={...}, const xxx::ProtocolHeader * const t=0x00680698) Line 466 + 0x11 C++ test_protocollayers.exe!boost::archive::save<portable_binary_oarchive,xxx::ProtocolHeader const *>(portable_binary_oarchive & ar={...}, const xxx::ProtocolHeader * const & t=0x00680698) Line 535 + 0xf C++ The classes usually contain: "template<class Archive> void serialize( Archive & ar, const unsigned int /* version */)" stuff, along with explicit: "boost::serialization::void_cast_register<Derived, Base>(0,0);" in ctors (or it doesnt work). "this_type" = abstract base "true_type" = derived both classes are successfully retrieved via type info (registered class). The "vp = serialization::void_downcast(*true_type, *this_type, &t);" works too (because the void_cast_register). But it doesnt find appropriate basic_pointer_oserializer .... I placed a breakpoint at "basic_serializer_map::insert(const basic_serializer * bs)" to see what types get registered at startup (initterm ctors). There are indeed registrations but some (derived) types are missing. What gives? BTW ... could you make "portable_binary_oarchive" (and iarchive) included in available boost archive types? I find it useful because serialization is used in cross platform protocol stacks (little vs. big endian archs). Is there any chance to reduce binary overhead due to registration data (shared_ptr/type info ... binary size almost doubled due to contained type info in small payloads). Can stringified type info be omitted/shortened (i use hierachial namespaces which blow the length)? Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1255637&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

[serialization] two problems
by Vladimir Prus 10 Aug '05

10 Aug '05

Hi, after "cvs up" is run into two new problems with serialization. First is missing include, patch attached. The second is this: gcc.compile.c++ ../../../src/runtime/bin/gcc/debug/threading-multi/runtime_standalone.o In file included from /space/NM/boost/boost/archive/detail/iserializer.hpp:47, from /space/NM/boost/boost/archive/basic_binary_iarchive.hpp:36, from /space/NM/boost/boost/archive/binary_iarchive.hpp:21, from ../../../src/runtime/runtime_standalone.cpp:14: /space/NM/boost/boost/serialization/is_abstract.hpp:30: error: redefinition of `struct boost::is_abstract<T>' /space/NM/boost/boost/type_traits/is_abstract.hpp:130: error: previous definition of `struct boost::is_abstract<T>' The second patch addresses this problem, but I'd also suggest to remove boost/serialization/is_abstract.hpp to avoid further problems. This happens in CVS HEAD, but I suspect the same problems might be present on release branch, and so should be merged there. - Volodya

2 5

[format] Inconsistency with printf
by martin.ecker＠tab.at 10 Aug '05

10 Aug '05

1 0

Re: [boost] alignment problem in proposed any alternative
by Martin Bonner 10 Aug '05

10 Aug '05

----Original Message---- From: christopher diggins [mailto:cdiggins@videotron.ca] Sent: 10 August 2005 06:30 To: Boost mailing list Subject: [boost] alignment problem in proposed any alternative > The question I have is whether in practice though are there are any > compilers which have stricter alignment requirements on small types > (<= sizeof(void*)) than a void pointer. I don't know of any such compilers, but I /can/ conceive of such. A (16-bit) word addressed machine where sizeof(int*) is 4 but sizeof(void*) is 6 might have the required alignment of int be 4, but the required alignment of void* only be 2 :-( On the other hand, it might be acceptable to say "boost::any" is not supported on such machines. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

Re: [boost] Improved boost::any
by felipe 10 Aug '05

10 Aug '05

hello and good day to all, Well, I posted earlier about this, but yes, if you are going make a decent "any" with stack-allocation, you should let the maximum buffer size be variable. I didn't go into details about alignment or exceptions because I think it's pretty much old news. (In his article "Discriminated Unions", Andrei Alexandrescu considers all of this, however I don't totally agree with his implementation--too hairy for the 9-to-5 programmer.) My own recommendation is that both alignment and buffer size be adjustable. By default they should have sensible values. For example, 8 for both gives decent results on a lot of platforms, although you could do better with the help of sizeof and alignment_of. Besides simplifying the class definition, letting the programmer tweak alignment can be useful for types that can benefit from extra alignment. An example might be a character array--it only "needs" byte alignment, but maybe all of the string operations are tweaked for 32-bit alignment. Somebody made a rather interesting question, whether an object having size less than void * might need alignment greater than void *. Well, about the only maxim the C/C++ standards give is that alignment is platform dependent. In practice, I've never seen such a strange case. I think that sizeof(X) <= sizeof(Y) is a pretty good indicator that alignment(X) <= alignment(Y). (But remember, "minimum-acceptable" alignment is not the same as "optimum" alignment--my pentium lets me store and fetch a double at 0xDEADBEEF, but these operations aren't cheap!) Also, be careful with alignment_of: I remember it giving me some strange values on some illegal but idiomatic structures (e.g. zero-length arrays). If it gives you zero, put 8 or something you think is sensible. hope this helps On Tue, 09 Aug 2005 18:07:06 +0200, <boost-request(a)lists.boost.org> wrote: > Date: Tue, 09 Aug 2005 10:17:48 -0400 > From: christopher diggins <cdiggins(a)videotron.ca> > Subject: Re: [boost] Improved boost::any > To: boost(a)lists.boost.org > Message-ID: <026101c59ced$1ee4a3d0$2b792518@heronnest> > Content-Type: text/plain; format=flowed; charset=iso-8859-1; > reply-type=original > ----- Original Message ----- > From: "Vladimir Prus" <ghost(a)cs.msu.su> >> >> If the trick is to use "void*" pointer to data for storing data when >> it's >> small, then: >> >> - it's interesting to see performance comparison for any<string>, or >> any<some_other_large_class> > Another part of the optimization, is to avoid reallocating when > reassigning > any a different value with the same type. > On a related note: several people have suggested that a buffer should be > used with an arbitrary size set at compile time, which would help > significantly for container types. > >> - can't this be just patch to boost::any, as opposed to completely >> different >> class? > What does submitting a patch entail? Is that the way to go if the > implementation is completely different? > - Chriostopher Diggins -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

[Boost-bugs] [ boost-Bugs-1254062 ] 1.33 RC2: polymorphic stuff broken further??
by SourceForge.net 10 Aug '05

10 Aug '05

Bugs item #1254062, was opened at 2005-08-08 03:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1254062&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: 1.33 RC2: polymorphic stuff broken further?? Initial Comment: Hello again, i just downloaded 1.33 RC2 and noticed polymorphic serialization doesnt work for my projects anymore. These errors are new and different from RC1 (which didnt work too, but 1.32 works). I cant get it compile anymore (static compile time asserts and others)... I even loaded up the provided sample boost ser. projects and notice there are similar errors too (from libs\serialization\vc7ide\*.sln) ---- demo_exception demo_exception.cpp e:\SDK\Boost\boost_1_33_0_RC2\libs\serialization\vc7ide\..\..\..\boost\archive\detail\oserializer.hpp(566) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] e:\SDK\Boost\boost_1_33_0_RC2\libs\serialization\vc7ide\..\..\..\boost\archive\detail\oserializer.hpp(566) : see reference to class template instantiation 'boost::STATIC_ASSERTION_FAILURE<x>' being compiled with [ x=false ] e:\SDK\Boost\boost_1_33_0_RC2\libs\serialization\vc7ide\..\..\..\boost\archive\basic_text_oarchive.hpp(78) : see reference to function template instantiation 'void boost::archive::save<Archive,T>(Archive &,T & )' being compiled with [ Archive=boost::archive::text_oarchive, T=School * ] e:\SDK\Boost\boost_1_33_0_RC2\libs\serialization\vc7ide\..\..\..\boost\archive\detail\interface_oarchive.hpp(85) : see reference to function template instantiation 'void boost::archive::basic_text_oarchive<Archive>::save_override<T>(T & ,int)' being compiled with [ Archive=boost::archive::text_oarchive, T=School * ] \SDK\Boost\boost_1_33_0_RC2\libs\serialization\example\demo_exception.cpp(219) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_oarchive<Archive>::operator <<<School*>(T & )' being compiled with [ Archive=boost::archive::text_oarchive, T=School * ] (iserializer is same problem:) Boost\boost_1_33_0_RC2\libs\serialization\vc7ide\..\..\..\boost\archive\detail\iserializer.hpp(544) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' (similar to error in my projects) These errors go away if i make objects to be serialized "const" e.g. (for the sample) school* const .. ???? This "constness" constraint didnt show up in 1.32. It is especially difficult to enforce it if you serialize members with "ar & m1 & m2 .. " notation. ----- demo_shared_ptr: Boost\boost_1_33_0_RC2\libs\serialization\example\demo_shared_ptr.cpp(138) : error C2039: 'sp_counted_base_impl' : is not a member of 'boost::detail' Boost\boost_1_33_0_RC2\libs\serialization\example\demo_shared_ptr.cpp(138) : error C2061: syntax error : identifier 'sp_counted_base_impl' .... There are some errors with invalid project references and library names at all (linker errors, tries to link with wrong libs). It seems the project files are out of sync for long time. ---------------- Additionally: boost\boost\archive\detail\interface_iarchive.hpp(73) : error C2039: 'basic_iarchive' : is not a member of 'boost::archive::polymorphic_iarchive' boost\boost\archive\polymorphic_iarchive.hpp(52) : see declaration of 'boost::archive::polymorphic_iarchive' boost\boost\archive\detail\interface_iarchive.hpp(72) : while compiling class-template member function 'void boost::archive::detail::interface_iarchive<Archive>::lookup_helper(const boost::serialization::extended_type_info *const ,boost::shared_ptr<T> &)' boost\boost\archive\detail\interface_iarchive.hpp(73) : error C2662: 'boost::archive::detail::basic_iarchive::lookup_basic_helper' : cannot convert 'this' pointer from 'boost::archive::polymorphic_iarchive' to 'boost::archive::detail::basic_iarchive &' Reason: cannot convert from 'boost::archive::polymorphic_iarchive' to 'boost::archive::detail::basic_iarchive' Conversion requires a second user-defined-conversion operator or constructor This is my include list (i use precompiled header): ... #include "boost/archive/polymorphic_oarchive.hpp" #include "boost/archive/polymorphic_iarchive.hpp" #include "boost/serialization/shared_ptr.hpp" #include "boost/serialization/serialization.hpp" #include "boost/serialization/utility.hpp" #include "boost/serialization/list.hpp" #include "boost/serialization/version.hpp" #include "boost/serialization/map.hpp" #include "boost/serialization/vector.hpp" #include "boost/serialization/string.hpp" #include "boost/serialization/split_member.hpp" (i had to move "boost/serialization/shared_ptr.hpp" backwards after "archive" headers in contrast to 1.32) These 1.33 poly serialization bugs are big showstoppers for us because we extensively use serialization. If they remain, 1.33 will have to be skipped... Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1254062&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

3 4

Custom allocator for shared_ptr
by Dave 10 Aug '05

10 Aug '05

Hello all, I assume that the reference count object pointed to by shared_ptr objects is on the heap. Is there a way that I can specify a custom allocator for shared_ptr to use for this purpose? Thanks, Dave

4 3

[mpl] sort algorithm complexity
by Felipe Magno de Almeida 10 Aug '05

10 Aug '05

In the page it is informed that sort has an average complexity of O(nlog n), but I'm writing this: template <typename T, typename U> struct sort_hierarchy_pred : mpl::not_< boost::is_base_and_derived<T, U> >::type { }; typedef mpl::back_inserter< mpl::vector<> > aux_in; template <typename SequenceT> struct sort_hierarchies : public mpl::sort<SequenceT, typename mpl::lambda<sort_hierarchy_pred<mpl::_, mpl::_> >::type , aux_in> {}; and for a sequence of 5 or more, the compile time and memory usage gets too huge. To became unuseable. What I'm trying to achieve is a sequence of types that are sorted with the bases first... Could anybody shed some light why and if there's some workaround this? thanks in advance, Felipe. -- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."

3 10

Problem with writing a dijkstra_visitor
by Fabian Buske 09 Aug '05

09 Aug '05

Hi, I'm trying to write a dijkstra visitor, that sets the weight of an egde to the maximum value after assigning it to a minimum spanning tree. The visitor is created according to the bacon sample: template <typename WeightMap> class special_dijkstra_visitor : public boost::default_dijkstra_visitor { public: special_dijkstra_visitor(WeightMap& w):default_dijkstra_visitor(),weight_map_(w){}; template <typename Edge, typename Graph> void edge_relaxed(Edge e, Graph& g) { weight_map_[e] = DBL_MAX; } template <class Edge, class Graph> void edge_not_relaxed(Edge e, Graph& g) { weight_map_[e] = DBL_MAX; } private: WeightMap weight_map_; }; // Convenience function template <typename WeightMap> special_dijkstra_visitor<WeightMap> visit_special_dijkstra(WeightMap w) { return special_dijkstra_visitor<WeightMap>(w); } The graph based on an adjacency matrix with property<edge_weight_t, double> The visitor is called by: property_map<Graph, edge_weight_t>::type weightmap = get(edge_weight, g); prim_minimum_spanning_tree(g, root, &p[0], distance, weightmap, indexmap, visitor(visit_special_dijkstra(weightmap))); The linux gnu 3.4.4 compiler gives the following error messages *snip template instance error messages* /zeug/study/OpenMSLibs/CGAL-3.1-gcc-3.4.4/include/boost/graph/dijkstra_shortest_paths.hpp:120: error: ` edge_relaxed' undeclared (first use this function) /zeug/study/OpenMSLibs/CGAL-3.1-gcc-3.4.4/include/boost/graph/dijkstra_shortest_paths.hpp:122: error: ` edge_not_relaxed' undeclared (first use this function) /zeug/study/OpenMSLibs/CGAL-3.1-gcc-3.4.4/include/boost/graph/dijkstra_shortest_paths.hpp:143: error: ` finish_vertex' undeclared (first use this function) ... I'm wondering, cause I thought deriving from default_dijkstra_visitor ensures that finish_vertex is allready implemented. Compiling the bacon sample on the same graph works fine. So I'm really confused. Any hints for debugging the code? Thanks a lot. Regards Fabian

2 1

Boost regression notification (2005-08-09)
by Douglas Gregor 09 Aug '05

09 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-09T14:43:35Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Re: [boost] Improved boost::any
by Eyal Farago 09 Aug '05

09 Aug '05

I read the code project article and I have few comments: 1. why optimize only for types smaller than void*? you can specify a different max size (bigger than sizeof(void*) and probably a product of it with another integer) to achieve even better results. 2. the implementation is pretty messy and quite dangerous, I'm quite sure it wouldn't compile/work on multimple platforms, and the first one that pops into my mind is solaris which enforce proper alighnment... 3. it is possible to borrow some of the tricks boost::variant uses to achieve correct allignment. i.e. using a boost::variant<void*, char[/*buffer size here*/]> and when the buffer is used store the actual alignment in a member variable of the class. 4. if 3 isn't possible, look at boost::function implementation, but I'm not sure if they're using a buffer or a simple union with a void* and few other types... eyal. -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org]On Behalf Of christopher diggins Sent: Tuesday, August 09, 2005 12:49 AM To: Boost mailing list Subject: [boost] Improved boost::any I have developed a type very similar to boost::any which requires less memory and significantly reduces the number of allocations / deallocations. If anyone is interested I have posted a brief article about it at CodeProject http://www.codeproject.com/useritems/dynamic_typing.asp and I have uploaded the source to the vault ( http://boost-sandbox.sourceforge.net/vault/index.php ). Is there any interest? Christopher Diggins http://www.cdiggins.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] Improved boost::any
by felipe 09 Aug '05

09 Aug '05

hello and good day, Yes, this is actually not unlike the my own implementation of "any". But rather than limit myself to objects that fit in sizeof(void *) bytes, I keep an aggregate member whose size is governed by a template parameter with a default value of sizeof(void *). This way I can arbitrarily specify the mininum size at which objects are heap-allocated. I think this is probably the way to go for discriminant unions.. the typelist solution is just to messy for my tastes, and boost::any is too consumptive. Anyone interested? sincerely, Phillip On Tue, 09 Aug 2005 01:49:45 +0200, <boost-request(a)lists.boost.org> wrote: > Message: 19 > Date: Mon, 08 Aug 2005 18:48:39 -0400 > From: christopher diggins <cdiggins(a)videotron.ca> > Subject: [boost] Improved boost::any > To: Boost mailing list <boost(a)lists.boost.org> > Message-ID: <016001c59c6b$51e3e250$2b792518@heronnest> > Content-Type: text/plain; format=flowed; charset=iso-8859-1; > reply-type=original > I have developed a type very similar to boost::any which requires less > memory and significantly reduces the number of allocations / > deallocations. > If anyone is interested I have posted a brief article about it at > CodeProject http://www.codeproject.com/useritems/dynamic_typing.asp and I > have uploaded the source to the vault ( > http://boost-sandbox.sourceforge.net/vault/index.php ). Is there any > interest? > Christopher Diggins > http://www.cdiggins.com > ----------------------------- -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

1 0

Re: [boost] cross_iterator
by BARTLETT, Peter, FM 08 Aug '05

08 Aug '05

>Alex wrote: >[cross_iterator] >Please take a look and let me know what you think. A great start but, if I understand correctly, there is a significant difference with how zip_iterator works. The zip_iterator's dereference method returns a tuple of references to the underlying values, whereas your cross_iterator just returns the tuple of iterators themselves. Thus to use cross_iterator with standard algorithms, the user would have to provide a function object that acts on iterators rather than values which is unusual and unintuitive. Thus to me it seems like cross_iterator needs to borrow much of the TMP code from the detail of zip_iterator (assuming the community is happy with how that class works). Conceptually the two classes only differ in the ++ and -- operators. Pete Bartlett *********************************************************************************** The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. Authorised and regulated by the Financial Services Authority This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by The Royal Bank of Scotland plc in this regard and the recipient should carry out such virus and other checks as it considers appropriate. Visit our websites at: http://www.rbs.co.uk/CBFM http://www.rbsmarkets.com ********************************************************************************

2 1

cross_iterator
by Alex Mendes da Costa 08 Aug '05

08 Aug '05

Hi folks, A cross_iterator is to a zip_iterator as a cross_product is to a dot_product. For example, given two sequences { a, b }, { 1, 2 }, the sequence of tuples generated by a cross_iterator would be { ( a, 1 ), ( b, 1 ), ( a, 2 ), ( b, 2 ) }. I've put my implementation of cross_iterator in the sandbox (cross_iterator.zip @ http://boost-sandbox.sourceforge.net/vault/) There's no documentation yet, but I've included a sample file that demonstrates how to use the new iterator. Please take a look and let me know what you think. Alex

2 2

[Range] Doc typo [in 1.33.0 RC2]
by Pablo Aguilar 08 Aug '05

08 Aug '05

In the FAQ page, the first answer says: "... that a sub_range do propagate const-ness" ^^ I believe it should say "does" Pablo

2 1

Boost regression notification (2005-08-08)
by Douglas Gregor 08 Aug '05

08 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-08T14:56:20Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. pool Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 19 failures in 4 libraries: lambda (15) pool (1) rational (2) wave (1) |lambda| algorithm_test: vc-7_1 bind_tests_advanced: vc-7_1 bind_tests_simple: vc-7_1 bind_tests_simple_f_refs: vc-7_1 bll_and_function: vc-7_1 constructor_tests: vc-7_1 control_structures: vc-7_1 exception_test: vc-7_1 extending_rt_traits: vc-7_1 is_instance_of_test: vc-7_1 lambda_cast_test: vc-7_1 member_pointer_test: vc-7_1 operator_tests_simple: vc-7_1 phoenix_control_structures: vc-7_1 switch_construct: vc-7_1 |pool| test_pool_alloc: vc-7_1 |rational| rational_example: vc-7_1 rational_test: vc-7_1 |wave| testwave: vc-7_1

3 2

Boost Library with Socket++ Library :
by Mottengte, Rajeev Kumar 08 Aug '05

08 Aug '05

Hi I tried to use boost library along with Socket++ for network serialization. I have created a socket++ class osockinet which is derived from iostream. I have given this class to boost archive constructor instead of the normal fstream class for archive to redirect to network. Rest of the code is same. I am getting segmentation fault. Can anybody help me on this. It is in Fedora Linux. ThanX & Rgds Rajeev

1 0

Error in Boost.MultiIndex Examples documentation
by Michael Goldshteyn 08 Aug '05

08 Aug '05

Example 6: complex searches and foreign keys See source code. This program illustrates some advanced techniques that can be applied for complex data structures using multi_index_container. Consider a car_model class for storing information about automobiles. On a first approach, car_model can be defined as: struct car_model { std::string model; std:string manufacturer; int price; }; This definition has a design flaw that any reader acquainted with relational databases can easily spot: The manufacturer member is duplicated among all cars having the same manufacturer. --- This definition also has a syntax error that any C++ programmer can easily spot! :) Mike

2 1

[filesystem] path normalization?
by Vladimir Prus 08 Aug '05

08 Aug '05

Hello, suppose I have this: path p = .........; p /= "../../../a/b/c" ; with current CVS version of filesystem I get paths like: bin/gcc/debug/threading-multi/../../../../bin/nm/debug/threading-multi/print_and_set.map which are correct, but it has reduntant elements. Say first ".." undoes "threading-multi" and next ".." undoes "debug" and the path is the same as bin/nm/debug/threading-multi/print_and_set.map which is much smaller, and so better for things like error diagnostic. Any change that filesystem perform such path normalization either during operator/= or as a separator function? TIA, Volodya

2 2

Re: [boost] [intel-9.0] --arg_dep_lookup, BOOST_FUNCTION_SCOPE_USING_DECLARATION_BREAKS_ADL and__EDG _VERSION__=304
by JOAQUIN LOPEZ MU?Z 08 Aug '05

08 Aug '05

----- Mensaje original ----- De: John Maddock <john(a)johnmaddock.co.uk> Fecha: Domingo, Agosto 7, 2005 11:39 am Asunto: Re: [boost] [intel-9.0] -- arg_dep_lookup,BOOST_FUNCTION_SCOPE_USING_DECLARATION_BREAKS_ADL and__EDG _VERSION__=304 > >Could it be that Intel compilers under Linux also necessitate > >the --arg_dep_lookup compiler switch (which is currently not > >set)? This looks like the only sensible conslusion from > >the facts described. > > Unfortunately *not* setting that switch has no effect on the Win32 > compiler > (at least not as far as this bug is concerned). I have a test > case for this > bug sitting in my "bug-reports" directory so it looks this has > been > submitted to Intel before, as soon as I can boot up Linux again, > I'll verify > that I can reproduce it and have a play around with the command > line > switches. > Thank you! Would you mind reporting your findings back to the list when you get something? Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 3

[mpl]suggested addition in vault/cppljevans/mpl/child_i_depth_j.zip
by Larry Evans 08 Aug '05

08 Aug '05

child_i_depth_j allows the traversal of a tree of applications. It's useful for accessing, for example, the i-th superclass of the results of mpl/fold, as demonstrated by the test file: libs/mpl/test/child_i_depth_j_test.cpp included in the zip file mentioned in the subject line. Could this be added to mpl? Is there something I could do to facilitate this addition? -regards Larry

4 9

SF CVS outage, fyi...
by Rene Rivera 07 Aug '05

07 Aug '05

( 2005-08-04 10:34:06 - Project CVS Service ) Starting on 2005-08-09 at 09:00 Pacific, developer CVS service will be offline for a expected period of up to 36 hours to facilitate significant hardware upgrades. Developer CVS service is moving from its current home on a 4 x 700MHz PIII, 500GB RAID5, 4GB RAM host to a new host that has roughly quadruple the I/O performance: a 2 x 2.8GHz Xeon, 1TB RAID5 striped, 8GB RAM host. Further announcements of CVS service improvements will occur in the weeks following this hardware upgrade (CVS sync delay is not yet eliminated, but that is on our list to complete). -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

1 0

[1.33.0] Unintentional dependency
by David Abrahams 07 Aug '05

07 Aug '05

I just realized that Boost.Parameter contains a dependency on boost/python/detail/is_xxx.hpp that I meant to fix before release by moving is_xxx.hpp into boost/detail. I'm certainly willing to wait until after 1.33.0 to fix this, but people complained bitterly about dependencies on boost/python/detail/indirect_traits.hpp before I did the same refactorization there. Doug, what do you think? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 2

Boost regression notification (2005-08-07)
by Douglas Gregor 07 Aug '05

07 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-07T15:09:19Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

1 0

Boost regression notification (2005-08-06)
by Douglas Gregor 06 Aug '05

06 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-06T15:20:18Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 12 failures in 1 library: serialization (12) |serialization| test_list_binary_archive: cw-9_5-darwin test_list_binary_archive_dll: cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_5-darwin test_list_ptrs_text_archive: cw-9_5-darwin test_list_ptrs_text_warchive: cw-9_5-darwin test_list_ptrs_xml_archive: cw-9_5-darwin test_list_ptrs_xml_warchive: cw-9_5-darwin test_list_text_archive: cw-9_5-darwin test_list_text_warchive: cw-9_5-darwin test_list_xml_archive: cw-9_5-darwin test_list_xml_warchive: cw-9_5-darwin

3 2

Boost on FreeBSD [patch]
by Simon Barner 06 Aug '05

06 Aug '05

Dear Boost developers, I am currently testing a CVS snapshot of the upcoming boost 1.33.0 release (from 07/31), and I found the attached patch is needed. This is because the T_DIVIDE macro is already declared in the FreeBSD header file /usr/include/machine/trap.h, which is pulled via various other header files. Kind regards, Simon (maintainer of the FreeBSD boost port) P.S.: I'll try RC1 as soon as possible. P.P.S.: Please Cc: me in your replys, I'm not on the list. Thanks.

5 5

about icpc error
by Bo Liu 06 Aug '05

06 Aug '05

Hello Martin, Can you tell me how you got the following more-than-one-instance error resolved? /boost/head-regression/boost/boost/iostreams/copy.hpp(182): error: more than one instance of overloaded function "resolve" matches the argument list: function template "boost::iostreams::detail::resolve<Mode,Ch,Iter>(const boost::iterator_range<Iter> &)" function template "boost::iostreams::detail::resolve<Mode,Ch,T>(const T &, boost::disable_if<boost::iostreams::is_std_io<T>, void>::type *)" argument types are: (const boost::iterator_range<const char *>) return copy_impl(resolve<input, char_type>(src), wrap(snk), buffer_size); command: icpc -c -w1 -g -O0 -I"../bin/boost/libs/iostreams/test" -I"/boost/head-regression/boost" -o "../bin/boost/libs/iostreams/test/newline_filter_test.test/intel-8.1-linux/debug/newline_filter_test.o" "/boost/head-regression/boost/libs/iostreams/test/newline_filter_test.cpp" I got the googled link, http://64.233.187.104/search?q=cache:uEsi-MT1fegJ:www.jobmanager.com/engine…, when I ran into the similar problem. It seems that you have resolved problem since that page was removed. Thanks, -Bo __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Who's Using Boost?
by David Abrahams 06 Aug '05

06 Aug '05

I have two concerns about these pages: 1. They violate the library naming/branding conventions (http://www.boost.org/more/discussion_policy.htm#lib_names) 2. How shall we get http://www.boost.org/libs/python/projects.html integrated into it? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 3

CSS expert advice needed
by David Abrahams 06 Aug '05

06 Aug '05

It has frustrated me that footnotes are rendered in such extremely small type in the Parameter library documentation (http://www.boost-consulting.com/libs/parameter) but I can't tell what needs to change in the CSS to fix it. Can anyone help? Thanks, -- Dave Abrahams Boost Consulting www.boost-consulting.com

5 16

Name polution with boost::type_traits
by Ivan Godard 06 Aug '05

06 Aug '05

May I suggest that the type_traits identifiers all be placed in a boost::type_traits namespace, with one indirect #include file to grandfather existing usage? The added file, say hide_type_traits.hpp, would include all the detail .hpp files the way that type_traits.hpp does now. The individual detail files would wrap each API declaration in "namespace type_traits{...}". The present type_traits.hpp would simply: #include "hide_type_traits.hpp" namespace boost { using namespace type_traits; } The effect is that current usage will still work if you include type_traits.hpp as at present, but those of us who want the type_traits names (bit not the rest of boost) in the file namespace can do a "using boost::type_traits;" to achieve that. What prompts this note is a desire to prepare for TR1 while continuing to support old compilers. We attempted to say (in a file included when using an older compiler): namespace std { #include "boost/type_traits.hpp" } so that the boost type_traits identifiers would appear in the std namespace under an old compiler just as they would in a compiler that implements TR1. However, this blows up because the boost type_traits library transitively includes other boost stuff it uses, and that stuff does *not* like to be in std :-) Of course, we could leave all the identifiers in the boost space and pick them out one by one with using statements; that's in fact what we are doing. But that means we have to track your library with our using's, a maintenance nuisance. Lastly, may I suggest that future libraries with lots of identifiers should routinely use a per-module namespace, like the mpl library does now? That would obviate this nuisance should the library later be standardized. Ivan

2 1

Boost regression notification (2005-08-05)
by Douglas Gregor 05 Aug '05

05 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-05T15:10:44Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 34 failures in 3 libraries: iostreams (1) serialization (32) thread (1) |iostreams| mapped_file_test: intel-win32-9_0 |serialization| test_list_binary_archive: cw-9_4 cw-9_5-darwin test_list_binary_archive_dll: cw-9_4 cw-9_5-darwin test_list_ptrs_binary_archive: cw-9_4 cw-9_5-darwin test_list_ptrs_binary_archive_dll: cw-9_4 cw-9_5-darwin test_list_ptrs_text_archive: cw-9_4 cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_4 test_list_ptrs_text_warchive: cw-9_4 cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_4 test_list_ptrs_xml_archive: cw-9_4 cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_4 test_list_ptrs_xml_warchive: cw-9_4 cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_4 test_list_text_archive: cw-9_4 cw-9_5-darwin test_list_text_archive_dll: cw-9_4 test_list_text_warchive: cw-9_4 cw-9_5-darwin test_list_text_warchive_dll: cw-9_4 test_list_xml_archive: cw-9_4 cw-9_5-darwin test_list_xml_archive_dll: cw-9_4 test_list_xml_warchive: cw-9_4 cw-9_5-darwin test_list_xml_warchive_dll: cw-9_4 |thread| test_thread: vc-6_5

3 2

[1.33.0] [Serialization] Important: cw-9_4 failures
by Douglas Gregor 05 Aug '05

05 Aug '05

Lots of Serialization tests are failing: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/ developer/issues.html We need to resolve these before we can release RC2. Doug

3 2

[Type Traits, BoostBook] Lots of BoostBook parsing errors
by David Abrahams 05 Aug '05

05 Aug '05

xslt-xsltproc ../bin.v2/doc/gcc-3.4.4/debug/boost.docbook file:///boost/tools/boostbook/dtd//boostbook.dtd:412: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" %DocBook; ^ Entity: line 1: %DocBook; ^ src/boost.xml:345: parser error : Entity 'eacute' not defined <firstname>Hervé</firstname> ^ src/boost.xml:346: parser error : Entity 'ouml' not defined <surname>Brönnimann</surname> ^ src/boost.xml:701: parser error : Entity 'auml' not defined <surname>Järvi</surname> ^ ... ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:123: parser error : Entity 'nbsp' not defined struct</phrase> <link linkend="boost_typetraits.is_void">is_void</link><phr ^ ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:123: parser error : Entity 'nbsp' not defined ><phrase role="special"> :</phrase><phrase role="keyword"> public</phrase>  ^ ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:126: parser error : Entity 'nbsp' not defined struct</phrase> <link linkend="boost_typetraits.is_void">is_void</link><phr ^ ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:126: parser error : Entity 'nbsp' not defined ><phrase role="special"> :</phrase><phrase role="keyword"> public</phrase>  ^ ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:142: parser error : Entity 'nbsp' not defined struct</phrase> <link linkend="boost_typetraits.is_pointer">is_pointer</lin ^ ../bin.v2/libs/type_traits/doc/gcc-3.4.4/debug/type_traits.xml:142: parser error : Entity 'nbsp' not defined ><phrase role="special"> :</phrase><phrase role="keyword"> public</phrase>  ^ .... -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

[parameter] some typos in tutorial...
by Pavel Chikulaev 05 Aug '05

05 Aug '05

Hi David, There is a strange symbols in /libs/parameter/doc/html/index.html in section 2.6.2 after second function code with modifier . Absolutely the same in 2.7.2 and 2.7.3... In section 2.8.3 "Mnemonics" note can overlap code in that section when page less than 800 pixels wide. It's better to use tables IMO there. -- Pavel Chikulaev

7 14

[Range] No Reply?
by David Abrahams 05 Aug '05

05 Aug '05

Thorsten Ottosen <nesotto(a)cs.aau.dk> writes: > Citat David Abrahams <dave(a)boost-consulting.com>: > > Hi Dave, > >> >> Thorsten, >> >> there are important issues here that go to the suitability of this >> library for generic programming. I notice there was no answer on the >> list. It's crucial that you deal with these questions eventually, and >> IMO it should happen before the 1.33.0 release. >> > > I'll see what I can do. My laptop was stolen two weeks ago, so > its hard for me to do any real work. Ouch! I'm sorry to hear that! > When is 1.33.0 going to be? I think we're hoping to do a prerelease candidate this weekend or Monday. > Anyway, here's the issues: I'm not sure that you quite "got" most of the concerns I raised. > 1. change XXX to boost::XXX. ok, I don't see any problem with this. I > could fix it monday. -------------- If you already understood everything I'm writing in this section delimited by dashes, please just tell me so and I'll relax. I'm not asking for you to simply change XXX to boost::XXX everywhere. To quote from my original posting: > | 1. What does it take to get support for standard containers as ranges? > | According to what I can see in the documentation, the standard > | containers don't satisfy the range concepts. IOW, > | > | begin(v) > | > | isn't valid when v is a standard vector. > | > | From what I can tell from browsing the implementation, the > | requirement should be: > | > | boost::begin(v) The problem is that the Range concept requirements, as you specified them, are not satisfied by standard containers. Therefore the standard containers are not Ranges. Since it is a goal of the library that the standard containers be Ranges, you need to fix the way you've specified the concept requirements. And as I said later in the post: > One should be able to look at a concept definition and understand > which types will model that concept. That concept > definition may of course lead you to look at the implementation of > other functions, but it has to let you get ahold of one end of the > string, so you can follow it to its logical conclusion. That's why > the concept definition should say that boost::begin(s) is a > requirement... and of course it should link(**) to the documentation for > boost::begin so the reader can find out what it takes to make that > function work, and deduce that it works for standard containers. -------------- I also said: > | and the default behavior of boost::begin needs to be documented. > > it's documented in another document. I provided linke to in in the > CVS version some time ago after you requrested it. And then I asked that you post a link (both to the page with the boost::begin documentation and to the page in the main docs that links to it), but I have yet to see a reply. > 2. swappable range: > > The page says: "Since ranges are characterized by a specific underlying iterator > type, we get a type of range for each type of iterator." > > that's the definition. Sorry, but that's not a definition of anything. > Is it so hard to grasp? It is easy to infer what you mean, if you're very familiar with the new iterator concepts. It's also very easy to misinterpret if you're not, because swappable iterator is a counterintuitive name. More importantly, as I suggested, there is no need to name these concepts (because you can just say "Requires: iterator<R>::type is a model of RandomAccessTraversalIterator," or whatever), especially not before they have been shown to be useful in specifying algorithms. There's no need to build a parallel and redundant concept hierachy. In fact, it's probably harmful to do so. > 3. Implementation of concepts. > > A type conforms to a concept, so ok, you can't implement it. Maybe a renaming > to "Implementations of types that concorm to Range concepts". ? I don't know what the right title is first try to answer the question I asked: You need to rename this page. What is it really describing? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 4. links from concepts to implementation. I'm not sure what you're referring to. > I remember I put some links when you asked for it. It should be > in the cvs code. In the code? I remember asking you to post some links. Or maybe you mean you fulfilled the request in (**) to put links in the documentation? Can you tell me where, on the boost-consulting CVS mirror, I can find that? > Do you want more links? I can't know until I can see what you've already done. > 5. containers and iterators. It should be explained in the introduction > that pairs and containers "just works". That is insufficient. The concept requirements have to be correct. And by the way, if you mean "This library therefore provides the means to adapt standard-like containers, null terminated strings, std::pairs of iterators, and raw arrays (and more), such that the same generic code can work with them all." then no, it doesn't make it clear that they "just work." It claims that the library gives me the *means* to make them "just work." So I'm left asking, "how do I do that?" Also, IIUC, this and other mentions of null terminated strings need to be removed now. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 9

[1.33.0 RC1] libs/type_traits/docs/html needs boostbook.css
by Larry Evans 05 Aug '05

05 Aug '05

The html tables created by the Jamfile.v2 and type_traits.qbk in parent directory have no delimiters between columns and rows without a boostbook.css in the html directory. A copy of the boostbook.css from: libs/python/doc/tutorial/doc/html seems to work.

2 5

Fw: shared_array EXC_BAD_ACCESS
by Peter Dimov 05 Aug '05

05 Aug '05

I'm forwarding the following post from boost-users http://lists.boost.org/boost-users/2005/08/12938.php since it describes a pretty severe configuration problem on Mac OS X that apparently leads to inconsistent definitions of BOOST_HAS_THREADS and all kinds of interesting ODR violations. Christopher Hunt wrote: > OK, this is now completely solved. :-) > > Interestingly, boost/detail/lightweight_mutex.hpp was being included > in one place and declaring lightweight_mutex from > boost/detail/lwm_nop.hpp. However the implementation from > boost/detail/lwm_pthreads.hpp was actually being used. > > To cut a long story short, declaring a prefix file that forced boost > to configure itself prior to importing Cocoa and Carbon dependencies > completely solved the problem. Here's what my Cocoa pch file looks > like: > > // > // Prefix header for all source files > // > > #ifdef __cplusplus > #include <boost/config.hpp> > // Gets brought in early so that any > Carbon presence doesn't influence > // its configuration. > #endif > > #ifdef __OBJC__ > #import <Cocoa/Cocoa.h> > #endif > > If you're doing just Carbon, then do your #include <Carbon/Carbon.h> > after boost/config.hpp is included (in place of the #ifdef __OBJC__ > block). > > The real gremlin here is this bit of code in > boost/config/platform/macos.hpp: > > # ifndef TARGET_CARBON > # include <boost/config/posix_features.hpp> > # endif > > There is a posting that discusses the rationale of the above: > http://lists.boost.org/boost-users/2004/10/8110.php and also makes the > observation that there's probably a better way to check for MSL. > > My recommendation is to check for the definition of __MSL__. Thus the > above code becomes: > > # ifndef __MSL__ > # include <boost/config/posix_features.hpp> > # endif > > IMHO the existing MSL check is a bug (checking TARGET_CARBON is too > broad) and will be a trap for all Cocoa/Carbon programmers wanting to > use boost. I would also think that the reality now is that most people > use xcode/gcc and not CodeWarrior/MSL (this is from someone who used > to use CW and MSL all the time). Thus, the motivation for addressing > the issue should now be high. > > What needs to be done to fix the problem? I'm willing to help to save > some other poor soul from spending a day or two stuffing around. > > Cheers, > -C

2 2

[Boost-bugs] [ boost-Support Requests-1252231 ] pointer refresh?? ?!?!??!?!?!
by SourceForge.net 04 Aug '05

04 Aug '05

Support Requests item #1252231, was opened at 2005-08-04 14:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1252231&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Peter Dimov (pdimov) Summary: pointer refresh?? ?!?!??!?!?! Initial Comment: i used boost-shared_ptr in a system tray app, and i think i'm loosing some data because of it. If the app stays minimized in sys tray for let's say an hour, things don't go very well. i'm not having any errors, but i ask u if that is possible ? it;s like they need some refresh or something..don't know what ... this is critical..help-help.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1252231&group_… ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[1.33.0] Release candidate #1 is available
by Doug Gregor 04 Aug '05

04 Aug '05

Boost 1.33.0 release candidate #1 is now available here: http://www.osl.iu.edu/~dgregor/boost-1.33.0/ There are two sets of files important for this release: - boost_1_33_0_rc1.*: The actual release candidate - boost_1_33_0_(docbook|fo|man).*: The documentation in other formats Please download and unpack the archives, browse the documentation, try the release with your favorite compiler, etc. Thanks! Doug Gregor 1.33.0 Release Manager

12 18

[network] Boost.Network proposal v0.3
by Pedro Lamarão 04 Aug '05

04 Aug '05

Fellow Boosters, this is an update on my proposal for (the beggining of?) a Boost.Network library, located in the Sandbox. I consider it feature complete for a 1.0 milestone; the features being: *) IOStreams classes, fully buffered *) A listener class *) A wrapper for the name resolution service *) A type to store addresses The missing pieces being: *) Complete the copy constructores and assignment operators of the generic_address class. *) Implement optimized xsputn() and xsgetn() in the stream buffer. *) Implement setbuf() in the stream buffer. *) Documentation (never enough) The above list is what I intend to polish up for a formal proposal. This is the TODO list for a next version: *) Address types specific for IPv4 and IPv6, with input operators. *) A formatter output operator for generic address types based on the name resolution service. *) Resolver options and manipulators for the above output operator. *) Code conversion in the stream buffer. *) A poller class. *) Wrapper for sendfile/TransmitFile. *) Implement showmanyc() and perhaps putbackfail() in the stream buffer. With a proper poller class I believe most people's desires for non-blocking operation would be satisfied. I'm going out of town on vacations for some days, so things are going to stall for a while. I hope to complete all tasks soon after Boost 1.33 is released and a new review cycle starts. -- Pedro Lamarão

6 8

[1.33.0 RC1] Possible regression in serialization
by Eelis van der Weegen 04 Aug '05

04 Aug '05

Here's another one-liner that fails to compile (with gcc 3.3.5): #include <boost/serialization/nvp.hpp> I get the following error: In file included from .../boost_1_33_0/boost/serialization/nvp.hpp:33, from t.cpp:1: .../boost_1_33_0/boost/serialization/tracking.hpp:50: error: syntax error before `>' token Again, this worked with Boost 1.32 :) Regards, Eelis

3 2

Boost regression notification (2005-08-04)
by Douglas Gregor 04 Aug '05

04 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-04T14:58:10Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 1 failure in 1 library: thread (1) |thread| test_thread: borland-5_6_4

1 0

Minor documentation issues
by Ariel Badichi 04 Aug '05

04 Aug '05

Hi, The issues are present in release candidate #1. * The full library names in the main page are inconsistent; sometimes "library" is appended to the library name, and sometimes not. Some of these should probably have capital-cased "library" appended - like most of the other libraries. (There seem to be a few exceptions, e.g., Wave and functional/hash, which aren't (just) libraries.) * The "conversion" library entry in the "Libraries Listed Alphabetically" section in libs/libraries.htm is missing a few characters. * Some header filenames in libs/ptr_container/doc/headers.html are incorrect - they miss the .hpp extension.

4 5

Re: [boost] weak_ptr, maybe empty -- doc bug?
by Andy Thomas-Cramer 04 Aug '05

04 Aug '05

Is this a documentation bug? template<class Y> explicit shared_ptr(weak_ptr<Y> const & r); Effects: If r is empty, constructs an empty shared_ptr ... It seems to be throwing an exception, rather than returning an empty shared_ptr. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Joe Gottman > Sent: Wednesday, August 03, 2005 7:16 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] weak_ptr, maybe empty > > > "Andy Thomas-Cramer" <Andy_Thomas-Cramer(a)avid.com> wrote in message > news:2F6133743473D04B8685415F8243F4765347D5@madison- > msg1.global.avidww.com... > > > > I have a weak_ptr that might be empty. If not empty, I'd like to make a > > smart pointer from it. > > > > But the code below throws in the shared_ptr constructor, and I don't see > > how to test whether a weak_ptr is empty. > > > > boost::weak_ptr<int> wp; > > boost::shared_ptr<int> sp(wp); > > if ( sp.get() ) { > > ... > > } > > > > Suggestions? > > > > It depends what you mean by empty. A weak_ptr can either > a) be associated with a valid shared_ptr > b) be associated with a shared_ptr that has since expired > or c) be default initialized and never associated with a shared_ptr > > If you don't need to differentiate between case b) and c), the most > elegant > way is > if (shared_ptr<int> sp = wp.lock()) { > //do work with valid shared_ptr > } > > If you need to distinguish between b) and c) you can continue with > } else { > weak_ptr empty; > if (!(wp < empty) && !(empty < wp)) { > //case c, default-constructed weak_ptr > } else { > //case b, expired weak_ptr > } > } > > In practice, most people don't need to distinguish between case b) and c) > > Joe Gottman > > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Need help commiting a fix in the CVS Re: [1.33.0 RC1] Possible regression in multi_index
by JOAQUIN LOPEZ MU?Z 04 Aug '05

04 Aug '05

----- Mensaje original ----- De: Eelis van der Weegen <gmane(a)contacts.eelis.net> Fecha: Jueves, Agosto 4, 2005 9:00 am Asunto: [boost] [1.33.0 RC1] Possible regression in multi_index > I'm having trouble compiling a source file consisting of the > following single line: > > #include <boost/multi_index/ordered_index.hpp> > > Using gcc 3.3.5, I get the following error: [...] > error: no > class template named `archive_exception' in `boost::archive' > Hi Eelis, thank you very much for the report. This is indeed a bug in ordered_index.hpp, I forgot to add an include defining archive_exceptions. As it happens, I've got a local test that checks that every header in Boost.MultiIndex correctly compiles when included in isolation, but the compiler I'm using does not implement 2-phase lookup and didn't catch this one... Are fixes still allowed to go to RC2? If so, I'd appreciate if someone could check the attached boost/multi_index/ordered_index.hpp replacement. It merely adds an additional include to solve Eelis' report, and I've locally checked it doesn't break anything. I cannot commit it myself, since I don't have CVS write access these days. I'm also sorry I can't send the fix as a diff file, but I don't have any diffing tool here --the change boils down to a new line at position 65. Thank you for your help, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[1.33.0] 31 remaining broken links
by Jonathan Turkanis 04 Aug '05

04 Aug '05

Hi, There are still a few broken links. The affected areas of Boost are: - who's using boost (FEAR) - numeric/interval - numeric/ublas - serialization - spirit - test - people/darin adler - build v1 Jonathan begin 666 NewReport.txt M1DE,13H@(" @($,Z7$1O8W5M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-< M2&]M95QB;V]S=%\Q7S,S7S!<9&]C7&AT;6Q<=VAO7W-?=7-I;F=?8F]O<W1? M7&]P96XN:'1M; T*#0H@("!A(&AR968]:'1T<#HO+V9E87(N<V]U<F-E9F]R M9V4N;F5T+R ]/3T^(%1H92!S97)V97(@<F5S<&]N<V4@8V]U;&0@;F]T(&)E M('!A<G-E9"X-"@T*1DE,13H@(" @($,Z7$1O8W5M96YT<R!A;F0@4V5T=&EN M9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q7S,S7S!<;&EB<UQN=6UE<FEC7&EN M=&5R=F%L7&1O8UQI;G1E<G9A;"YH=&T-"@T*(" @82!H<F5F/2-I;G1E<G9A M;%]P;VQI8VEE<R ]/3T^(&9I;&4@9F]U;F0L(&)U="!I;G1E<FYA;"!L:6YK M(&ES(&%B<V5N= T*(" @82!H<F5F/2-C:&5C:VEN9R ]/3T^(&9I;&4@9F]U M;F0L(&)U="!I;G1E<FYA;"!L:6YK(&ES(&%B<V5N= T*(" @82!H<F5F/6AT M=' Z+R]W=W<N<FAE:6XM;6%I;BYD92]P96]P;&4O:FUA=7)E<B]I;G1E<G9A M;"YT87(N9WH@/3T]/B!%<G)O<CH@<F5S;W5R8V4@;F]T(&9O=6YD#0H-"D9) M3$4Z(" @("!#.EQ$;V-U;65N=',@86YD(%-E='1I;F=S7'1U<FMA;FES7$AO M;65<8F]O<W1?,5\S,U\P7&QI8G-<;G5M97)I8UQU8FQA<UQD;V-<8FQA<RYH M=&T-"@T*(" @82!H<F5F/2-?=&]D;S P,# P,R ]/3T^(&9I;&4@9F]U;F0L M(&)U="!I;G1E<FYA;"!L:6YK(&ES(&%B<V5N= T*(" @82!H<F5F/2-G83@@ M/3T]/B!F:6QE(&9O=6YD+"!B=70@:6YT97)N86P@;&EN:R!I<R!A8G-E;G0- M"B @(&$@:')E9CTC7W1O9&\P,# P,#0@/3T]/B!F:6QE(&9O=6YD+"!B=70@ M:6YT97)N86P@;&EN:R!I<R!A8G-E;G0-"B @(&$@:')E9CTC9V$X(#T]/3X@ M9FEL92!F;W5N9"P@8G5T(&EN=&5R;F%L(&QI;FL@:7,@86)S96YT#0H@("!A M(&AR968](U]T;V1O,# P,# U(#T]/3X@9FEL92!F;W5N9"P@8G5T(&EN=&5R M;F%L(&QI;FL@:7,@86)S96YT#0H@("!A(&AR968](V=A." ]/3T^(&9I;&4@ M9F]U;F0L(&)U="!I;G1E<FYA;"!L:6YK(&ES(&%B<V5N= T*(" @82!H<F5F M/2-?=&]D;S P,# P-B ]/3T^(&9I;&4@9F]U;F0L(&)U="!I;G1E<FYA;"!L M:6YK(&ES(&%B<V5N= T*(" @82!H<F5F/2-G83@@/3T]/B!F:6QE(&9O=6YD M+"!B=70@:6YT97)N86P@;&EN:R!I<R!A8G-E;G0-"@T*1DE,13H@(" @($,Z M7$1O8W5M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q M7S,S7S!<;&EB<UQS97)I86QI>F%T:6]N7&1O8UQA<F-H:79E<RYH=&UL#0H- M"B @(&$@:')E9CUS<&5C:6%L+FAT;6PC9&5R:79E9'!O:6YT97)S(#T]/3X@ M9FEL92!F;W5N9"P@8G5T(&EN=&5R;F%L(&QI;FL@:7,@86)S96YT#0H@("!A M(&AR968]<W!E8VEA;"YH=&UL(V1E<FEV961P;VEN=&5R<R ]/3T^(&9I;&4@ M9F]U;F0L(&)U="!I;G1E<FYA;"!L:6YK(&ES(&%B<V5N= T*#0I&24Q%.B @ M(" @0SI<1&]C=6UE;G1S(&%N9"!3971T:6YG<UQT=7)K86YI<UQ(;VUE7&)O M;W-T7S%?,S-?,%QL:6)S7'-E<FEA;&EZ871I;VY<9&]C7'1R86ET<RYH=&UL M#0H-"B @(&$@:')E9CUS<&5C:6%L+FAT;6PC9&5R:79E9'!O:6YT97)S(#T] M/3X@9FEL92!F;W5N9"P@8G5T(&EN=&5R;F%L(&QI;FL@:7,@86)S96YT#0H- M"D9)3$4Z(" @("!#.EQ$;V-U;65N=',@86YD(%-E='1I;F=S7'1U<FMA;FES M7$AO;65<8F]O<W1?,5\S,U\P7&QI8G-<<W!I<FET7&1O8UQP<F5F86-E+FAT M;6P-"@T*(" @82!H<F5F/6AT=' Z+R]W=W<N9V5O8W)A=VQE<BYC;VTO;&ES M=',O,R]3;W5R8V5&;W)G92\Q,C@S-R\P+R ]/3T^($5R<F]R.B!R97-O=7)C M92!N;W0@9F]U;F0@*%)%1$E214-4140@5$\Z(&AT=' Z+R]S;W5R8V5F;W)G M92YN970O;&ES=',O,R]3;W5R8V5&;W)G92\Q,C@S-R\P+R I#0H-"D9)3$4Z M(" @("!#.EQ$;V-U;65N=',@86YD(%-E='1I;F=S7'1U<FMA;FES7$AO;65< M8F]O<W1?,5\S,U\P7&QI8G-<<W!I<FET7'!H;V5N:7A<9&]C7'!R969A8V4N M:'1M; T*#0H@("!A(&AR968]:'1T<#HO+VYE=W,N9VUA;F4N;W)G+W1H<F5A M9"YP:' _9W)O=7 ]9VUA;F4N8V]M<"YS<&ER:70N9V5N97)A;" ]/3T^(%1H M92!A='1E;7!T('1O(&-O;FYE8W0@=&\@=&AE('-E<G9E<B!F86EL960N#0H@ M("!A(&AR968]:'1T<#HO+W=W=RYG96]C<F%W;&5R+F-O;2]L:7-T<R\S+U-O M=7)C949O<F=E+S$R.#,W+S O(#T]/3X@17)R;W(Z(')E<V]U<F-E(&YO="!F M;W5N9" H4D5$25)%0U1%1"!43SH@:'1T<#HO+W-O=7)C969O<F=E+FYE="]L M:7-T<R\S+U-O=7)C949O<F=E+S$R.#,W+S O("D-"@T*1DE,13H@(" @($,Z M7$1O8W5M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q M7S,S7S!<;&EB<UQT97-T7&1O8UQP;W)T86)I;&ET>2YH=&UL#0H-"B @($$@ M:')E9CUH='1P.B\O8F]O<W0N<V]U<F-E9F]R9V4N;F5T+W)E9W)E<W-I;VXM M;&]G<R]D979E;&]P97(O=&5S="YH=&UL(#T]/3X@17)R;W(Z(')E<V]U<F-E M(&YO="!F;W5N9 T*#0I&24Q%.B @(" @0SI<1&]C=6UE;G1S(&%N9"!3971T M:6YG<UQT=7)K86YI<UQ(;VUE7&)O;W-T7S%?,S-?,%QL:6)S7'1E<W1<9&]C M7&-O;7!O;F5N='-<=&5S=%]E>&5C7VUO;FET;W)<8V]M<&EL871I;VXN:'1M M; T*#0H@("!!(&AR968]+BXO+BXO+BXO<W)C+W5N:71?=&5S=%]R97-U;'0N M8W!P(#T]/3X@1FEL92!M:7-S:6YG#0H@("!!(&AR968]+BXO+BXO+BXO<W)C M+W-U<'!L:65D7VQO9U]F;W)M871T97)S+F-P<" ]/3T^($9I;&4@;6ES<VEN M9PT*#0I&24Q%.B @(" @0SI<1&]C=6UE;G1S(&%N9"!3971T:6YG<UQT=7)K M86YI<UQ(;VUE7&)O;W-T7S%?,S-?,%QL:6)S7'1E<W1<9&]C7&-O;7!O;F5N M='-<=71F7&-O;7!I;&%T:6]N+FAT;6P-"@T*(" @02!H<F5F/2XN+RXN+RXN M+W-R8R]U;FET7W1E<W1?<F5S=6QT+F-P<" ]/3T^($9I;&4@;6ES<VEN9PT* M(" @02!H<F5F/2XN+RXN+RXN+W-R8R]S=7!P;&EE9%]L;V=?9F]R;6%T=&5R M<RYC<' @/3T]/B!&:6QE(&UI<W-I;F<-"@T*1DE,13H@(" @($,Z7$1O8W5M M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q7S,S7S!< M;&EB<UQT97-T7&1O8UQC;VUP;VYE;G1S7'5T9EQC;VUP;VYE;G1S7'1E<W1? M8V%S95QB;V]S=%]F=6YC=&EO;E]T8RYH=&UL#0H-"B @($$@:')E9CTN+B\N M+B\N+B\N+B\N+B\N+B\N+B]B;V]S="]T97-T+W5N:71?=&5S=%]S=6ET95]E M>"YH<' @/3T]/B!&:6QE(&UI<W-I;F<-"@T*1DE,13H@(" @($,Z7$1O8W5M M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q7S,S7S!< M;&EB<UQT97-T7&1O8UQC;VUP;VYE;G1S7'5T9EQC;VUP;VYE;G1S7'1E<W1? M8V%S95QP87)A;5]B;V]S=%]F=6YC=&EO;E]T8RYH=&UL#0H-"B @($$@:')E M9CTN+B\N+B\N+B\N+B\N+B\N+B\N+B]B;V]S="]T97-T+W5N:71?=&5S=%]S M=6ET95]E>"YH<' @/3T]/B!&:6QE(&UI<W-I;F<-"@T*1DE,13H@(" @($,Z M7$1O8W5M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q M7S,S7S!<;&EB<UQT97-T7&1O8UQT97-T<UQU;FET7W1E<W1?<W5I=&5?97A? M=&5S="YH=&UL#0H-"B @($$@:')E9CTN+B\N+B]T97-T+W5N:71?=&5S=%]S M=6ET95]E>%]T97-T+F-P<" ]/3T^($9I;&4@;6ES<VEN9PT*#0I&24Q%.B @ M(" @0SI<1&]C=6UE;G1S(&%N9"!3971T:6YG<UQT=7)K86YI<UQ(;VUE7&)O M;W-T7S%?,S-?,%QP96]P;&5<9&%R:6Y?861L97(N:'1M#0H-"B @(&$@:')E M9CUH='1P.B\O=W=W+G-P:65S+F-O;2]^9W)E9R]B;'5E;65A;FEE<RYH=&UL M(#T]/3X@17)R;W(Z(')E<V]U<F-E(&YO="!F;W5N9 T*(" @82!H<F5F/6AT M=' Z+R]W=W<N9V5N97)A;&UA9VEC+F-O;2 ]/3T^($5R<F]R.C0P,PT*#0I& M24Q%.B @(" @0SI<1&]C=6UE;G1S(&%N9"!3971T:6YG<UQT=7)K86YI<UQ( M;VUE7&)O;W-T7S%?,S-?,%QT;V]L<UQB=6EL9%QV,5QB=6EL9%]S>7-T96TN M:'1M#0H-"B @(&$@:')E9CTC9W)I<W0@/3T]/B!F:6QE(&9O=6YD+"!B=70@ M:6YT97)N86P@;&EN:R!I<R!A8G-E;G0-"@T*1DE,13H@(" @($,Z7$1O8W5M M96YT<R!A;F0@4V5T=&EN9W-<='5R:V%N:7-<2&]M95QB;V]S=%\Q7S,S7S!< M=&]O;'-<8G5I;&1<=C%<9V-C+6YO8WEG=VEN+71O;VQS+FAT;6P-"@T*(" @ M82!H<F5F/6AT=' Z+R]W=W<N;F%N;W1E8V@N=VES8RYE9'4O?FMH86XO<V]F M='=A<F4O9VYU+7=I;C,R+VUN;RUC>6=W:6XM:&]W=&\N='AT(#T]/3X@17)R M;W(Z(')E<V]U<F-E(&YO="!F;W5N9 T*#0I&24Q%.B @(" @0SI<1&]C=6UE M;G1S(&%N9"!3971T:6YG<UQT=7)K86YI<UQ(;VUE7&)O;W-T7S%?,S-?,%QT M;V]L<UQB=6EL9%QV,5QS=6YP<F\M=&]O;',N:'1M; T*#0H@("!A(&AR968] M:'1T<#HO+V)O;W-T+G-O=7)C969O<F=E+FYE="]R96=R97-S:6]N+6QO9W,O M8W,M4W5N3U,N:'1M;" ]/3T^($5R<F]R.B!R97-O=7)C92!N;W0@9F]U;F0- #"@T* ` end

5 4

Review Request: xpressive
by Eric Niebler 04 Aug '05

04 Aug '05

As of version 0.9.5, posted yesterday, xpressive is close enough to v1.0 for me to feel comfortable putting it up for review. Could it please be added to the queue? BTW, GMane apparantly dropped the following msg, which I sent yesterday: << Background >> xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. << Significant changes since 0.9.3 >> - c_regex_traits to wrap the global C locale - null_regex_traits for searching non-char data - doc and test improvements - bugs in static regexes and Unicode support squashed << Download >> xpressive.zip at: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler << Docs >> http://boost-sandbox.sf.net/libs/xpressive Note: You can consider this the xpressive 1.0 release candidate. All that remains is to add more tests and documentation, and perhaps a tweak to the traits interface. -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

[1.33.0 RC1] Possible regression in multi_index
by Eelis van der Weegen 04 Aug '05

04 Aug '05

I'm having trouble compiling a source file consisting of the following single line: #include <boost/multi_index/ordered_index.hpp> Using gcc 3.3.5, I get the following error: In file included from t.cpp:1: .../boost_1_33_0/boost/multi_index/ordered_index.hpp: In member function `void boost::multi_index::detail::ordered_index<KeyFromValue, Compare, SuperMeta, TagList, Category>::rearranger(boost::multi_index::detail::ordered_index_node<typename SuperMeta::type::node_type>*, boost::multi_index::detail::ordered_index_node<typename SuperMeta::type::node_type>*)': .../boost_1_33_0/boost/multi_index/ordered_index.hpp:1092: error: no class template named `archive_exception' in `boost::archive' Needless to say this used to work with Boost 1.32 :) Regards, Eelis

1 0

[parameters] some typos in reference...
by Pavel Chikulaev 04 Aug '05

04 Aug '05

Hi Daniel, There are some strange symbols with modifier "" after in section 4.2 after second member function definition, again in the same section in "operator()" subsection after first operator() definition, then in section 6.1 after second function body. Is it a bug of rst, or what? Also <hr> with class="docutils footer" IMO looks bad here - it's just take about 80% of space, and IMO it's would look much better if it would take 100%... Even simple <hr/> IMO would be better here... -- Pavel Chikulaev

3 6

Fw: [network] Boost.Network proposal v0.3
by Scott Woods 04 Aug '05

04 Aug '05

Pardon. An error in that last message. ----- Original Message ----- From: "Scott Woods" <scottw(a)qbik.com> To: <boost(a)lists.boost.org> > The above paragrah is about the long term significance of non-blocking vs > blocking. I believe you are also facing the issue of library > (de-)composition; > if you ultimately want to provide both a blocking and non-blocking API it > is less difficult to imagine a non-blocking API over a blocking API than the > other way around. Should be; "if you ultimately want to provide both a blocking and non-blocking API it is less difficult to imagine a blocking API over a non-blocking API than the other way around."

1 0

weak_ptr, maybe empty
by Andy Thomas-Cramer 04 Aug '05

04 Aug '05

I have a weak_ptr that might be empty. If not empty, I'd like to make a smart pointer from it. But the code below throws in the shared_ptr constructor, and I don't see how to test whether a weak_ptr is empty. boost::weak_ptr<int> wp; boost::shared_ptr<int> sp(wp); if ( sp.get() ) { ... } Suggestions?

3 2

[parameter] missing link in main page and libraries.htm?
by Joaquín Mª López Muñoz 03 Aug '05

03 Aug '05

Can't find links to Boost.Parameter docs from the main page or libraries.htm. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 15

[Boost-bugs] [ boost-Bugs-1250901 ] polymorphic i/o archives and stl containers problem
by SourceForge.net 03 Aug '05

03 Aug '05

Bugs item #1250901, was opened at 2005-08-03 02:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250901&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: polymorphic i/o archives and stl containers problem Initial Comment: Hello, i downloaded 1.33.0 RC1 from http://www.osl.iu.edu/~dgregor/boost-1.33.0/ and tried to recompile some rather large projects with it (currently using 1.32.0). Using MS VC 7.1 and GCC 3.4.4 Doesnt work for boost::serialization: boost::archive::polymorphic_iarchive& ar boost::archive::polymorphic_oarchive& ar It bumps on STL containers now: boost\serialization\collections_load_imp.hpp(118) : error C2039: 'reset_object_address' : is not a member of 'boost::archive::polymorphic_iarchive' boost\archive\polymorphic_iarchive.hpp(52) : see declaration of 'boost::archive::polymorphic_iarchive' ---- snip "collections_load_imp.hpp" ---- // map input template<class Archive, class Container> struct archive_input_map { inline void operator()(Archive &ar, Container &s) { #if BOOST_WORKAROUND(BOOST_DINKUMWARE_STDLIB, == 1) typedef BOOST_DEDUCED_TYPENAME std::pair< BOOST_DEDUCED_TYPENAME Container::key_type, BOOST_DEDUCED_TYPENAME Container::referent_type > type; #else typedef BOOST_DEDUCED_TYPENAME std::pair< BOOST_DEDUCED_TYPENAME Container::key_type, BOOST_DEDUCED_TYPENAME Container::mapped_type > type; #endif stack_construct<Archive, type> t(ar); // borland fails silently w/o full namespace ar >> boost::serialization::make_nvp("item", t.reference()); std::pair<BOOST_DEDUCED_TYPENAME Container::const_iterator, bool> result = s.insert(t.reference()); assert(result.second); // make sure we inserted a new element ar.reset_object_address(& (* result.first), & t); } }; ---- snip "collections_load_imp.hpp" ---- "ar.reset_object_address(& (* result.first), & t);" is called but not implemeted for these "polymorphic" archive types? I only found it implemented in "basic_iarchive_impl" (and "basic_oarchive_impl" respective). What gives? It worked for 1.32 (because there was no "reset_object_address" there). Is there another (new) way to use polymorphic archive interfaces serializing stl containers? Regards, A. Focht ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250901&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

[1.33.0] Checklist for RC2
by Douglas Gregor 03 Aug '05

03 Aug '05

These are the issues we need to resolve before I can roll RC2, which is likely to become the final release: - Jonathan Turkanis needs a picture - Fix remaining broken links - iostreams: Document how to get bzip2/gzip iostreams to work in more/getting_started.html - regex: Decide what to do about std::equal bug in VC++ 8.0 beta (it *is* a beta, and it *is* a compiler bug) I expect that we can get all of these done for a release candidate tonight with a final release tomorrow. Doug

2 3

Re: [boost] Interest for a perl6-like-junctions-class?
by Jan Hermelink 03 Aug '05

03 Aug '05

FlSt(a)gmx.de wrote: > BTW: Today I tried to install the > Perl 6 interpreter Pugs, but I didn't get it to work. I wanted to > analyze the Perl 6 implementation of junctions especially the behaivor > of comparisons, because I don't want to tell something wrong here. If you have Windows, try PXPerl (http://pixigreg.com/) It contains a ready-to-run pugs.exe. none, one, all and any seems to work... Jan

1 0

Re: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X<Y >
by Brian Braatz 03 Aug '05

03 Aug '05

I had run into a problem once where I had a forward declare of a type, and then the type was declared below a template- the template was trying to get to a type in the forward declared class, when I derived from the class, I was able to get it to compile. this was months ago and my memory could be wrong (I was also very tired when I wrote that). ----Original Message----- From: boost-bounces(a)lists.boost.org on behalf of Andreas Huber Sent: Tue 8/2/2005 11:36 AM To: boost(a)lists.boost.org Subject: Re: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X<Y > --- Brian Braatz <brianb(a)rmtg.com> wrote: > Suggestion: > > is there some way in your design you can get away with deriving > from the > incomplete type to "de-incomplete" it? I don't understand. You can't inherit from an incomplete type. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] weak_ptr, maybe empty
by Andy Thomas-Cramer 03 Aug '05

03 Aug '05

Thanks, that did it. It's not intuitive, and not obvious from the documentation. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Michael B. Edwin Rickert > Sent: Wednesday, August 03, 2005 3:14 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] weak_ptr, maybe empty > > Andy Thomas-Cramer wrote: > > I have a weak_ptr that might be empty. If not empty, I'd like to make a > > smart pointer from it. > > > > But the code below throws in the shared_ptr constructor, and I don't see > > how to test whether a weak_ptr is empty. > > > > boost::weak_ptr<int> wp; > > boost::shared_ptr<int> sp(wp); > > if ( sp.get() ) { > > ... > > } > > The documentation (http://boost.org/libs/smart_ptr/weak_ptr.htm) seems > to show a few options. The most similar to your situation would be: > > boost::weak_ptr< int > wp; > boost::shared_ptr< int > sp = wp.lock(); > if ( sp.get() ) { > ... > } > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[1.33.0] 300 broken links [repost]
by Jonathan Turkanis 03 Aug '05

03 Aug '05

Hi, I ran a shareware HTML link checker on release candidate 1, and found 334 broken links; I'm attaching the report. A few of them appear bogus ("Error: invalid syntax"), and some appear to reflect the temporary unavailability of news.gmane.org, but most appear legitimate. I'll volunteer to fix as many of them as I can, if it's not too late to make it into the release. Some I can't fix, because I don't know where they're supposed to point. Here are the affected areas of Boost: Libraries: - compatibility - conversion - crc - date_time - disjoint_sets - filesystem - format - function - graph - hash - iterator - math - minmax - multi_index - numeric/conversion - numeric/interval - numeric/ublas - parameter - preprocessor - property_map - ptr_container - python - random - range - rational - regex - serialization - smart_ptr - spirit - test - threads - timer - tuple - type_traits - utility - variant - wave Tools: - build (v1 + v2) - boostbook Misc: - index.htm - doc/html/index.html - doc/html/who_s_using_boost_.html - doc/html/who_s_using_boost_/open.html - more/discussion_policy.htm - more/mailing_lists.htm - more/test_policy.htm - more/background.html - more/bibliography.html - more/cpp_committee_meetings.html - more/error_handling.html - more/formal_review_schedule.html - more/generic_exception_safety.html - more/generic_programming.html - more/getting_started.html - more/regression.html - more/version_history.html - more/writingdoc/template/definitions.html - people/darin_adler.htm - people/dietmar_kuehl.htm - people/jonathan_turkanis.htm - people/mark_rodgers.htm - people/people.htm - people/ralf_w_grosse_kunstleve.htm - people/vesa_karvonen.htm Jonathan

6 15

Boost regression notification (2005-08-03)
by Douglas Gregor 03 Aug '05

03 Aug '05

<html> <head> <meta http-equiv="refresh" content="1; url=issues-email.txt"> </head> <body> Update in progress (building archive index, done in approximately 4 seconds), please wait... </body> </html>

2 1

[mpl] as_sequence< X< Y > > instantiates typedefs in X< Y >
by Andreas Huber 03 Aug '05

03 Aug '05

Hi there I'm trying to address a point raised by Jonathan Turkanis during the formal review of the statechart library. Basically, the problem boils down to the following: #include <boost/mpl/list.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/as_sequence.hpp> namespace mpl = boost::mpl; // InnerInitial is either an mpl sequence of types or a single type template< class InnerInitial > struct state { // stateArray_ must have a length equal to the number of types // in InnerInitial int stateArray_[ mpl::size< typename mpl::as_sequence< InnerInitial >::type >::type::value ]; }; // A is defined later, possibly in a different translation unit struct A; template< class X > struct B { typedef typename X::reactions reactions; }; int main() { // fine: instantiation with an incomplete type state< A > a; // fine: instantiation with an mpl sequence containing B< A > state< mpl::list< B< A > > > b; // error: mpl::as_sequence triggers the instantiation of B's member // typedef, which tries to access the member typedef of A. A compile- // time error results because A is still incomplete at this point. state< B< A > > c; // *** here *** return 0; } MSVC7.1 and GCC3.4 agree that the last state template instantiation is illegal (use of undefined type A). I'm wondering whether there is any way to make this legal (different as_sequence implementation, implement the state template differently, etc.)? Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

2 14

[iostreams-1.33.0-RC1] documentation error?
by Russell Hind 03 Aug '05

03 Aug '05

2.1.1 states "Here io::stream<my_device> is a derived class of std::basic_streambuf, and io::stream<my_device> is a derived class of std::basic_istream, std::basic_ostream or std::basic_iostream depending on the mode of my_device, i.e., depending on which of the fundamental i/o operations read, write and seek it supports." Shouldn't the first part be "Here io::stream_buffer<my_device>"? Cheers Russell

2 1

Re: [boost] [1.33.0] Checklist for RC2
by JOAQUIN LOPEZ MU?Z 03 Aug '05

03 Aug '05

----- Mensaje original ----- De: Douglas Gregor <doug.gregor(a)gmail.com> Fecha: Miércoles, Agosto 3, 2005 4:05 pm Asunto: [boost] [1.33.0] Checklist for RC2 > These are the issues we need to resolve before I can roll RC2, > which is > likely to become the final release: > > - Jonathan Turkanis needs a picture > - Fix remaining broken links > - iostreams: Document how to get bzip2/gzip iostreams to work > in > more/getting_started.html > - regex: Decide what to do about std::equal bug in VC++ 8.0 > beta (it > *is* a beta, and it *is* a compiler bug) > Hi, I posted about the following several times, but the message went unnoticed. Maybe it is a misunderstanding from my part, but the "getting started" page lists Boost.Serialization as not autolinkable and not dyanmically linkable. I think this is no longer true in Boost 1.33 (but I might be wrong.) I would have taken care of the problem myself, but currently I can't access the CVS, as I'm on vacation. I'd be greateful if someone can correct this bit. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

Re: [boost] [1.33.0] User reports go live / feedback request
by Matt Doyle 03 Aug '05

03 Aug '05

> The draft version of user-centric regression reports is now > available at > http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_ > 0/user/summary_release.html > (http://tinyurl.com/bamym) If you'd like to comment on > usability/presentation of these before they go public with the > release, now it's time :). I liked the idea of having hyper-links to the details but I think the older 1.32 version was more readable. The first thing I did when I looked at it was print it out for reference. Without color the table is of no use. If you put text in each cell as before (OK, FAIL, ect...), in addition to the color, then it can be used in B/W or color. Scanned by Fortigate {X3BTB534}

3 3

mailing list delays
by David Abrahams 03 Aug '05

03 Aug '05

The problem should be fixed now. Let's hear it for the OSL guys! From: Rob Henderson <robh(a)cs.indiana.edu> Date: July 26, 2005 8:50:35 AM MDT To: Jeff Squyres <jsquyres(a)osl.iu.edu> Cc: OSL Sysadmin <osl-sysadmin(a)osl.iu.edu>, Bruce Shei <shei(a)cs.indiana.edu> Subject: Re: boost mailing lists I wanted to let you know that I think I've figured out what is going on with the recent slowness with email to the mailman lists that was reported. The email address xxx@xxxx that is on the boost list appears to have some kind of anti-spam tarpit set up that is catching milliways. Email to this address is handled by mail.tapeinternational.no and it you telnet to port 25 on this host from milliways you will see that it is (I assume) deliberately slow. During the initial '220' response, it is sending characters at a rate of about one character per 30 seconds. This keeps the connection from milliways moving along at a rate sufficient to keep it from timing out but slow enough that delivery is taking hours. If you telnet to port 25 from any other CS/OSL host the response is very fast so it is clearly set up to catch milliways. I don't know why they have done this, but I'd say the options are to either remove that user from the list or contact them and try to get them to stop this. Please let me know if there is anything else I can do related to this issue. We have disabled delivery to the offending email address and notified its owner. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3

[1.33.0][iostreams][serialization]
by Jeff Flinn 03 Aug '05

03 Aug '05

I've spent the last several hours trying to update my project with 1.33.0.RC. The only changes were naming issues with iostreams, and the getting rid of the lovely :) asserts on serialization inclusions previous to archive inclusions. Also an issue with operator << and const_cast-ing appears below, and switching to the standard BOOST_SHARED_POINTER_EXPORT_GUID macro which now appears to handle pointers in namespaces properly. All compiles and links succesfully under VC7.1. Rudimentary xml serialization seems to save/load succesfully. I am having an problems when using iostreams/serialization together to support copy/paste/drag/drop under Windows MFC. Which all worked flawlessly using 1.32.0 along with pre-release iostreams. I'd appreciate it if anyone sees anything blatantly wrong with the code below. CSharedFileSink::write is not being called at all. This leads and assert in MFC's CSharedFile::Detach because the file has never been written to. The member CSafeDataSource::GlobalArchiveHdl instantiates a CSharedFileOStream and attempts to serialize it's mVal data member to a binary archive. Thanks in advance, Jeff namespace adi { namespace mfc { namespace clipboard { struct CSharedFileSink : public boost::iostreams::sink { CSharedFile& mSharedFile; CSharedFileSink( CSharedFile& aSharedFile ) : boost::iostreams::sink() , mSharedFile(aSharedFile) {} std::streamsize write( const char* s, std::streamsize n ) { mSharedFile.Write( s, n ); return n; } }; class CSharedFileOStream : private boost::base_from_member<CSharedFile> , public boost::iostreams::stream<CSharedFileSink> { typedef boost:: base_from_member<CSharedFile > tSharedFile; typedef boost::iostreams::stream<CSharedFileSink> tBase; public: CSharedFileOStream() : tSharedFile( GMEM_MOVEABLE|GMEM_DDESHARE|GMEM_ZEROINIT ) , tBase( CSharedFileSink( tSharedFile::member ) ) {} HGLOBAL Detach(){ return tSharedFile::member.Detach(); } }; template< class T > class CSafeDataSource : public COleDataSource { typedef T value_type; value_type mVal; HGLOBAL GlobalArchiveHdl() { CSharedFileOStream lOut; boost::archive::binary_oarchive oa( lOut ); // oa & mVal; // same result as below oa << const_cast<const value_type&>(mVal); //BOOST_1_33_0 return lOut.Detach(); } CSafeDataSource( const T& aVal ) : COleDataSource(),mVal(aVal){ DelayRenderData( NativeFormat() ); } friend void ToClipBoard<T>( const T& aVal ); friend void Drag<T>( const T& aVal , tDragImagePtr aDragImagePtr , DWORD aDropEffect ); public: static CLIPFORMAT NativeFormat(){ return RegisteredClipboardFormat<value_type>(); } virtual BOOL OnRenderGlobalData( LPFORMATETC lpFormatEtc, HGLOBAL* phGlobal ) { if( lpFormatEtc->cfFormat == NativeFormat() ) { return (*phGlobal = GlobalArchiveHdl())? TRUE : FALSE; } return FALSE; } }; } } }

2 6

Boost Build V2 docs removed from cvs?
by John Maddock 03 Aug '05

03 Aug '05

All the links to the docs bbv2 docs from tools/build/v2/index.html seem to go nowhere. Has someone removed the docs from cvs? Thanks, John.

1 0

[1.33.0] Final release schedule
by Douglas Gregor 03 Aug '05

03 Aug '05

The release is starting to shape up, and here is our final release schedule. We'll stick to it unless something goes horribly wrong. Code freeze - 11pm EST on Sunday, July 24 Total freeze (including documentation) - 11pm EST on Wednesday, July 27 Final release - Monday, August 1st Doug Gregor 1.33.0 Release Manager

12 30

[date_time] and BCB
by Richard Jennings 03 Aug '05

03 Aug '05

The CVS head revision of date_time fails to compile with Borland C++ 5.6.4. This is because the run time libraries lack the re-entrant functions such as localtime_r. I added Borland to the list of compilers that do not support this in date_time/compiler_config.hpp and then the library compiles fine. Richard

3 5

iterators::function_output_iterator is missing in boost_1_32_0
by Oleg Abrosimov 03 Aug '05

03 Aug '05

Hello boosters! I've just found that function_output_iterator, mentioned in boost_1_32_0/libs/iterator/doc/function_output_iterator.html is missing in the boost or boost/iterator directories both in my own copy and in sf.net CVS. Neither me nor my compiler could found it. Was it deprecated? or removed accidentally? Best, Oleg Abrosimov

2 2

singleton design plan
by Jason Hise 03 Aug '05

03 Aug '05

This message is an in depth description of my current design plan for a new singleton library, which I hope to complete and schedule for review by boost in the coming year. I would appreciate any comments, questions, or suggestions regarding this plan before I begin work on the code. Specifically, I would like to know if there are any important issues that this design fails to address, or difficulties with the interface that would turn away potential users. (My old singleton library, which was not accepted by boost, is available at http://tinyurl.com/6qvrd. It was rejected primarily because it failed to adequately address concerns related to multi threading and dlls.) Thus far, my high level design plan looks like this: The creator_policy defines fundamental pointer, const_pointer, and reference types. These hold references to a creator policy instance which maintains the singleton internally, so that the pointer types can always see and access the state of the single instance. This way, pointers to the singleton instance are not invalidated when the state of the singleton changes. The creator_policy defines create, replace, and destroy methods, as well as methods to generate instances of the various pointer types. Create only creates the instance if it does not already exist, destroy only destroys the instance if it does exist, and replace makes sure any existing instance is destroyed before attempting creation. Thus far, I hope to support the following creators: -------------------------------------------------------------------------------- in_place_creator creates/destroys inside an aligned_storage POD interface: create ( [ctor params] ); replace ( [ctor params] ); destroy ( ); pros: no memory allocation/deallocation ever required constructor params can be easily specified cons: automatic creation, when it occurs, always uses the default constructor singleton cannot be created as a derived type useful for simple, user defined singleton classes -------------------------------------------------------------------------------- source_sink_creator owns fixed source and sink functors, specified with template parameters interface: create ( ); replace ( ); destroy ( ); pros: source can return a derived type automatic creation uses source rather than default construction cons: source and sink cannot be set or changed at runtime constructor arguments cannot be specified by calling code useful for singleton types provided by untouchable code, which may require calling special functions to get pointers to instances -------------------------------------------------------------------------------- dynamic_source_sink_creator owns dynamic source and sink functors interface: create ( [source[, sink]] ); replace ( [source[, sink]] ); destroy ( [source[, sink]] ); pros: source can return a derived type automatic creation uses source rather than default construction source and sink can optionally be changed at run time source and sink can change functor types when they are set (example: from function pointer to lambda expression) cons: specifying constructor parameters to pass is non-trivial dynamic memory allocation and virtual functions must be used to store the functors in order to allow for different functor types at runtime, thus creation is more expensive and can potentially fail useful for a singleton which needs to take the forms of unspecified derived types and is frequently destroyed and created via some type of factory -------------------------------------------------------------------------------- The lifetime_policy owns and wraps the creator policy, and provides pointer and reference types which wrap those belonging to the creator. It also provides functions to generate instances of the various pointer types, and provides a function to access the creator_policy instance. The unmanaged lifetime simply typedefs the underlying pointer and reference types, and thus results in no overhead. The longevity_lifetime and lifo_lifetime behave similarly, but handle scheduling of automated destruction when any of the pointer generation methods are called. The dependency_lifetime will wrap the internal pointer types to perform reference counting (the reference count itself will be stored in the lifetime_policy instance). The timeout_lifetime will manage a separate thread that releases the instance when it finishes counting down. It will also wrap the internal pointer types to reset the timer when a pointer is dereferenced, and reset and lock the timer while any references exist. The threading_policy owns and serializes access to the lifetime_policy. It also has a function to get access to the lifetime_policy instance, and provides pointer, const_pointer, and reference types which wrap and forward to the lifetime's corresponding types. For the single_threaded policy, these pointer types are simply typedefs of the lifetime's pointer types, resulting in no overhead, and the function through which the lifetime_policy instance is accessed just returns a raw pointer to it. For the multi_threaded policy, pointer types perform locking before forwarding to lifetime pointer types, and the reference type acts as a lock throughout it's existence. The mutex is stored inside the threading_policy instance. The function which returns a pointer to the lifetime_policy instance returns a smart pointer which serializes access. A storage_policy determines how instances of the threading_policy are stored (and because these instances contain instances of the other policies, this indirectly controls how all of the policy instances are stored). static_storage stores policy instances directly as global variables, which is fine for singletons that are not required to have a specific lifetime with regard to other singletons. These global variables will be set up in such a way that it will be guaranteed that any automatic destruction takes place before the policy bundle is destroyed. group_storage allows multiple singletons to have their policies stored in a master group. No policies in this group are destroyed until all automated destruction that will be performed by any members of the group has completed. This way, if destructors of some of the singletons in this group trigger re-creation of other singletons in the same group, the policies needed to recreate the singletons are guaranteed to still exist. dll_storage requires linking with singleton.dll, and stores instances in a special exported manager singleton to ensure unique singleton instances across dll boundaries. All policy instances of this type are guaranteed to be destroyed only after all automated destruction has taken place. A singleton class exists, which takes a singleton type and a name tag as template parameters. The name will have a default type called 'unnamed'. This name parameter enables using multiple singleton instances of the same type. Policies are traits of the name specified, so using the default name 'unnamed' results in using the default policies. Policies can be specified by declaring a name as an undefined struct, and then specializing the desired policy traits for that name. The singleton class contains three pointer types, which wrap those of the threading policy. These are strong_pointer, lazy_pointer, and weak_pointer. strong_pointer attempts automatic creation of the singleton instance if it does not exist when the pointer is first created, and also attempts automatic creation if needed any time it is dereferenced. lazy_pointer only attempts automatic creation when dereferenced, and weak_pointer will never create the instance automatically. For the lifo_lifetime, a strong_pointer can be used to specify a dependency of some singleton B on some singleton A by having B own a strong_pointer to A. This will ensure that A is created before B and destroyed after B. Const versions of these three pointer types will also exist. Creation, destruction, and non-const member functions will not be allowed to be called through these const pointer types. A single reference type will exist which will be the result of dereferencing any pointer type via the unary * operator. const_pointers return const qualified references. Pointers only perform temporary locking (if the threading policy supports locking) when a member function is called via the -> operator or when a create or destroy operation is invoked. References lock the singleton throughout their entire lifetime, and thus can be used to make a series of operations on the singleton instance atomic. A reference provides an implicit conversion to a raw reference of the singleton's type (which comes back const if the reference is const). Create and destroy can only be called on non-const references. Typical code will access a singleton instance by creating one of the above pointer types and calling member functions through it via the -> operator. Ex: singleton < MyType, SomeName >::lazy_pointer ptr; ptr->DoSomething ( ); -------------------------------------------------------------------------------- I plan to sneak an improved version of the null developed by Scott Meyers in with this code in a header called boost/null.hpp, and use it in the singleton's implementation. It will be defined as follows: namespace boost { const class { private: void operator & ( ) const; public: #ifndef BOOST_NO_MEMBER_TEMPLATES // provide conversion to any pointer type template < typename Class, typename Type > operator Type Class::* ( ) const { return 0; } template < typename Type > operator Type * ( ) const { return 0; } #else //provide conversion to int if member templates are not supported operator int ( ) const { return 0; } #endif//BOOST_NO_MEMBER_TEMPLATES } null; } #undef NULL #define NULL (::boost::null) -------------------------------------------------------------------------------- Any and all comments or suggestions on this plan are welcomed. Potential problems are much easier to address at design time than after the code is written. -Jason

8 20

[signals] Signals 1.33 dylib crashes when used with Xcode
by Chiedo Acholonu 02 Aug '05

02 Aug '05

I'm using boost 1.33 and recently tried to build the signals dll using the darwin toolset. I then created a simple Xcode project called TestSignals to test it was working correctly. The project only contains the maximum.cpp example file (/boost-root/libs/signals/examples/maximum.cpp) linked against the signals dynamic library. The project builds just fine, but when I run the app, Xcode crashes with: "TestSignals has exited due to signal 10 (SIGBUS)." Here is a piece of the crash log (I can send the full log on request): --- Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 maximum.ob 0x0040c844 std::less<int>::operator()(int const&, int const&) const + 48 (stl_function.h:227) --- I tried using different example files, and they all crash. The library is built multithreaded and I do define BOOST_SIGNALS_DYN_LINK in my project. I'm running on Tiger 10.4.2 using Xcode 2.1. Has anyone tried this or run into a similar problem? Thanks, Chiedo

1 0

singleton, dlls, and shared memory
by Jason Hise 02 Aug '05

02 Aug '05

I was researching how to ensure that a singleton has only one instance within a loaded dll and came up with this: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/ba… The page has a lot of information, and while most of it makes a decent amount of sense, a good deal of it is still unfamiliar territory for me. So I have a few of questions. A) Security Attributes. How important are they? Is it ok to just use null for this parameter, or should I be researching this structure and its effects in depth? B) Size of shared memory. It appears that the 'pseudo file' being used as shared memory is fixed in size and thus I have to guess how much I might need at compile time. Is there a way to resize this file if need be? C) Allocating and deallocating the memory. Is there existing code out there that takes a buffer of memory like this and manages malloc/free like calls to it (possibly wrapping the functionality in a std allocator) or do I need to roll my own? -Jason

1 0

[Boost-bugs] [ boost-Patches-1249809 ] Minor spell errors on lambda_functor_base.hpp header
by SourceForge.net 02 Aug '05

02 Aug '05

Patches item #1249809, was opened at 2005-08-01 22:57 Message generated for change (Settings changed) made by urzuga You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1249809&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Duilio J. Protti (dprotti) Assigned to: Nobody/Anonymous (nobody) Summary: Minor spell errors on lambda_functor_base.hpp header Initial Comment: Attached is the patch with the corresponding corrections. The patch is not just for /boost/lambda/detail/lambda_functor_base.hpp file, but also for lambda_fwd.hpp. Bye, Duilio Protti. ---------------------------------------------------------------------- Comment By: Jaakko Järvi (urzuga) Date: 2005-08-02 20:49 Message: Logged In: YES user_id=284669 Fixed ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1249809&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Patches-1249809 ] Minor spell errors on lambda_functor_base.hpp header
by SourceForge.net 02 Aug '05

02 Aug '05

Patches item #1249809, was opened at 2005-08-01 22:57 Message generated for change (Comment added) made by urzuga You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1249809&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Fixed Priority: 5 Submitted By: Duilio J. Protti (dprotti) Assigned to: Nobody/Anonymous (nobody) Summary: Minor spell errors on lambda_functor_base.hpp header Initial Comment: Attached is the patch with the corresponding corrections. The patch is not just for /boost/lambda/detail/lambda_functor_base.hpp file, but also for lambda_fwd.hpp. Bye, Duilio Protti. ---------------------------------------------------------------------- >Comment By: Jaakko Järvi (urzuga) Date: 2005-08-02 20:49 Message: Logged In: YES user_id=284669 Fixed ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=307586&aid=1249809&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Announcement] LCSD'05 Call for papers, extended deadline
by jarvi 02 Aug '05

02 Aug '05

The following call for papers should be of interest to many in the Boost community. For more information, see http://lcsd05.cs.tamu.edu Posting the announcement has been approved by Boost moderators. Best, Jaakko Järvi ----------------------------------------------------------------------- LIBRARY-CENTRIC SOFTWARE DESIGN - LCSD'05 Workshop, on Sunday, October 16, 2005 at the Object-Oriented Programming, Systems, Languages and Applications (OOPSLA'05) conference in San Diego, California, October 16-20, 2005 ----------------------------------------------------------------------- CALL FOR PAPERS --- EXTENDED DEADLINE The deadline for submission has been extended to Aug 07, 2005. ----------------------------------------------------------------------- Libraries are central to all major scientific, engineering, and business areas, yet the design, implementation, and use of libraries are underdeveloped arts. This workshop is one of the first steps in the process of placing all aspects of libraries on a sound technical and scientific basis through research into fundamental issues and documentation of best practices. A software library is an organized collection of code with associated tools supporting programming in general or in specific domains, usually united by a specified set of principles and conventions. Most libraries are aimed at the use by several people and in different environments. The areas of software library research include * Design and implementation of libraries * Program and system design based on libraries * Libraries supporting specific application domains, such as biology and banking * Evolution, refactoring, and maintenance of libraries * Empirical studies of library use * Performance of libraries, including benchmarking and library-based optimizations * Design of language facilities and tools in support of library definition and use * Validation, debugging, and testing of libraries * Extensibility, parameterization, and customization * Distribution of libraries * Specification of libraries and their semantics * Usability for library users and developers * Assessing quality of libraries * Documentation and teaching of libraries * Creating and supporting communities of library users * Using several libraries in combination We invite the submission of extended abstracts on software library research, including, but not limited to, the above list of topics. The extended abstracts should address issues important to libraries as a field, i.e., describe ideas or techniques that can be reused for libraries across problem domains and/or languages; they should refrain from merely describing a particular library, no matter how novel the choice of domain. As an additional criterion, the extended abstracts are reviewed against suitability for a journal publication of the corresponding full paper. For uniformity, authors should use the latest ACM SIGS conference style file (option 1) at http://www.acm.org/sigs/pubs/proceed/template.html. Submissions should be limited to 10 pages in this style. Accepted extended abstracts will be posted on the workshop's Web site prior to the workshop, and collected in a proceedings published as a Rensselaer Polytechnic Institute tech report. Authors of selected papers will be invited to submit a full paper for a special issue of a journal, to be announced later. IMPORTANT DATES Aug 7 Submission of extended abstracts (extended from Jul 31) Sep 9 Notification of acceptance Oct 4 Final version posted on workshop Web site Oct 16 Workshop SUBMISSION PROCEDURE For details of the electronic submission procedure, see the workshop's Web site, http://lcsd05.cs.tamu.edu. ORGANIZERS * David Musser, Rensselaer Polytechnic Institute * Andrew Lumsdaine, Indiana University * Jaakko Jarvi, Texas A&M University * Sibylle Schupp, Chalmers University of Technology * Todd Veldhuizen, Indiana University * Jeremy Siek, Rice University Primarily, the email address lcsd05(a)cs.tamu.edu should be used for questions addressed to the organizers. PROGRAM COMMITTEE * Uwe Assmann, Technical University of Dresden * Matt Austern, Google Inc. * Herve Broennimann, Polytechnic University * Antonio Cisternino, University of Pisa * Jack Dongarra, University of Tennessee * Ulrich Eisenecker, University of Leipzig * Rob Fowler, HiPerSoft, Rice University * Calvin Lin, University of Texas at Austin * Anthony Simons, University of Sheffield * Alex Stepanov, Adobe Systems Inc. * Bjarne Stroustrup, Texas A&M and AT&T Labs * Don Syme, Microsoft Research * Frank Tip, IBM Research In addition, the organizers will serve as program committee members. WORKSHOP GOALS AND ACTIVITIES The workshop establishes a scientific forum for presenting original research in the design, implementation, and evaluation of software libraries. Other major activities include the identification of open questions specific to library research and the discussion of a strategic plan for establishing library research as a field. The outcome of the workshop is a combination of research contributions and specific next steps for improving the infrastructure for library research. Participants are expected to read the accepted submissions beforehand. The technical presentations, although based on the accepted papers, should not provide mere summaries of the papers. Instead, authors are encouraged to use their presentation slots (20 + 10 mins) to bring up topics for discussion. The technical presentations are mixed with scientific and organizational discussions. The discussions aim at furthering the topics of the presentations, thus their agenda will be publicly discussed among the participants and then posted on the website of the workshop. All participants are expected to come prepared with their tentative answers or thoughts. The full-day workshop starts with a keynote talk for the stimulation of discussion and concludes with a plenary discussion that decides the specific next steps for improving the infrastructure for library research. FOR MORE INFORMATION AND UPDATES please visit the workshop's Web site, http://lcsd05.cs.tamu.edu.

1 0

Re: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X< Y >
by Andreas Huber 02 Aug '05

02 Aug '05

--- Brian Braatz <brianb(a)rmtg.com> wrote: > Suggestion: > > is there some way in your design you can get away with deriving > from the > incomplete type to "de-incomplete" it? I don't understand. You can't inherit from an incomplete type. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

1 0

Boost regression notification (2005-08-02)
by Douglas Gregor 02 Aug '05

02 Aug '05

Boost regression test failures ------------------------------ Report time: 2005-08-02T15:32:20Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 0 failure in 0 library:

4 3

[iostreams] problem with building library
by Alexey Bakhvalov 02 Aug '05

02 Aug '05

I am trying to build Boost RC1 and I have problem if I enable zlib and bzip2 support for IOStreams library. I am using Boost.Build system and I get the following error during the build process: unknown dependent target <@boost!libs!iostreams!build>libboost_bzip2.lib The build is executed from Boost root directory using .bat-file of the following contents: set NO_BZIP2=0 set NO_ZLIB=0 set ZLIB_SOURCE=.\external\zlib123 set ZLIB_INCLUDE=.\external\zlib123 set BZIP2_SOURCE=.\external\bzip2-1.0.3 set BZIP2_INCLUDE=.\external\bzip2-1.0.3 set TOOLS=vc-7_1 bjam install Am I doing something wrong or it's a problem of the build system? Alexey Bakhvalov

3 3

[tokenizer] offset_separator does not behave as docs state it does
by Bart 02 Aug '05

02 Aug '05

The docs for the offset_separator state the following regarding the breturnpartiallast construction parameter: "For example the string "122501" with offsets (2,2,4) ... With it set to false, it will parse to 12 25 and then will stop because there are only 2 characters left in the sequence instead of the 4 that should have been there." This leads me to believe, the string "1225011" (3 chars in last part) should also stop parsing after the first two tokens and ignore the third. It does not. Using the following example (compiled against current cvs)... int main(){ using namespace std; using namespace boost; string s = "1225199"; int offsets[] = {2,2,4}; offset_separator f(offsets, offsets+3, false, false); tokenizer<offset_separator> tok(s,f); for(tokenizer<offset_separator>::iterator beg=tok.begin(); beg!=tok.end();++beg){ cout << *beg << "\n"; } } Output is: 12 25 199 I think it should be just: 12 25 Thanks, Bart

1 0

1.33.0 Release, why not Beta it first?
by Michael Goldshteyn 02 Aug '05

02 Aug '05

I am going to once again raise the issue of putting the releases into Beta, prior to making a final (6-9 month) release. Perhaps we need a policy of the release being in a final Beta built form for some period, say 2-4 weeks, prior to the final release. I think this will allow people who wait for a packaged version to experiment with any newly added features, fixes, etc... and report issues that can be resolved in the final release, but were not made visible by the regression tests. Just my opinion, Mike

3 2

[1.33.0] User reports go live / feedback request
by Aleksey Gurtovoy 02 Aug '05

02 Aug '05

The following message is a courtesy copy of an article that has been posted to gmane.comp.lib.boost.testing as well. The draft version of user-centric regression reports is now available at http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/user/summar… (http://tinyurl.com/bamym) If you'd like to comment on usability/presentation of these before they go public with the release, now it's time :). -- Aleksey Gurtovoy MetaCommunications Engineering

3 5

[Boost-bugs] [ boost-Bugs-1250022 ] Spelling error in error message
by SourceForge.net 02 Aug '05

02 Aug '05

Bugs item #1250022, was opened at 2005-08-02 00:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250022&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: Spelling error in error message Initial Comment: In basic_archive.hpp, line 21: #error "no serialization headers my precede any archive headers" should be "may", not "my" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1250022&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X< Y >
by Brian Braatz 02 Aug '05

02 Aug '05

Suggestion: is there some way in your design you can get away with deriving from the incomplete type to "de-incomplete" it? > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Andreas Huber > Sent: Monday, August 01, 2005 3:33 AM > To: boost(a)lists.boost.org > Subject: [boost] [mpl] as_sequence< X< Y > > instantiates typedefs in X< Y > > > > Hi there > > I'm trying to address a point raised by Jonathan Turkanis during the > formal review of the statechart library. Basically, the problem boils > down to the following: > > #include <boost/mpl/list.hpp> > #include <boost/mpl/size.hpp> > #include <boost/mpl/as_sequence.hpp> > > namespace mpl = boost::mpl; > > // InnerInitial is either an mpl sequence of types or a single type > template< class InnerInitial > > struct state > { > // stateArray_ must have a length equal to the number of types > // in InnerInitial > int stateArray_[ > mpl::size< > typename mpl::as_sequence< InnerInitial >::type > >::type::value > ]; > }; > > // A is defined later, possibly in a different translation unit > struct A; > > template< class X > > struct B > { > typedef typename X::reactions reactions; > }; > > int main() > { > // fine: instantiation with an incomplete type > state< A > a; > // fine: instantiation with an mpl sequence containing B< A > > state< mpl::list< B< A > > > b; > // error: mpl::as_sequence triggers the instantiation of B's member > // typedef, which tries to access the member typedef of A. A compile- > // time error results because A is still incomplete at this point. > state< B< A > > c; // *** here *** > > return 0; > } > > MSVC7.1 and GCC3.4 agree that the last state template instantiation is > illegal (use of undefined type A). I'm wondering whether there is any > way to make this legal (different as_sequence implementation, implement > the state template differently, etc.)? > > Thanks & Regards, > > -- > Andreas Huber > > When replying by private email, please remove the words spam and trap > from the address shown in the header. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Re: [boost] [ANN] xpressive 0.9.5 in boost-sandbox
by Brian Braatz 02 Aug '05

02 Aug '05

Nice work! (I especially like the static expressions :) ) Any feel for when you will be ready for formal review? > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Eric Niebler > Sent: Monday, August 01, 2005 8:24 PM > To: Boost mailing list > Subject: [boost] [ANN] xpressive 0.9.5 in boost-sandbox > > << Background >> > xpressive is a TR1 regex work-alike that also accepts regexes as > expression templates and lets regexes nest and call each other > recursively. > > << Significant changes since 0.9.3 >> > - c_regex_traits to wrap the global C locale > - null_regex_traits for searching non-char data > - doc and test improvements > - bugs in static regexes and Unicode support squashed > > << Download >> > xpressive.zip at: > http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler > > << Docs >> > http://boost-sandbox.sf.net/libs/xpressive > > Note: You can consider this the xpressive 1.0 release candidate. All > that remains is to add more tests and documentation, and perhaps a tweak > to the traits interface. > > -- > Eric Niebler > Boost Consulting > www.boost-consulting.com > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[ANN] xpressive 0.9.5 in boost-sandbox
by Eric Niebler 02 Aug '05

02 Aug '05

<< Background >> xpressive is a TR1 regex work-alike that also accepts regexes as expression templates and lets regexes nest and call each other recursively. << Significant changes since 0.9.3 >> - c_regex_traits to wrap the global C locale - null_regex_traits for searching non-char data - doc and test improvements - bugs in static regexes and Unicode support squashed << Download >> xpressive.zip at: http://boost-sandbox.sf.net/vault/index.php?directory=eric_niebler << Docs >> http://boost-sandbox.sf.net/libs/xpressive Note: You can consider this the xpressive 1.0 release candidate. All that remains is to add more tests and documentation, and perhaps a tweak to the traits interface. -- Eric Niebler Boost Consulting www.boost-consulting.com

1 0