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

[mpl] integral_c bool partial specialization
by Matt Calabrese 19 Jul '05

19 Jul '05

The bool partial specialization of ::boost::mpl::integral_c currently does not appear to contain a value_type type member meaning it does not fully conform to the Integral Constant pure abstraction specified in documentation.

2 1

[tokenizer] Type requirements
by Nikolay Mladenov 18 Jul '05

18 Jul '05

Hi All, What are the requirements on the Type template parameter of boost::tokenizer. I could not find this in the documentation. I want to pass type similar to std::pair < std::string::const_iterator, std::string::const_iterator > . But it seems that the type should have operator += and/(or?) assign member. Is that correct? Is there any other customization mechanism here? Thanks Nikolay

1 0

multi_array 64-bit patch
by Thomas Klimpel 18 Jul '05

18 Jul '05

Hello, The Boost Multi_Array library produces some 64-bit related warnings when used with Visual C++.NET. It seems to me that these warnings are valid and correspond to real 64-bit problems. To get rid of these annoying warnings, I have fixed two minor inconsistencies in multi_array/iterator.hpp and multi_array/multi_array_ref.hpp, but that was not enough. I also had to change the definition of boost::detail::multi_array::index in multi_array/types.hpp from "typedef int index;" to "typedef std::ptrdiff_t index;". There might be better solutions, but it was the best I could think of, because std::ptrdiff_t is a signed type and will adapt to a 64-bit environment. Index: multi_array/iterator.hpp =================================================================== --- multi_array/iterator.hpp (Revision 1040) +++ multi_array/iterator.hpp (Arbeitskopie) @@ -98,7 +98,7 @@ array_iterator() {} - array_iterator(int idx, TPtr base, const size_type* extents, + array_iterator(index idx, TPtr base, const size_type* extents, const index* strides, const index* index_base) : idx_(idx), base_(base), extents_(extents), Index: multi_array/types.hpp =================================================================== --- multi_array/types.hpp (Revision 1040) +++ multi_array/types.hpp (Arbeitskopie) @@ -26,7 +26,7 @@ // needed typedefs typedef std::size_t size_type; -typedef int index; +typedef std::ptrdiff_t index; } // namespace multi_array } // namespace detail Index: multi_array/multi_array_ref.hpp =================================================================== --- multi_array/multi_array_ref.hpp (Revision 1040) +++ multi_array/multi_array_ref.hpp (Arbeitskopie) @@ -389,7 +389,7 @@ // Calculate the array size num_elements_ = std::accumulate(extent_list_.begin(),extent_list_.end(), - 1,std::multiplies<index>()); + size_type(1),std::multiplies<size_type>()); #if 0 assert(num_elements_ != 0); #endif

2 1

[Preprocessor] Workaround for CW8.3
by David Abrahams 18 Jul '05

18 Jul '05

BOOST_PP_SEQ_ENUM is failing for me when invoked from another macro; When the argument is (A0) I get BOOST_PP_SEQ_ENUM_2 and when the argument is (A0)(A1) I get BOOST_PP_SEQ_ENUM_4 I think what happens is that CW "sees through" the outer set of parens in # define BOOST_PP_SEQ_ENUM(seq) BOOST_PP_CAT(BOOST_PP_SEQ_ENUM_, BOOST_PP_SEQ_SIZE(seq)) seq and pastes seq to itself, yielding a length of 4 instead of 2. Here's a workaround: # define BOOST_PP_SEQ_ENUM_I(size,seq) BOOST_PP_CAT(BOOST_PP_SEQ_ENUM_, size) seq # define BOOST_PP_SEQ_ENUM(seq) BOOST_PARAMETER_SEQ_ENUM_I(BOOST_PP_SEQ_SIZE(seq), seq) I hope this is useful. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

[1.33.0] Inspection report
by Douglas Gregor 18 Jul '05

18 Jul '05

The inspection report shows that we have a bunch of little fixes to make before we release. Please check it out and fix whatever you can: http://www.boost.org/regression-logs/inspection_report.html Doug

8 14

some ptr_container issues
by Ross Boylan 18 Jul '05

18 Jul '05

I'm using the cvs version (as of a couple of days ago) of the ptr_container library with a regular 1.32 boost. Should transfer operations between dissimilar containers (e.g., ptr_vector and ptr_list, assuming both have the same underlying type) work? They don't seem to. I can't quite tell from the docs (which define these abstractly, e.g., for ptr_sequence) whether this should work or not. Previous versions of the docs made it explicit that the operations were templated on the type of the second container. Second, the definition of transfer does not say where the elements are to be inserted (i.e., whether they go before the "before" iterator, or whether the "before" iterator will end up before the inserted elements). While it's not hard to guess right with some knowledge of how the standard works (and even how other ptr_container functions work), it would be nice to be explicit. Third, I didn't see any explicit discussion of circumstances that invalidate iterators. Again, it's pretty easy to guess this is the same as the corresponding standard classes, but it's probably worth saying so. Finally, the discussion of exception classes does not describe the circumstances under which the exceptions are thrown. Some functions do discuss their exceptions, but I'm not sure if they all do. I was surprised that at throws bad_ptr_container_operation; I would have expected bad_index (this behavior *is* documented--I'm just saying it seems odd). Thanks for your work on these utilities. -- Ross Boylan wk: (415) 502-4031 530 Parnassus Avenue (Library) rm 115-4 ross(a)biostat.ucsf.edu Dept of Epidemiology and Biostatistics fax: (415) 476-9856 University of California, San Francisco San Francisco, CA 94143-0840 hm: (415) 550-1062

2 3

Re: [boost] Macros at namespace scope: trailing semicolon?
by Dave Gomboc 18 Jul '05

18 Jul '05

You were asking another, but... > 1) Do you think that the LOG() macro should contain a trailing > semicolon? The macro itself should, yes, so the user need not type one. > 2) I'm pretty sure you'll say #1, but which of the following examples > do you prefer? > > int foo() > { > LOG("NO SEMICOLON HERE?") // 1 > stuff(); > > LOG("OR does this seem better?"); // 2 > more_stuff(); > } #1. If someone did #2, yielding an extra, empty statement, it's not a tragedy, however (unless my compiler warned about such empty statements -- in which case I would delete the extraneous semicolon.) There's undoubtedly some compiler that boost supports that will do this, so best not to have the extra one there in the first place, I think. > 3) Do you see harm if the macro does not contain the trailing > semicolon? If so, what harm is it? Specifically, how does usage > #2 above re-enforce bad understanding of macros? (Or am I > misconstruing the nature of your objection?) It's logically inconsistent for the macro to not to perform its entire job. If that job is to "expand into an expression", certainly, it shouldn't generate a semicolon. If that job is to "expand into a statement", then just as certainly, it should. But its job ought not to be to "expand into a statement except for the trailing semicolon": that would be absurd. > 4) What is the important degree of indirection that I would be missing > by talking about the usage of the LOG macro as a call to the log > function? I understand that I could call it "a macro that expands > to a call to the log function" but I don't think that anyone would > be more enlightened by that. Other than being more detailed about > what's really happening, it's not clear to me what important > mistake is being made that bothers you. If our coding convention > states that macros are uppercase, then we already know it's a > macro, so simply repeating that is unnecessary, IMHO. Referring to it as the log function is clearly wrong. The listener might doubt your understanding, even if you knew perfectly well that it was indeed a macro that expanded to a function call. I see no disadvantage in referring to it as the LOG macro. Dave

1 0

Boost regression notification (2005-07-18)
by Douglas Gregor 18 Jul '05

18 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-07-18T15:30: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. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 229 failures in 12 libraries: filesystem (2) io (1) multi_index (1) parameter (7) program_options (5) python (53) random (2) serialization (139) spirit (1) test (6) thread (2) wave (10) |filesystem| operations_test_dll: borland-5_6_4 path_test_dll: borland-5_6_4 |io| ios_state_unit_test: intel-win32-8_1 |multi_index| test_special_set_ops: vc-8_0 |parameter| basics: gcc-3_4_3-sunos vc-8_0 macros: gcc-3_4_3-sunos vc-8_0 sfinae: cw-8_3 gcc-3_4_3-sunos vc-8_0 |program_options| cmdline_test_dll: mingw-3_4_2 positional_options_test_dll: mingw-3_4_2 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_3-darwin |python| andreas_beyer: intel-win32-8_1 args: intel-win32-8_1 auto_ptr: intel-win32-8_1 back_reference: intel-win32-8_1 ben_scott1: intel-win32-8_1 bienstman1: intel-win32-8_1 bienstman2: intel-win32-8_1 bienstman3: intel-win32-8_1 builtin_converters: intel-win32-8_1 callbacks: intel-win32-8_1 const_argument: intel-win32-8_1 crossmod_exception: intel-win32-8_1 data_members: intel-win32-8_1 defaults: intel-win32-8_1 dict: intel-win32-8_1 docstring: intel-win32-8_1 enum: intel-win32-8_1 exception_translator: intel-win32-8_1 extract: intel-win32-8_1 implicit: intel-win32-8_1 injected: intel-win32-8_1 iterator: intel-win32-8_1 keywords: intel-win32-8_1 list: intel-win32-8_1 long: intel-win32-8_1 map_indexing_suite: intel-win32-8_1 minimal: intel-win32-8_1 multi_arg_constructor: intel-win32-8_1 nested: intel-win32-8_1 numpy: intel-win32-8_1 object: intel-win32-8_1 opaque: intel-win32-8_1 operators: intel-win32-8_1 pearu1: intel-win32-8_1 pickle1: intel-win32-8_1 pickle2: intel-win32-8_1 pickle3: intel-win32-8_1 pickle4: intel-win32-8_1 pointer_vector: intel-win32-8_1 polymorphism: intel-win32-8_1 polymorphism2: intel-win32-8_1 properties: intel-win32-8_1 raw_ctor: intel-win32-8_1 return_arg: intel-win32-8_1 shared_ptr: intel-win32-8_1 slice: intel-win32-8_1 staticmethod: intel-win32-8_1 str: intel-win32-8_1 test_pointer_adoption: intel-win32-8_1 try: intel-win32-8_1 tuple: intel-win32-8_1 vector_indexing_suite: intel-win32-8_1 virtual_functions: intel-win32-8_1 |random| random_test: intel-win32-8_1 intel-win32-8_1 |serialization| test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 vc-7_1 vc-7_1 vc-8_0 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-7_1 vc-7_1 vc-8_0 test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: vc-6_5 vc-6_5-stlport vc-7_0 test_demo: intel-win32-8_1 test_demo_dll: cw-9_4 cw-9_4 test_demo_exception: intel-win32-8_1 test_demo_exception_dll: cw-9_4 cw-9_4 test_demo_fast_archive_dll: vc-6_5 test_demo_pimpl_dll: vc-6_5 vc-7_0 test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-7_1 vc-7_1 vc-7_1 vc-8_0 vc-8_0 vc-8_0 test_demo_portable_archive_dll: borland-5_6_4 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin intel-win32-8_1 test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin vc-6_5 vc-7_0 test_demo_xml_load: intel-win32-8_1 test_demo_xml_save: intel-win32-8_1 test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: vc-6_5 vc-7_0 test_map_text_archive_dll: vc-6_5 vc-7_0 test_map_text_warchive_dll: vc-6_5 vc-7_0 test_mi_xml_archive_dll: vc-8_0 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin vc-6_5 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_registered_xml_archive: vc-8_0 |spirit| owi_mt_tests: gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_mutex: vc-7_1 test_thread: vc-6_5 |wave| test_re2c_lexer: vc-8_0 vc-8_0 test_slex_lexer: vc-8_0 vc-8_0 testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux vc-8_0 vc-8_0

1 0

[inspect] Boost Inspection Report *Run Date:* 14:43:58 UTC, Monday 18 July 2005
by Rene Rivera 18 Jul '05

18 Jul '05

-- -- 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 Boost Inspection Report *Run Date:* 14:43:58 UTC, Monday 18 July 2005 An inspection program <http://www.boost.org/tools/inspect/index.html> checks each file in the current Boost CVS for various problems, generating this web page as output. Problems detected include tabs in files, missing copyrights, broken URL's, and similar misdemeanors. Totals 10429 files scanned 821 directories scanned 180 problems reported problem counts: 4 files with invalid line endings 0 bookmarks with invalid characters 0 invalid urls 104 broken links 38 unlinked files 23 file names too long 4 files with tabs 7 violations of the Boost min/max guidelines Summary *Library* *Problems* algorithm <#algorithm> 1 boost-root <#boost-root> 3 build <#build> 6 date_time <#date_time> 5 iostreams <#iostreams> 86 iterator <#iterator> 7 libs <#libs> 3 mpl <#mpl> 2 numeric <#numeric> 3 program_options <#program_options> 1 python <#python> 11 quickbook <#quickbook> 8 regex <#regex> 1 regression <#regression> 32 serialization <#serialization> 2 test <#test> 7 type_traits <#type_traits> 2 Details algorithm libs/algorithm/string/doc/external_concepts.html: unlinked file boost-root index.htm: broken link: doc/html/date_time/date_time_io.html, broken link: doc/html/date_time/details.html#date_time.changes, broken link: doc/html/date_time/local_time.html build tools/build/v2/example/libraries/util/foo/include/lib1.h: file's directory depth will exceed 8 levels if placed on a CD tools/build/v2/index.html: broken link: ../../../doc/html/bbv2.html, broken link: ../../../doc/html/bbv2/installation.html, broken link: doc/userman.pdf tools/build/v2/test/test_system.html: unlinked file date_time boost/date_time/date_parsing.hpp: violation of Boost min/max guidelines on line 80, violation of Boost min/max guidelines on line 81 boost/date_time/period.hpp: violation of Boost min/max guidelines on line 339, violation of Boost min/max guidelines on line 340 libs/date_time/xmldoc/date_time_docs_howto.html: unlinked file iostreams libs/iostreams/doc/acknowledgments.html: unlinked file libs/iostreams/doc/faq.html: unlinked file libs/iostreams/doc/functions/reverse.html: broken link: ../../../../boost/iostreams/reverse.hpp, unlinked file libs/iostreams/doc/guide/adapters.html: broken link: ../../../../boost/iostreams/adapt.hpp, broken link: ../../../../boost/iostreams/device/container_device.hpp, broken link: ../functions/adapt.html libs/iostreams/doc/guide/code_conversion.html: broken link: ../../../../boost/iostreams/converting_stream.hpp, broken link: ../../../../boost/iostreams/converting_streambuf.hpp, broken link: ../classes/converting_stream.html, broken link: ../classes/converting_streambuf.html libs/iostreams/doc/guide/compression.html: broken link: ../../src/bzip2, broken link: ../../src/zlib libs/iostreams/doc/guide/concepts.html: broken link: ../../../boost/iostreams/concepts.hpp, broken link: classes/device.html, broken link: classes/device.html#sink, broken link: classes/device.html#source, broken link: classes/device.html#synopsis, broken link: classes/filter.html, broken link: classes/filter.html#multichar_filter, broken link: classes/filter.html#synopsis, broken link: concepts/bidirectional_device.html, broken link: concepts/bidirectional_filter.html, broken link: concepts/closable.html, broken link: concepts/device.html, broken link: concepts/direct.html, broken link: concepts/filter.html, broken link: concepts/input_filter.html, broken link: concepts/localizable.html, broken link: concepts/multi_character.html, broken link: concepts/output_filter.html, broken link: concepts/peekable.html, broken link: concepts/seekable_device.html, broken link: concepts/seekable_filter.html, broken link: concepts/sink.html, broken link: concepts/source.html libs/iostreams/doc/guide/filtering_streams.html: broken link: graphics/bidirectional_chain.gif, broken link: graphics/input_chain.gif, broken link: graphics/output_chain.gif, broken link: graphics/seekable_chain.gif libs/iostreams/doc/guide/generic_streams.html: broken link: ../modes.html libs/iostreams/doc/guide/guide.html: unlinked file libs/iostreams/doc/guide/modes.html: broken link: ../compression.html, broken link: graphics/important_modes.gif, broken link: graphics/key_bidirectional_seq.gif, broken link: graphics/key_important.gif, broken link: graphics/key_input_seq.gif, broken link: graphics/key_output_seq.gif, broken link: graphics/key_read_head.gif, broken link: graphics/key_read_write_head.gif, broken link: graphics/key_write_head.gif, broken link: graphics/modes.gif libs/iostreams/doc/quick_reference.html: broken link: ../bibliography.html#deutsch3, broken link: ../guide/code_conversion.html, broken link: concepts/filters.html, broken link: concepts/sinks.html, broken link: source.html, invalid (cr only) line-ending, unlinked file libs/iostreams/doc/rationale.html: broken link: functions/adapt.html, unlinked file libs/iostreams/doc/reference.html: unlinked file libs/iostreams/doc/tutorial/container_sink.html: broken link: ../non_blocking.html libs/iostreams/doc/tutorial/container_source.html: broken link: ../non_blocking.html libs/iostreams/doc/tutorial/writing_filters.html: broken link: ../classes/symmetric.hpp libs/iostreams/test/putback_test.hpp: invalid (cr only) line-ending iterator libs/iterator/doc/filter_iterator_ref.html: unlinked file libs/iterator/doc/indirect_iterator_ref.html: unlinked file libs/iterator/doc/issues.html: unlinked file libs/iterator/doc/iter-issue-list.html: unlinked file libs/iterator/doc/iterator_adaptor_ref.html: unlinked file libs/iterator/doc/make_filter_iterator.html: unlinked file libs/iterator/doc/ref_problem.html: unlinked file libs libs/libraries.htm: broken link: ../doc/boost.docbook, broken link: ../doc/boost.fo, invalid (cr only) line-ending mpl libs/mpl/doc/src/refmanual/Data.Integral.rst: filename contains more than one dot character ('.') libs/mpl/doc/src/refmanual/ExtensibleAssociativeSequence.rst: filename > 31 chars numeric boost/numeric/conversion/detail/old_numeric_cast.hpp: violation of Boost min/max guidelines on line 159, violation of Boost min/max guidelines on line 192 libs/numeric/conversion/doc/converter_policies.html: invalid (cr only) line-ending program_options boost/program_options/positional_options.hpp: violation of Boost min/max guidelines on line 43 python boost/python/object/pointer_holder.hpp: tabs in file libs/python/doc/new-conversions.html: unlinked file libs/python/doc/tutorial/doc/html/python/embedding.html: broken link: ../object.html libs/python/doc/v2/bibliography.html: unlinked file libs/python/doc/v2/errors.html: broken link: ../../../../doc/html/functionN.html libs/python/doc/v2/from_python.html: unlinked file libs/python/doc/v2/header.html: unlinked file libs/python/doc/v2/overview.html: unlinked file libs/python/doc/v2/rationale.html: unlinked file libs/python/pyste/tests/inherit3.h: tabs in file libs/python/test/docstring.py: tabs in file quickbook tools/quickbook/detail/quickbook.cpp: tabs in file tools/quickbook/doc/html/index.html: broken link: libraries.html tools/quickbook/doc/html/quickbook/docinfo.html: broken link: ../libraries.html tools/quickbook/doc/html/quickbook/highlight.html: broken link: ../libraries.html tools/quickbook/doc/html/quickbook/pyhighlight.html: broken link: ../libraries.html tools/quickbook/doc/html/quickbook/quickbook.html: broken link: ../libraries.html tools/quickbook/doc/html/quickbook/ref.html: broken link: ../libraries.html tools/quickbook/doc/html/quickbook/syntax.html: broken link: ../libraries.html regex libs/regex/performance/input.html: unlinked file regression tools/regression/test/compile-fail~fail.cpp: nonportable path tools/regression/test/compile-fail~pass.cpp: nonportable path tools/regression/test/compile~fail.cpp: nonportable path tools/regression/test/compile~pass.cpp: nonportable path tools/regression/test/compile~warn.cpp: nonportable path tools/regression/test/run-fail~compile-fail.cpp: nonportable path tools/regression/test/run-fail~fail-warn.cpp: nonportable path tools/regression/test/run-fail~fail.cpp: nonportable path tools/regression/test/run-fail~pass.cpp: nonportable path tools/regression/test/run-fail~warn.cpp: nonportable path tools/regression/test/run~compile-fail.cpp: nonportable path tools/regression/test/run~fail-note.cpp: nonportable path tools/regression/test/run~fail-warn.cpp: nonportable path tools/regression/test/run~fail.cpp: nonportable path tools/regression/test/run~note.cpp: nonportable path tools/regression/test/run~pass.cpp: nonportable path tools/regression/test/run~warn-note.cpp: nonportable path tools/regression/test/run~warn.cpp: nonportable path tools/regression/xsl_reports/runner/instructions.html: unlinked file tools/regression/xsl_reports/xsl/html/issues_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/library_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/library_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/make_tinyurl.html: unlinked file tools/regression/xsl_reports/xsl/html/summary_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/summary_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/expected_results_2_new_format.xsl: filename > 31 chars tools/regression/xsl_reports/xsl/v2/html/issues_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/library_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/library_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/make_tinyurl.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_user_legend.html: unlinked file serialization libs/serialization/doc/serialization.html: broken link: ../../../boost/serialization/shared_count.hpp libs/serialization/vc7ide/test_reset_object_address.vcproj: filename > 31 chars test libs/test/doc/components/test_exec_monitor/compilation.html: broken link: ../../../src/supplied_log_formatters.cpp, broken link: ../../../src/unit_test_result.cpp libs/test/doc/components/utf/compilation.html: broken link: ../../../src/supplied_log_formatters.cpp, broken link: ../../../src/unit_test_result.cpp libs/test/doc/components/utf/components/test_case/boost_function_tc.html: broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp libs/test/doc/components/utf/components/test_case/param_boost_function_tc.html: broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp libs/test/doc/tests/unit_test_suite_ex_test.html: broken link: ../../test/unit_test_suite_ex_test.cpp type_traits libs/type_traits/cxx_type_traits.htm: broken link: ../../doc/html/boost_typetraits/background.html, unlinked file

1 0

Defining compilers suggestion
by Edward Diener 18 Jul '05

18 Jul '05

It would be much easier, and less confusing, when looking at compiler workarounds in Boost code if their were defines for various compilers/versions in a configuratiion header file such as: #define BOOST_COMPILER_SOME_COMPILER_LOWER (PREPROCESSOR_TAG >= nnnn) #define BOOST_COMPILER_SOME_COMPILER_UPPER (PREPROCESSOR_TAG <= nnnn) #define BOOST_COMPILER_SOME_COMPILER (BOOST_COMPILER_SOME_COMPILER_LOWER && BOOST_COMPILER_SOME_COMPILER_UPPER) where SOME_COMPILER might be VC71,GCC40 etc. Then in code one could see: #if defined(BOOST_COMPILER_VC71) etc. rather than the less understandable #if defined(MSC_VER == nnnn) etc. I would just like to see more readability in the Boost code regarding compiler workarounds. I am also aware their is a workaround macro, but even that deals in compiler preprocessor tags rather than a more readable compiler version. I am aware that many workarounds have to deal with versions before or after a certain version number but even that can be made more readable by macros which tell one the actual compiler which is involved. I realize I am just a reader of Boost code and not a Boost developer but I think this suggestion would make for a little more readable code in its own small way.

11 61