- Boost - lists.boost.org

Macros at namespace scope: trailing semicolon?
by David Abrahams 14 Oct '05

14 Oct '05

I am defining a macro, BOOST_PARAMETER_KEYWORD(tag_namespace, name) that declares a keyword for the Parameter library. It has to be used at namespace scope. I have the option to define it so that correct usage requires a trailing semicolon, or so that the trailing semicolon is forbidden. Unfortunately I don't have the ability to make it optional. Which should I choose? IMO there's no chance of confusing it with a function call, since a function call would be illegal in the context in which it's used, and people are naturally more likely to add a semicolon without thinking about it, and if I design the macro so that a semicolon is required it will interact more smoothly with editors and pretty-printers. So I can't see any good reason not to require the semicolon. Arguments? -- Dave Abrahams Boost Consulting www.boost-consulting.com

19 87

[wave] Using wave to preprocess boost headers
by Thomas Andersen 14 Oct '05

14 Oct '05

I have tried to get wave to preprocess the boost headers. However I get an error in cstdint.hpp line 246 # if ULONG_MAX == 18446744073709551615 // 2**64 - 1 error: ill formed integer literal or integer constant too large: 18446744073709551615 Have anybody else encountered this problem, and found a way around it? Best regards, Thomas Andersen

4 4

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

14 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-14T13:51:13Z 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… 76 failures in 5 libraries: parameter (3) python (2) range (3) serialization (63) variant (5) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux unnamed: vc-7_1 |python| pointer_vector: cw-9_4 vector_indexing_suite: cw-9_4 |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_exported_binary_archive: vc-6_5 test_exported_binary_archive_dll: vc-6_5 test_exported_text_archive: vc-6_5 test_exported_text_archive_dll: vc-6_5 test_exported_text_warchive: vc-6_5 test_exported_text_warchive_dll: vc-6_5 test_exported_xml_archive: vc-6_5 test_exported_xml_archive_dll: vc-6_5 test_exported_xml_warchive: vc-6_5 test_exported_xml_warchive_dll: vc-6_5 test_no_rtti_binary_archive: vc-6_5 test_no_rtti_binary_archive_dll: vc-6_5 test_no_rtti_text_archive: vc-6_5 test_no_rtti_text_archive_dll: vc-6_5 test_no_rtti_text_warchive: vc-6_5 test_no_rtti_text_warchive_dll: vc-6_5 test_no_rtti_xml_archive: vc-6_5 test_no_rtti_xml_archive_dll: vc-6_5 test_no_rtti_xml_warchive: vc-6_5 test_no_rtti_xml_warchive_dll: vc-6_5 test_shared_ptr_132_binary_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_binary_archive_dll: vc-6_5 test_shared_ptr_132_text_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_archive_dll: vc-6_5 test_shared_ptr_132_text_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_text_warchive_dll: intel-win32-8_1 vc-6_5 test_shared_ptr_132_xml_archive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_archive_dll: vc-6_5 test_shared_ptr_132_xml_warchive: vc-6_5 vc-6_5-stlport test_shared_ptr_132_xml_warchive_dll: vc-6_5 test_shared_ptr_binary_archive: borland-5_6_4 vc-6_5 test_shared_ptr_binary_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive: borland-5_6_4 vc-6_5 test_shared_ptr_text_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_text_warchive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_archive_dll: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive: borland-5_6_4 vc-6_5 test_shared_ptr_xml_warchive_dll: borland-5_6_4 vc-6_5 |variant| recursive_variant_test: mingw-3_4_2 variant_test4: mingw-3_4_2 variant_test6: mingw-3_4_2 variant_test7: mingw-3_4_2 variant_test8: mingw-3_4_2

1 0

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

14 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-14T05:00:23Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 141 failures in 12 libraries: concept_check (13) graph (2) mpl (1) parameter (14) python (1) serialization (36) spirit (8) thread (4) tuple (1) type_traits (1) typeof (21) xpressive (39) |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 |graph| graphviz_test: vc-7_1 layout_test: intel-win32-9_0 |mpl| size_t: gcc-4_0-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux msvc tutorial: gcc-2.95.3-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux vc-7_1 |python| 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| tricky_abstract_type_test: intel-win32-9_0 |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| test1: intel-win32-9_0 test1u: intel-win32-9_0 test2: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test2u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test3: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin intel-win32-9_0 test3u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test4: gcc-3.3.6-linux gcc-3_3-darwin test4u: gcc-3.3.6-linux gcc-3_3-darwin test5: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test5u: gcc-3.3.6-linux gcc-3_3-darwin test6: gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin test6u: gcc-3.3.6-linux gcc-3_3-darwin test7: intel-win32-9_0 test7u: intel-win32-9_0 test8: intel-win32-9_0 test8u: intel-win32-9_0 test9: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0 test9u: gcc-3.3.6-linux gcc-3_3-darwin intel-win32-9_0

1 0

Re: [boost] Interest in dimension/unit-checking library?
by Scott Schurr 14 Oct '05

14 Oct '05

I'm no where close to the expert that you guys are, so I'll quickly toss in my two cents and get out of your way. On 10/13/05 Matt Calabrese <rivorus(a)gmail.com> wrote: > > On 10/13/05, Deane Yang <deane_yang(a)yahoo.com> wrote: > > > > Mathematically, I think Andy is entirely correct in what he says above. > > Once you take the ratio of two measurements of the same dimension (or > > quantity), you end up with a pure number that really can't be > > distinguished from other ratios or pure numbers. > > > I tend to disagree here. A ratio of two lengths, for example, is in > fact a value in radians. Um, careful there. Suppose I'm measuring the height of a shrub at various points in time. If I take one of those measurements and divide it by a measurement taken at a different time, then I get a ratio that expresses the shrub's change in height in a unitless way - I get the same value whether I made my measurements in meters, inches, or furlongs. This is an example of a common case where dividing two lengths doesn't give radians - it's just a ratio. The dimension/unit-checking library should solve the problems that it has enough information to solve. When it runs out of information it should ask for help. Would it make sense to have something like a unitless_cast<radians>? Scott Schurr

6 5

[graph][1.33.1] STLport 5 compile problems.
by Rene Rivera 14 Oct '05

14 Oct '05

There seems to be a conflict between the Graph library and the new STLport... http://tinyurl.com/dk2fc [1] [1] http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/o… -- -- 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

2 4

[Boost-bugs] [ boost-Feature Requests-1326829 ] STLPort with NO_IOSTREAMS
by SourceForge.net 14 Oct '05

14 Oct '05

Feature Requests item #1326829, was opened at 2005-10-14 16:38 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1326829&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: NN (nn1234) Assigned to: Nobody/Anonymous (nobody) Summary: STLPort with NO_IOSTREAMS Initial Comment: Boost does specializations for streams even when _STLP_NO_IOSTREAMS defined. It would be nice to not specialize classes with streams when _STLP_NO_IOSTREAMS macro is defined. Thanx. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1326829&group_… ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

VC++ 7.1 build options lead to AV
by Ashok Thirumurthi 14 Oct '05

14 Oct '05

Dear Boost, The following call stack leads to an access violation when I link a VC 7.1 DLL to the release build of the boost signals 1_33_0 DLL. In comparison, there is no access violation when I link to the debug build of the same library. Similarly, when I add the signals source to my own release DLL, there is no access violation. I attempted to disable all compiler optimizations in msvc.jam as follows. However, after running bjam -a in signals\build and installing the output, the AV still occurs. # 8.0 deprecates some of the options if ! [ MATCH ^([67].*) : $(version) ] { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /O2 ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /O1 ; flags msvc.link.dll MANIFEST : "mt -manifest " ; flags msvc.link.dll OUTPUTRESOURCE : "-outputresource:" ; } else { # flags msvc.compile CFLAGS $(condition)/<optimization>speed : /Ogity /O2 /Gs ; # flags msvc.compile CFLAGS $(condition)/<optimization>space : /Ogisy /O1 /Gs ; } Note that I have a default installation of Visual Studio 2003. How can I alter the release build to avoid the access violation? More information: Access violation reading location 0x00000004 (*((k2).content)).__vfptr is 0x00000000 bool operator()(const any& k1, const any& k2) const { if (k1.type() == typeid(front_type)) return !(k2.type() == typeid(front_type)); if (k1.type() == typeid(back_type)) return false; > if (k2.type() == typeid(front_type)) return false; if (k2.type() == typeid(back_type)) return true; > Colorado.dll!boost::signals::detail::any_bridge_compare<std::less<int>,int>::operator()(const boost::any & k1={...}, const boost::any & k2={...}) Line 54 + 0xc C++ Colorado.dll!boost::detail::function::function_obj_invoker2<boost::signals::detail::any_bridge_compare<std::less<int>,int>,bool,boost::any,boost::any>::invoke(boost::detail::function::any_pointer function_obj_ptr={...}, boost::any a0={...}, boost::any a1={...}) Line 119 + 0x1b C++ boost_signals-vc71-mt-1_33.dll!010a2340() boost_signals-vc71-mt-1_33.dll!010a2c6a() boost_signals-vc71-mt-1_33.dll!010a42be() boost_signals-vc71-mt-1_33.dll!010a4bd0() boost_signals-vc71-mt-1_33.dll!010a4dfc() boost_signals-vc71-mt-1_33.dll!010a5933() Colorado.dll!boost::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >::signal0<bool,boost::last_value<bool>,int,std::less<int>,boost::function<bool __stdcall(void),std::allocator<void> > >(const boost::last_value<bool> & c={...}, const std::less<int> & comp={...}) Line 198 + 0x85 C++ ... Do these observations suggest how I might successfully handle this callback from the release boost DLL? Thanks in advance, - Ashok Thirumurthi

1 0

Re: [boost] [ANN] Phoenix-2 prerelease
by Eric Niebler 14 Oct '05

14 Oct '05

Joel de Guzman wrote: > Docs: http://tinyurl.com/77pz5 > In "Block Statement", (http://tinyurl.com/b25hr) you show how to use the comma operator to sequence statements. I see problems here, especially when calling a function that takes a predicate that isn't the last argument. For instance, how would you use Phoenix to create a filter_iterator? iterator begin, end; ... boost::make_filter_iterator(arg1 > 5, begin, end); // Oops! ---------------------------^ Isn't that comma going to be Phoenix's overloaded comma? -- Eric Niebler Boost Consulting www.boost-consulting.com

3 3

Rephrase "Broken Compiler Workarounds"?
by Daryle Walker 14 Oct '05

14 Oct '05

I was just looking at the phrase "Broken Compiler Workarounds" on a page about Boost on Wikipedia <http://en.wikipedia.org/wiki/Boost_library>. I realized that a naïve look makes it ambiguous whether the compiler is broken or the workarounds are broken. Maybe a hyphen could go between the first two words? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

4 3