October 2005 - Boost - lists.preview.boost.org

BOOST_WORKAROUND and g++ -Wundef
by Angus Leeming 23 Oct '05

23 Oct '05

Compiling the attached code with g++ 3.4.4 as g++ -Wundef -Iboost/cvs -o trial trial.cpp produces a heap of warnings warning: "__BORLANDC__" is not defined warning: "_MSC_FULL_VER" is not defined warning: "__MWERKS__" is not defined The warnings are produced by code like: #if BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3003)) and are, of course, silenced by: #if defined(__MWERKS__) && \ BOOST_WORKAROUND(__MWERKS__, BOOST_TESTED_AT(0x3003)) Grepping around the boost sources, I see that my 'fix' has been applied about 70 times already in the 1260 uses of BOOST_WORKAROUND. Assuming that the lack of consistency reflects only the size of the task, I've made a patch applying the fix to Boost.Random. Chipping away at the block... Hoping that this is useful, Angus

4 16

regex - linking problem
by John Smith 23 Oct '05

23 Oct '05

Dear All, I have a problem linking with regex that I couldn't resolve - would greatly appreciate if anyone could give me a hint. I followed the discussion threads regarding similar problems and got forward with resolving other issues, however this final single problem I could not resolve: error LNK2001: unresolved external symbol "void __cdecl boost::re_detail::raise_runtime_error(class _STL::runtime_error const &)" (?raise_runtime_error@re_detail@boost@@YAXABVruntime_error@_STL@@@Z) My environment: o Windows XP o Microsoft DevStudio - Visual C++ 6, Service pack 6 o I am building my DLL, which will use boost::regex as (an additional) DLL o My build flags - Multithreaded dll (more info is avail if needed) o I am using stlport (which is located on my environment under '...\VC98\Include\stlport\...') o I include <boost/regex.hpp> and using 'boost::wregex', 'boost::wcmatch', 'boost::regex_search', etc o I added the next to 'user.hpp': #define BOOST_REGEX_NO_W32 #define BOOST_REGEX_NO_LIB o I am adding boost library to my linking process with the next pragma statement: #ifdef _DEBUG #pragma comment(lib, "<...the path...>\\boost_regex-vc6-mt-gdp-1_33") #else #pragma comment(lib, "<...the path...>\\boost_regex-vc6-mt-p-1_33") #endif // _DEBUG boost::regex build: o I use BJame.exe to build boost o I call 'VCVars32.bat' before all o I set the next environment variables before calling BJam: * VISUALC=<..the path to 'VC98'...> * INCLUDE=%STLPORT_PATH%;%INCLUDE% o Build line: BJam.exe -a -sTOOLS=MSVC-STLPORT --with-regex ...after all this: the linker error (unresolved 'raise_runtime_error' as written above) M A N Y T H A N K S ! ! ! Paz _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

3 7

Re: [boost] [Review] of binary_int utility starts
by Cromwell Enage 23 Oct '05

23 Oct '05

Errata: In the example I sent, each binary_int should have had all four template arguments set to 1111. (This is what happens when I deal with hexadecimals for too long.) Cromwell D. Enage __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs

1 0

[Review] of binary_int utility starts
by Pavel Vozenilek 22 Oct '05

22 Oct '05

Review of binary_int utility written by Scott Schurr begins today and lasts for 7 days. The utility can be found at http://boost-consulting.com/vault/ file binary_int.zip (8 kB). ===Description=== The class template binary_int allows binary literals to be used at compile time. The template reads a binary literal value comprised of from 1 to 16 comma separated 4-bit units of ones and zeros. Example of use: #include <boost/utility.hpp> unsigned int regValue2 = binary_int<1000,1001,0011,0000>::value; enum { val1 = binary_int<1100,0010>::value, val2 = binary_int<1100,0011>::value }; switch (x) { case binary_int<0110,0001>::value: ... break; case binary_int<0111,0001>::value: ... break; } ===Alternative implementation=== Matt Calabrese had written alternative, using only preprocessor. It can be found at http://www.illegal-immigration.com/Riv/boost/binary_literal.hpp Example of use: BOOST_BINARY_LITERAL( 101 0111 1010 0110 ) (there is no need for ::value, more on http://lists.boost.org/Archives/boost/2005/09/93007.php) ===Open questions in Scott Schurs's library=== * How does it work on 64 bit systems? Could someone try? * Naming: perhaps shorter names could be used (e.g. bits/nibble) * BOOST_WORKAROUND in the code, is it really needed? === Questions for the reviewers=== * Which one of the alternatives fits in Boost better? * What is your evaluation of the implementation(s)? * Do you think the utility should be accepted as a Boost library? /Pavel

6 6

Boost regression notification (2005-10-22 [RC_1_33_0])
by Douglas Gregor 22 Oct '05

22 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-22T14:17:08Z 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… 27 failures in 5 libraries: parameter (2) range (3) serialization (18) thread (1) variant (3) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |range| array: vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_demo_xml_load: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 test_demo_xml_load_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_shared_ptr_132_text_warchive: intel-win32-8_1 test_shared_ptr_binary_archive: borland-5_6_4 test_shared_ptr_binary_archive_dll: borland-5_6_4 test_shared_ptr_text_archive: borland-5_6_4 test_shared_ptr_text_archive_dll: borland-5_6_4 test_shared_ptr_text_warchive: borland-5_6_4 test_shared_ptr_text_warchive_dll: borland-5_6_4 test_shared_ptr_xml_archive: borland-5_6_4 test_shared_ptr_xml_archive_dll: borland-5_6_4 test_shared_ptr_xml_warchive: borland-5_6_4 test_shared_ptr_xml_warchive_dll: borland-5_6_4 |thread| test_thread: intel-win32-8_1 |variant| variant_test2: mingw-3_4_2 variant_test5: mingw-3_4_2 variant_test6: mingw-3_4_2

1 0

Boost regression notification (2005-10-22 [HEAD])
by Douglas Gregor 22 Oct '05

22 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-22T05:00:25Z 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. conversion Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 418 failures in 14 libraries: concept_check (13) conversion (2) date_time (6) graph (2) mpl (1) parameter (3) python (2) serialization (36) spirit (8) thread (4) tuple (1) type_traits (311) typeof (21) xpressive (8) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 |conversion| cast_test: vc-7_1 implicit_cast: vc-7_1 |date_time| testconstrained_value: vc-7_1 testgeneric_period: vc-7_1 testgregorian_calendar: vc-7_1 testint_adapter: vc-7_1 testtime_resolution_traits: vc-7_1 testwrapping_int: vc-7_1 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| efficiency: msvc sfinae: msvc tutorial: gcc-2.95.3-linux |python| builtin_converters: intel-win32-9_0 exec: intel-win32-9_0 |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin 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 |spirit| action_tests_debug: gcc-3_4_3-sunos distinct_tests_debug: gcc-3_4_3-sunos escape_char_parser_tests_debug: gcc-3_4_3-sunos grammar_def_test_debug: gcc-3_4_3-sunos switch_problem_debug: gcc-3_4_3-sunos switch_tests_single_debug: gcc-3_4_3-sunos traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |thread| test_condition: gcc-3_4_3-sunos test_mutex: gcc-3_4_3-sunos test_tss: gcc-3_4_3-sunos gcc-3_4_3-sunos |tuple| tuple_test_bench: gcc-3_4_3-sunos |type_traits| add_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 add_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 aligned_storage_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 alignment_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_nothrow_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_assign_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_constr_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_copy_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_trivial_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 has_virtual_destructor_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_abstract_test: gcc-3.4.4-linux vc-7_1 is_arithmetic_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_array_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_base_of_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_class_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_compound_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_convertible_test: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_empty_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_enum_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_floating_point_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_function_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_fundamental_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_integral_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_func_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_obj_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_member_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_object_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pod_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_polymorphic_test: gcc-2.95.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_same_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_scalar_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_signed_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_union_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_unsigned_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_void_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 is_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 rank_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_all_extents_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_const_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_cv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_extent_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_pointer_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_reference_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 remove_volatile_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin vc-7_1 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |xpressive| test3: gcc-3.4.4-linux test3u: gcc-3_3-darwin test4u: gcc-3_3-darwin test5: gcc-3.4.4-linux test5u: gcc-3_3-darwin test6: gcc-3.4.4-linux test6u: gcc-3_3-darwin test9u: gcc-3_3-darwin

1 0

[config] Standard version macros proposal -- Reviving the compiler version macros.
by Rene Rivera 22 Oct '05

22 Oct '05

After reading up on past discussions about what people want from a set of standard macros for compiler identification, I put together a wiki page with past information on the subject and my ideas as to what the consensus is. And basic proposal based on the ideas: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostConfig Discussion, contributions, funny anecdotes are welcome :-) -- -- 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

5 7

[mpl] weird error using has_xxx.hpp
by Andy Little 22 Oct '05

22 Oct '05

Hi, using VC7.1... In the following the output is 0, whereas it should be 1 . However commenting out either of the first 2 headers makes result correct. Can anyone repeat this in VC7.1? ------------- #include <boost/mpl/modulus.hpp> #include <boost/mpl/apply.hpp> #include <boost/mpl/has_xxx.hpp> namespace my{ template<typename T> struct X{ typedef int tag; }; BOOST_MPL_HAS_XXX_TRAIT_DEF(tag); } int main() { std::cout << my::has_tag<my::X<int> >::value << '\n'; } --------------- cheers Andy Little

2 2

Is portability to pre-standard compiler an issue when considering addition to boost library
by Axter 22 Oct '05

22 Oct '05

If code is proposed to be added to the boost library, and it can not compile on non-compliant (pre-standard) compiler, like VC++ 6.0, would that be a major factor for rejection? I have classes that are fully compliant to the C++ standard, but will not compile on VC++ 6.0, because 6.0 doesn't fully support template logic. Is this a factor in consideration for code addition to the boost library?

2 1

Fw: [Boost-bugs] [ boost-Support Requests-1334003 ] 100s of 'template with C linkage' errors
by Peter Dimov 22 Oct '05

22 Oct '05

Forwarding for archival purposes :-) Michael Hopkins wrote: > On 21/10/05 21:44, "Peter Dimov" <pdimov(a)mmltd.net> wrote: > >> I have no access to Mac OS X, but according to this post: >> >> http://www.pixelglow.com/lists/archive/macstl-dev/2005-February/000015.html >> >> this might be caused by the fact that your Boost headers are in >> /usr/include, because GCC has some heuristic that automatically >> encloses system headers in extern "C" blocks. >> >> http://developer.apple.com/documentation/DeveloperTools/gcc-4.0.0/cpp/Syste… >> eaders.html >> >> > Thanks for this Peter. Putting Boost in /opt/local/include/ has > solved the problem. I wonder if this should be mentioned somewhere > in the darwin Boost docs to stop other people going around the same > loop? > > Michael > > > > > > Web: http://www.hopkins-research.com/ > Phone: +44 (O)781 3467 381

1 0