April 2010 - Boost - lists.boost.org

[uuid] Confusing uuid_class example in documentation
by Sylvester-Bradley, Gareth 29 Apr '10

29 Apr '10

http://beta.boost.org/doc/libs/1_42_0/libs/uuid/uuid.html#POD%20Efficien cies includes some example code for making a uuid_class from the struct uuid POD. I was confused to see the example uuid_class both derives from boost::uuids::uuid *and* provides operator boost::uuids::uuid() [const]. Aren't the conversion operators unnecessary, as a conversion function is never called to convert an object to a base class of that type (by 12.3.2 [class.conv.fct])? In fact the source file that the documentation references (e.g. at https://svn.boost.org/trac/boost/browser/tags/release/Boost_1_43_0_beta1 /libs/uuid/test/test_uuid_class.cpp) doesn't include the conversion operators. I think the documentation should be updated to match. Cheers, Gareth ************************************************************************ The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only. This email and any response may be monitored by Sony to be in compliance with Sony's global policies and standards

2 1

[function] function_template.hpp has ambiguous mem_fn calls on compilers with std::mem_fn (VC10); simple 2-line fix
by Conrad Poelman 29 Apr '10

29 Apr '10

*Summary*: It seems that function_template.hpp needs "boost::" in front of mem_fn in two spots so as not to be ambiguous with std::mem_fn on compilers that have std::mem_fn. (mem_fn appears in that file 4 times; two spots already use fully-qualified "boost::mem_fn".) I entered this at https://svn.boost.org/trac/boost/ticket/4073, but just wondered what the process is for having this fix committed to boost repository. **Example**: Here's a reproducible example that won't compile in Visual Studio 2010 (produces an "ambiguous call to overloaded function" error regarding mem_fn - could be boost::mem_fn or could be std::mem_fn) but that compiles fine in other compilers that don't have an std::mem_fn: #include<boost/function.hpp> #include<string> class PrimitiveBuilder { public: bool someFunction( std::string& token ); void registerSomeFunction() { mPrimitiveFunctor =&PrimitiveBuilder::someFunction; // ambiguity error is here } private: typedef boost::function<bool (PrimitiveBuilder*, std::string& token)> PrimitiveFunctor; PrimitiveFunctor mPrimitiveFunctor; }; The above code compiles and works fine in VS 2010 once "boost::" is added to mem_fn in function_template.hpp. I look forward to hearing your thoughts. Thanks! -- Conrad

1 0

running the regression tests with SunCC 5.9
by Frank Meerkötter 29 Apr '10

29 Apr '10

Hello, I am trying to run the regression tests for boost on a SunSparc machine with the SunCC 5.9. As i am trying to evaluate a certain version of boost i provide a local tarball. python run.py --runner meerkoetter --toolsets=sun --user= --local=../boost/boost_1_42_0.tar.bz2 The tests sits for a few minutes at this line. Before it fails. # Starting tests ("/home/meerkoef/boost_regression/tools_bjam/bin.solarissparc/bjam" "-sBOOST_BUILD_PATH=/home/meerkoef/boost_regression:/home/meerkoef/boost_regression/tools_bb" "-sBOOST_ROOT=/home/meerkoef/boost_regression/boost" "--boost=/home/meerkoef/boost_regression/boost" "--boost-build=/home/meerkoef/boost_regression/tools_bb" "--debug-configuration" -l300 sun -d2 preserve-test-targets=off --dump-tests "--build-dir=/home/meerkoef/boost_regression/results" >>"/home/meerkoef/boost_regression/results/bjam.log" 2>&1)... # Running Boost.Build tests Traceback (most recent call last): File "run.py", line 60, in ? runner(root) File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 193, in __init__ self.main() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 551, in main getattr(self,action_m)() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 516, in command_regression self.command_test() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 317, in command_test self.command_test_boost_build() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 354, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); OSError: [Errno 2] No such file or directory: '/home/meerkoef/boost_regression/results/boost/bin.v2/libs/any/test/any_test.test' The last few lines in bjam.log show: [...] boost-test(RUN) "config/no_void_returns_pass" : "libs/config/test/no_void_returns_pass.cpp" boost-test(COMPILE_FAIL) "config/no_void_returns_fail" : "libs/config/test/no_void_returns_fail.cpp" boost-test(RUN) "config/no_wchar_t_pass" : "libs/config/test/no_wchar_t_pass.cpp" boost-test(COMPILE_FAIL) "config/no_wchar_t_fail" : "libs/config/test/no_wchar_t_fail.cpp" don't know how to make <e>sun ...found 1 target... ...can't find 1 target... Any ideas how i can fix this? btw. i noticed that the tools are build using the gcc and not the sun compiler. Is this correct? In the end i don't care what compiler is used to create the regression testing tools but still it makes me wonder if the tests are compiled with the right compiler? Here is the complete log: # Running regressions in /home/meerkoef/boost_regression... # Creating regression scripts at /home/meerkoef/boost_regression/tools_regression_src... # Dowloading regression scripts from http://svn.boost.org/svn/boost/trunk/tools/regression/src... # Getting Boost.Build v2... # Downloading "http://beta.boost.org/development/snapshot.php/trunk/tools/build/v2" to "/home/meerkoef/boost_regression"... # Looking for old unpacked archives... # Unpacking boost tarball ("/home/meerkoef/boost_regression/tools_bb.tar.bz2")... # Unpacked into directory "/home/meerkoef/boost_regression/boost-trunk-2010-04-26-09-02-11-EDT" # Deleting "tools_bb" directory... # Renaming "/home/meerkoef/boost_regression/boost-trunk-2010-04-26-09-02-11-EDT" into "tools_bb" # Getting Boost.Jam... # Downloading "http://beta.boost.org/development/snapshot.php/tags/tools/jam/Boost_Jam_3_1…" to "/home/meerkoef/boost_regression"... # Looking for old unpacked archives... # Unpacking boost tarball ("/home/meerkoef/boost_regression/tools_bjam.tar.bz2")... # Unpacked into directory "/home/meerkoef/boost_regression/boost-tags-2010-04-26-09-02-30-EDT" # Deleting "tools_bjam" directory... # Renaming "/home/meerkoef/boost_regression/boost-tags-2010-04-26-09-02-30-EDT" into "tools_bjam" # Getting regression tools an utilities... # Downloading "http://beta.boost.org/development/snapshot.php/trunk/tools/regression" to "/home/meerkoef/boost_regression"... # Looking for old unpacked archives... # Unpacking boost tarball ("/home/meerkoef/boost_regression/tools_regression.tar.bz2")... # Unpacked into directory "/home/meerkoef/boost_regression/boost-trunk-2010-04-26-09-02-51-EDT" # Deleting "tools_regression" directory... # Renaming "/home/meerkoef/boost_regression/boost-trunk-2010-04-26-09-02-51-EDT" into "tools_regression" # Getting boost-build.jam... # Using local file "../boost/boost_1_42_0.tar.bz2" # Tag: "boost_1_42_0" # Looking for old unpacked archives... # Unpacking boost tarball ("../boost/boost_1_42_0.tar.bz2")... # Unpacked into directory "/home/meerkoef/boost_regression/boost_1_42_0" # Deleting "/home/meerkoef/boost_regression/boost" directory... # Renaming "/home/meerkoef/boost_regression/boost_1_42_0" into "/home/meerkoef/boost_regression/boost" # Preinstalled "/home/meerkoef/boost_regression/bjam" is not found; building one... # Found "bjam" source directory "/home/meerkoef/boost_regression/tools_bjam" # Building "bjam" (./build.sh )... ### ### Using 'gcc' toolset. ### rm -rf bootstrap mkdir bootstrap gcc -o bootstrap/jam0 command.c compile.c debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c md5.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c ./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap/jam0 -f build.jam --toolset=gcc --toolset-root= ...found 48 targets... ...updating 2 targets... [MKDIR] bin.solarissparc [COMPILE] bin.solarissparc/bjam ...updated 2 targets... # Searching for "bjam" in "/home/meerkoef/boost_regression/tools_bjam"... # bjam succesfully built in "/home/meerkoef/boost_regression/tools_bjam/bin.solarissparc/bjam" location # Preinstalled "/home/meerkoef/boost_regression/process_jam_log" is not found; building one... # Found "process_jam_log" source directory "/home/meerkoef/boost_regression/tools_regression/build" # Building "process_jam_log" ("/home/meerkoef/boost_regression/tools_bjam/bin.solarissparc/bjam" "-sBOOST_BUILD_PATH=/home/meerkoef/boost_regression:/home/meerkoef/boost_regression/tools_bb" "-sBOOST_ROOT=/home/meerkoef/boost_regression/boost" "--boost=/home/meerkoef/boost_regression/boost" "--boost-build=/home/meerkoef/boost_regression/tools_bb" "--debug-configuration" process_jam_log -d2 -l300)... notice: found boost-build.jam at /home/meerkoef/boost_regression/boost-build.jam notice: loading Boost.Build from /home/meerkoef/boost_regression/tools_bb notice: Searching /etc /home/meerkoef /home/meerkoef/boost_regression/tools_bb /home/meerkoef/boost_regression /home/meerkoef/boost_regression/tools_bb /home/meerkoef/boost_regression/tools_bb/kernel /home/meerkoef/boost_regression/tools_bb/util /home/meerkoef/boost_regression/tools_bb/build /home/meerkoef/boost_regression/tools_bb/tools /home/meerkoef/boost_regression/tools_bb/contrib /home/meerkoef/boost_regression/tools_bb/. for site-config configuration file site-config.jam . notice: Loading site-config configuration file site-config.jam from /home/meerkoef/boost_regression/tools_bb/site-config.jam . notice: Searching /home/meerkoef /home/meerkoef/boost_regression/tools_bb /home/meerkoef/boost_regression /home/meerkoef/boost_regression/tools_bb /home/meerkoef/boost_regression/tools_bb/kernel /home/meerkoef/boost_regression/tools_bb/util /home/meerkoef/boost_regression/tools_bb/build /home/meerkoef/boost_regression/tools_bb/tools /home/meerkoef/boost_regression/tools_bb/contrib /home/meerkoef/boost_regression/tools_bb/. for user-config configuration file user-config.jam . notice: Loading user-config configuration file user-config.jam from /home/meerkoef/boost_regression/tools_bb/user-config.jam . notice: iostreams: using prebuilt zlib notice: iostreams: using prebuilt bzip2 notice: [python-cfg] Configuring python... notice: [python-cfg] Checking interpreter command "python"... notice: [python-cfg] running command '"python" -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1' notice: [python-cfg] ...requested configuration matched! notice: [python-cfg] Details of this Python configuration: notice: [python-cfg] interpreter command: "python" notice: [python-cfg] include path: "/usr/include/python2.4" notice: [python-cfg] library path: "/usr/lib/python2.4/config" "/usr/lib" warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html notice: will use 'g++' for gcc, condition <toolset>gcc-3.4.3 notice: using gcc libraries :: <toolset>gcc-3.4.3 :: /usr/sfw/bin /usr/sfw/lib /usr/sfw/lib32 /usr/sfw/lib64 notice: using gcc archiver :: <toolset>gcc-3.4.3 :: /usr/sfw/sparc-sun-solaris2.10/bin/ar notice: using gcc ranlib :: <toolset>gcc-3.4.3 :: /usr/sfw/sparc-sun-solaris2.10/bin/ranlib warning: toolset gcc initialization: can not find tool windres warning: initialized from notice: using rc compiler :: <toolset>gcc-3.4.3 :: as ...patience... ...found 487 targets... ...updating 27 targets... common.mkdir bin mkdir -p "bin" common.mkdir bin/gcc-3.4.3 mkdir -p "bin/gcc-3.4.3" common.mkdir bin/gcc-3.4.3/release mkdir -p "bin/gcc-3.4.3/release" gcc.compile.c++ bin/gcc-3.4.3/release/process_jam_log.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -D_CRT_SECURE_NO_WARNINGS -I"/home/meerkoef/boost_regression/boost" -c -o "bin/gcc-3.4.3/release/process_jam_log.o" "../src/process_jam_log.cpp" ../src/process_jam_log.cpp: In function `int main(int, char**)': ../src/process_jam_log.cpp:692: warning: comparison between signed and unsigned integer expressions gcc.compile.c++ bin/gcc-3.4.3/release/tiny_xml.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -fPIC -DBOOST_ALL_NO_LIB=1 -DNDEBUG -D_CRT_SECURE_NO_WARNINGS -I"/home/meerkoef/boost_regression/boost" -c -o "bin/gcc-3.4.3/release/tiny_xml.o" "../src/detail/tiny_xml.cpp" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2 mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3 mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static" gcc.compile.c++ /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/operations.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_All_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/home/meerkoef/boost_regression/boost" -c -o "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/operations.o" "/home/meerkoef/boost_regression/boost/libs/filesystem/src/operations.cpp" gcc.compile.c++ /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/path.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_All_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/home/meerkoef/boost_regression/boost" -c -o "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/path.o" "/home/meerkoef/boost_regression/boost/libs/filesystem/src/path.cpp" gcc.compile.c++ /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/portability.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_All_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/home/meerkoef/boost_regression/boost" -c -o "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/portability.o" "/home/meerkoef/boost_regression/boost/libs/filesystem/src/portability.cpp" gcc.compile.c++ /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/utf8_codecvt_facet.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_All_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/home/meerkoef/boost_regression/boost" -c -o "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/utf8_codecvt_facet.o" "/home/meerkoef/boost_regression/boost/libs/filesystem/src/utf8_codecvt_facet.cpp" RmTemps /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a(clean) rm -f "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a" gcc.archive /home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a "/usr/sfw/sparc-sun-solaris2.10/bin/ar" rc "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/operations.o" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/path.o" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/portability.o" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/utf8_codecvt_facet.o" "/usr/sfw/sparc-sun-solaris2.10/bin/ranlib" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/system mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/system" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3 mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release" common.mkdir /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static mkdir -p "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static" gcc.compile.c++ /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/error_code.o "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"/home/meerkoef/boost_regression/boost" -c -o "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/error_code.o" "/home/meerkoef/boost_regression/boost/libs/system/src/error_code.cpp" RmTemps /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a(clean) rm -f "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a" gcc.archive /home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a "/usr/sfw/sparc-sun-solaris2.10/bin/ar" rc "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a" "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/error_code.o" "/usr/sfw/sparc-sun-solaris2.10/bin/ranlib" "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a" gcc.link bin/gcc-3.4.3/release/process_jam_log "g++" -o "bin/gcc-3.4.3/release/process_jam_log" "bin/gcc-3.4.3/release/process_jam_log.o" "bin/gcc-3.4.3/release/tiny_xml.o" "/home/meerkoef/boost_regression/boost/bin.v2/libs/filesystem/build/gcc-3.4.3/release/link-static/libboost_filesystem.a" "/home/meerkoef/boost_regression/boost/bin.v2/libs/system/build/gcc-3.4.3/release/link-static/libboost_system.a" -mimpure-text ...updated 27 targets... # Searching for "process_jam_log" in "/home/meerkoef/boost_regression/tools_regression/build"... # process_jam_log succesfully built in "/home/meerkoef/boost_regression/tools_regression/build/bin/gcc-3.4.3/release/process_jam_log" location # Making "/home/meerkoef/boost_regression/results" directory... # Starting tests ("/home/meerkoef/boost_regression/tools_bjam/bin.solarissparc/bjam" "-sBOOST_BUILD_PATH=/home/meerkoef/boost_regression:/home/meerkoef/boost_regression/tools_bb" "-sBOOST_ROOT=/home/meerkoef/boost_regression/boost" "--boost=/home/meerkoef/boost_regression/boost" "--boost-build=/home/meerkoef/boost_regression/tools_bb" "--debug-configuration" -l300 sun -d2 preserve-test-targets=off --dump-tests "--build-dir=/home/meerkoef/boost_regression/results" >>"/home/meerkoef/boost_regression/results/bjam.log" 2>&1)... # Running Boost.Build tests Traceback (most recent call last): File "run.py", line 60, in ? runner(root) File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 193, in __init__ self.main() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 551, in main getattr(self,action_m)() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 516, in command_regression self.command_test() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 317, in command_test self.command_test_boost_build() File "/home/meerkoef/boost_regression/tools_regression_src/regression.py", line 354, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); OSError: [Errno 2] No such file or directory: '/home/meerkoef/boost_regression/results/boost/bin.v2/libs/any/test/any_test.test'

3 3

[Review] [ITL] ITL formal review results
by Hartmut Kaiser 29 Apr '10

29 Apr '10

Hi all, The formal review of the Interval Template Library (ITL) written by Joachim Faulhaber started February 18th and ended March 7th, 2010. We saw a lively discussion resulting in 14 votes: 10 people voted unconditionally YES, 3 voted conditionally YES, and 1 reviewer voted NO. The overwhelming majority of the votes was YES which reflects the overall discussion and the general consensus of this library being worth to be included into Boost. Based on this result and the discussions we saw the Interval Template Library is now formally accepted into Boost. Detailed results ---------------- Pros: Almost all reviewers highlighted the general usefulness of the library. The more experience the reviewers had with the library in real world applications the more they emphasized its usefulness. Here are some quotes: - "ITL solved this problem for me, in a way that honestly freed me from having to think about a lot of the unsavory low-level details." - " Until now, we only used the library for intervals of date-times (coded as integers), but I'm sure, that its usefulness goes far beyond." - " Very useful. I mentioned two projects where the library would have helped me if it had been into Boost earlier, and I'm considering rewriting them such that the problems make use of the library, and simplify them in that way." The comments on the quality of the documentation are unanimous: "impressive and quite complete", "I couldn't ask for more". It seemed to be generally helpful to understand the concepts of the library and to get started. Some people asked to add more simple quick-start examples to the documentation and the distribution. Overall, the library is mature and easy to use. All reviewers actually utilizing the ITL library for real world use cases reported they were able to start quickly and without problems. All reviewers using ITL in real world applications stated that no performance problems were encountered. This is important to note as the NO vote was based on the current lack of a interval tree implementation, which was considered to result in suboptimal performance for certain use cases. Cons: Some aspects of the design have been criticized: "OO-type design decisions", "fat 'one size fits all'-interval class template", and "incomplete extraction of global functions" are the major points of critique. These points have real merit. In order to make the design and interface more flexible and more durable these have to be rectified before the final inclusion of the library into Boost's code base. Joachim already agreed to a list of things to change addressing those problems. For certain use cases, specifically for interval map of collections, the current implementation has suboptimal complexity characteristics that leads to O(n^2) space usage in the worst case. OTOH, for the majority of applications of the library the worst case scenario seems to be (reportedly) irrelevant. This issue has been discussed at length and Joachim plans to add an implementation with a better worst case performance of the affected class templates as later optimizations. This is not considered to be a precondition to full inclusion into Boost's code base as it is not anticipated to cause any interface changes. Last but not least people suggested to change the name of the library as having the word template in the name does not carry any useful information. Joachim already agreed to this. Regards Hartmut Review Manager --------------- Meet me at BoostCon www.boostcon.com

3 3

About command line parameters parsing again...
by Denis Shevchenko 29 Apr '10

29 Apr '10

Hi all! Sorry for my English... During last two months I develop simple library for command line parameters parsing. Although there is many such libraries (e.g. on sf.net) I cannot find library with _realy_ simple using. Command line parameters parsing is simple, trivial task, so (imho) library for this task must be easy-to-learn and easy-to-use. Boost.Program_options is good and flexible library, but (imho) work with command line parameters must be easier. My library _not_ parse config file, because I like rule "one task - one library". My question: is it need in Boost another library for command line parameters parsing? P.S. Library: https://sourceforge.net/projects/clp-parser/ Denis

1 0

[range] irange is not very eloquent
by vicente.botet 29 Apr '10

29 Apr '10

Hi, I have find the function 'irange' in the section "Provided Ranges". template<class Integer> integer_range< range_detail::integer_iterator<Integer> > irange(Integer first, Integer last); I will expect in this section ranges and not functions. This function allows to treat integers as a model of the Random Access Range Concept. I find the name not very eloquent. What about make_integer_range, for example? BTW, I don't find the documentation of the the class integer_range. Where it is documented? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

3 10

[range] Permission to merge extensive documentation work from trunk.
by Neil Groves 29 Apr '10

29 Apr '10

Please may I merge just the documentation changes that have been performed on the trunk? These include: 1. corrections to documentation errors 2. complete documentation of the header files 3. acknowledgements for the Boost.RangeEx work. Regards, Neil Groves

3 6

[GSoC][boost.process] Blog
by Felipe Tanus 29 Apr '10

29 Apr '10

Hi, My project for Google Summer of Code was accepted, as many of you already know. I would like to give my thanks to anyone that supported me. I'll give my best in this project. Writing with my mentor, we decided that would be a good idea to keep an track from our actions, project decisions and have a place where interested people could help us without the need of we ask. Then, I created a blog that I'll write whenever I have something significant to tell. If you are interested in this project, I invite you to follow the updates from this blog[1] and comment whenever you like. This way, we might post in this mailing list only when it's strictly needed about the project. Thank you. [1] http://gsoc2010.fotanus.com -- Felipe de Oliveira Tanus E-mail: fotanus(a)gmail.com Blog: http://www.itlife.com.br Site: http://www.inf.ufrgs.br/~fotanus/ ----- "All we have to decide is what to do with the time that is given us." - Gandalf

1 0

[ANN] CodeSynthesis XSD 3.3.0 released
by Boris Kolpackov 29 Apr '10

29 Apr '10

Hi, I am pleased to announce the availability of CodeSynthesis XSD 3.3.0. CodeSynthesis XSD is an open-source (GPL2 + proprietary license), cross- platform W3C XML Schema to C++ data binding compiler. Provided with a schema, it generates C++ classes that represent the given vocabulary as well as parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with elements, attributes, and text in a direct representation of XML such as DOM or SAX. The XSD compiler uses several Boost libraries (filesystem and regex) in its implementation. The generated code can also map XML Schema date/time built- in types to Boost date_time types. The C++ classes can also be serialized into various binary formats besides XML. Boost serialization library is supported as one of the representations. Major new features in this release: * Support for uniform parsing and serialization of XML documents with varying root elements. * Configurable application character encoding (UTF-8, ISO-8859-1, etc). * Support for stream-oriented, partially in-memory/partially event- driven XML parsing and serialization. * Support for embedding the binary representation of the schema grammar into the application. * Generation of the detach functions that allow moving object model sub-trees without copying. * Support for XML compression. * Smaller and faster generated code for polymorphic XML Schemas (xsi:type and substitution groups). The release also adds support for a range of new operating system and C++ compiler versions, including: * AIX 6.x * Mac OS X 10.6 * Windows 7, * Windows Server 2008 * Visual Studio 2010 (10.0) * GNU g++ 4.5.0 * Intel C++ 11 * Sun Studio 12.1 * IBM XL C++ 11 Visual Studio 2010 project and solution files are provided for all the examples. For the complete list of new features in this release see: http://www.codesynthesis.com/pipermail/xsd-announcements/2010/000038.html CodeSynthesis XSD is available on IBM AIX, GNU/Linux, HP-UX, Mac OS X, Solaris, Windows, OpenVMS, and z/OS. Supported C++ compilers include: GNU g++, HP aCC, IBM XL C++, Intel C++, Sun C++, and MS Visual C++. More information, documentation, source code, and precompiled binaries for all the supported platforms are available from: http://www.codesynthesis.com/products/xsd/ Boris -- Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde Command line interface to C++ compiler http://codesynthesis.com/projects/cli

3 4

People in charge for the Boost-CMake mailing list
by Isidor Zeuner 29 Apr '10

29 Apr '10

Hello fellow Boosters, a couple of days ago I posted a message to the Boost-CMake mailing list and received a notification about the message awaiting moderator approval. Since then it was neither posted, nor did I receive a rejection notice. So I'm wondering if there is currently someone in charge of moderating this list, and if the message will expire at some point. Best regards, Isidor Zeuner

2 3