- Boost - lists.boost.org

How should we deal with access to zero pointers?
by Asger Mangaard 21 Oct '05

21 Oct '05

When writing code that *could* access a zero pointer, should one do the following: 1. Nothing 2. assert 3. Exception. In that case which one? My guess would be 1 since an access violation exception will be thrown any way (on VC++ at least), but now I'm not sure? Regards, Asger Mangaard

3 2

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

21 Oct '05

Michael Hopkins wrote: > On 21/10/05 17:26, "Peter Dimov" <pdimov(a)mmltd.net> wrote: > >> SourceForge.net wrote: >> >>>> I am trying Boost 1.33 on Mac OS X 10.4.2 with XCode >>>> 2.1 and compiling the smart pointer test program. I >>>> get hundreds of "error: template with C linkage" errors >>>> within many of the gcc includes. This happens whether >>>> I am using gcc 3.3 or 4.0. >>>> >>>> More detail available if necessary - please contact me >>>> on michael.hopkins(a)hopkins-research.com. >> >> Yes, I think that we do need more detail, but first please make sure >> that you are compiling as C++ and not as C. :-) >> >> > Peter > > I can see why you would think I was doing that, but I¹m sharing a > project directory with all my C++ code and the compiler output > certainly looks like C++. I suspect that something within the Boost > headers is making the compiler Othink in C rather than C++¹. > > I have attached the smart pointer test program and the full compiler > output from XCode when I try to build using Apple GCC4.0 and Apple > GCC3.3. There is a lot of info here so I have zipped them. > > I completely cleaned the projects before I started the builds. I > thought that maybe some combination of the compiler settings is > causing the problem but the same issue occurs whether I use the > ODevelopment¹ or ODeployment¹ settings which are very different. > > Let me know if you need anything else. 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…

1 0

Alternative solution to intermediate results problem of expression templates.
by Korcan Hussein 21 Oct '05

21 Oct '05

Hi I'm not sure if this has already been explored or even in current use but I think I may have come up with an alternative solution to the type deduction of intermediate results from expression templates. Instead of using automatic type erasing technique, take the compile-time parse tree of an intermediate expression and create an exact runtime replica of the expression tree using recursive variant types (using Boost.Variant in C++). The creation of the expression tree can be completely automated. I have tried this myself with promising results. The only (minor) downside is in order to avoid redundant copies of operands the types of the operands must be given but not the structure of the compile-time expression tree itself. Leaf nodes of the recursive variant hold constant references to there elements. I've done quick profile of this against the traditional eager evaluation of overloaded operators and it still is more efficient but tree creation does cost in time slightly. If people are interested I can post code the code for this.

1 0

Math lib docs
by John Maddock 21 Oct '05

21 Oct '05

Hubert, Daryle, I'm trying to figure out how to integrate the docs for the few new additions to Boost.Math that come with the TR1 library into the existing documentation. The new docs use quickbook, and the options appear to be: 1) Leave the existing docs as they are, the minor problem with this is that my addition ends up with it's own library entry under doc/html/index.html, while the rest of you get left out of there as you do now :-( 2) Use quickbook to create a new front page for the Math lib, but otherwise leave the html as it is. The doc/html/index.html would now look right, but the existing html docs would be second-class citizens in the BoostBook generated TOC for the Math lib: they would get a main entry, but no sub-entries, and just a forwarding link to the existing html. 3) Convert the existing docs to quickbook: it's a bit tedious, but surprisingly easy to do, and once you get the hang of it, easier to maintain than html: no honestly it is, not having to quote "<>&" etc code snippets is worth the change alone IMO. I don't mind making the initial changeover, but thereafter you guys would have to be happy maintaining the quickbook source. The main advantages are a coherent look to the docs, automatic TOC, optional PDF generation and so on. There's the potential to integrate the docs for the new complex number inverse trig special functions, with the existing docs for the scalar versions as well, but I haven't looked into that yet. Thoughts? Thanks, John.

2 1

(Nuisance) Warnings
by David Abrahams 21 Oct '05

21 Oct '05

Warnings present a difficult conundrum for Boost. I wonder if there's any way we can come up with a coherent policy, so individual library developers don't have to think through all the issues individually and our users develop consistent expectations. Here's what I know: * Some warnings that are just a nuisance, especially for templated code. For example, I am getting a warning from vc-8 that the implicit assignment operator of a particular class template instantiation couldn't be generated. I expect the availability of implicit assignment in that case to depend on the template parameter. In this case, any class template that can take reference arguments that become members of the class is susceptible. * It's impolite to unconditionally disable warnings that people may count on in their own code. The above is a nuisance for me, but it might be crucial for someone developing ordinary classes. * Some popular compilers (GCC) don't have #pragmas that let us turn off warnings in particular regions of code. On those compilers, there is sometimes no workaround in code; suppressing the warning must be done on the compiler's command-line. We can do it in Boost.Build, but of course that won't help people who are using other build systems. And for those that _are_ using Boost.Build, suppressing warnings at that point can be just as impolite as doing it in code. * Even when in-code workarounds are possible, they're often ugly, and since the workarounds (e.g. #pragmas) can be different for every compiler, they really pile up. So, ideas, anyone? -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 2

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

21 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-21T14:27:09Z 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… 28 failures in 4 libraries: parameter (2) python (5) range (3) serialization (18) |parameter| tutorial: borland-5_6_4 gcc-2.95.3-linux |python| builtin_converters: mingw-3_4_2 try: gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-4.0.1-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

1 0

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

21 Oct '05

Boost regression test failures ------------------------------ Report time: 2005-10-21T05:00:17Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 410 failures in 12 libraries: concept_check (13) 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 |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

[Boost-bugs] [ boost-Support Requests-1334003 ] 100s of 'template with C linkage' errors
by SourceForge.net 21 Oct '05

21 Oct '05

Support Requests item #1334003, was opened at 2005-10-21 03:27 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=1334003&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: 100s of 'template with C linkage' errors Initial Comment: Hi I am trying Boost 1.33 on Mac OS X 10.4.2 with XCode 2.1 and compiling the smart pointer test program. I get hundreds of "error: template with C linkage" errors within many of the gcc includes. This happens whether I am using gcc 3.3 or 4.0. More detail available if necessary - please contact me on michael.hopkins(a)hopkins-research.com. Many thanks Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1334003&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

2 1

Sun Studio 10 compiler version in sunpro_cc.hpp
by P Holdaway 21 Oct '05

21 Oct '05

When using... /opt/studio10/SUNWspro/bin/CC -V CC: Sun C++ 5.7 Patch 117830-04 2005/09/14 On uname -a SunOS solaris 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Fire-V250 The compiler works much better when I effectively back out the last patch to this file. Changing... if (__SUNPRO_CC < 0x570) to... if (__SUNPRO_CC <= 0x570) *** boost/config/compiler/sunpro_cc.hpp.orig Tue Mar 22 02:55:03 2005 --- boost/config/compiler/sunpro_cc.hpp Thu Oct 20 18:46:18 2005 *************** *** 57,63 **** # define BOOST_NO_INTEGRAL_INT64_T # endif ! # if (__SUNPRO_CC < 0x570) # define BOOST_NO_TEMPLATE_TEMPLATES // see http://lists.boost.org/MailArchives/boost/msg47184.php // and http://lists.boost.org/MailArchives/boost/msg47220.php --- 57,63 ---- # define BOOST_NO_INTEGRAL_INT64_T # endif ! # if (__SUNPRO_CC <= 0x570) # define BOOST_NO_TEMPLATE_TEMPLATES // see http://lists.boost.org/MailArchives/boost/msg47184.php // and http://lists.boost.org/MailArchives/boost/msg47220.php

2 1

[patch] using boost/version.hpp
by Christophe Prud'homme 21 Oct '05

21 Oct '05

Dear Boosters, I am trying to keep some backward compatibility (for some while) for the boost libraries we use in our codes (ublas for example), and I find that the addition below to boost/version.hpp helps a lot with readability in the code instead of using // BOOST_VERSION % 100 is the sub-minor version // BOOST_VERSION / 100 % 1000 is the minor version // BOOST_VERSION / 100000 is the major version ------------------- define BOOST_VERSION_MAJOR 1 #define BOOST_VERSION_MINOR 33 #define BOOST_VERSION_SUBMINOR 1 #define BOOST_MAKE_VERSION( a,b,c ) ((a)*100000+(b)*100+(c)) #define BOOST_VERSION \ BOOST_MAKE_VERSION(BOOST_VERSION_MAJOR,BOOST_VERSION_MINOR,BOOST_VERSION_SUBMINOR) #define BOOST_IS_VERSION(a,b,c) ( BOOST_VERSION >= BOOST_MAKE_VERSION(a,b,c) ) ---------------------------- In order to test the current version of boost: #if BOOST_IS_VERSION(1,33,0) ... write the code according to the API >= 1.33.0 #else ... write the code according to the API < 1.33.0 #endif would that be of interest ? Best regards C.

3 3