May 2007 - Boost - lists.preview.boost.org

Trac milestones
by Vladimir Prus 17 May '07

17 May '07

Is it possible for somebody with enough karma to create "1.34.1" milestone in trac, so that bugs can be assigned to that milestone? - Volodya

4 4

[algorithm][string] example fails to compile with bjam.v2
by JD 17 May '07

17 May '07

Hi, bjam on 1_34_0 and on HEAD fails to compile algorithm/string/example: *********************************************************************** bjam --toolset=msvc-8.0 warning: Graph library does not contain optional GraphML reader. note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note: directories containing the Expat headers and libraries, respectively. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). Jamfile:10: in modules.load rule subproject unknown in module Jamfile</G:/Program Files/boost-cvs/boost/libs /algorithm/string/example>. G:/Program Files/boost-cvs/boost/tools/build/v2/build\project.jam:312: in load-j amfile G:/Program Files/boost-cvs/boost/tools/build/v2/build\project.jam:68: in load G:/Program Files/boost-cvs/boost/tools/build/v2/build\project.jam:170: in projec t.find G:/Program Files/boost-cvs/boost/tools/build/v2\build-system.jam:237: in load G:\Program Files\boost-cvs\boost\tools\build\v2/kernel\modules.jam:261: in impor t G:\Program Files\boost-cvs\boost\tools\build\v2/kernel/bootstrap.jam:132: in boo st-build G:\Program Files\boost-cvs\boost\boost-build.jam:9: in module scope *********************************************************************** Seems that the jamfile has not been updated for the new build system. I'm no expert in bjam and I don't find the documentation very helpful but the Jamfile attached can at least compile most of the example (apart regex_example). Thanks. JD # Boost string_algo library examples Jamfile --------------------------------- # # Copyright Pavol Droba 2002-2003. Use, modification and # distribution is subject to the Boost Software License, Version # 1.0. (See accompanying file LICENSE_1_0.txt or copy at # http://www.boost.org/LICENSE_1_0.txt) # # See http://www.boost.org for updates, documentation, and revision history. exe conv_example : conv_example.cpp : <include>$(BOOST_ROOT) : ; exe predicate_example : predicate_example.cpp : <include>$(BOOST_ROOT) : ; exe find_example : find_example.cpp : <include>$(BOOST_ROOT) : ; exe replace_example : replace_example.cpp : <include>$(BOOST_ROOT) : ; exe rle_example : rle_example.cpp : <include>$(BOOST_ROOT) : ; exe trim_example : trim_example.cpp : <include>$(BOOST_ROOT) : ; exe regex_example : regex_example.cpp : <include>$(BOOST_ROOT) : ; exe split_example : split_example.cpp : <include>$(BOOST_ROOT) : ;

3 2

bjam FAQ
by Michael Walter 17 May '07

17 May '07

Hi, I've stumbled on that "Duplicate name of actual target" error; unfortunately the FAQ doesn't seem to solve my problem, since I'm trying to compile two different files which happen to have the same basename, i.e. something like this: lib foo : bar/test.cpp baz/test.cpp ; What's the proper way to handle this situation, except for manually specifying the object file name? Regards, Michael

5 4

[iostreams] Entire iostreams library outdated in 1.34.0?
by Kim Barrett 17 May '07

17 May '07

Following up on a discussion started on the boost-users list, under the same subject. It seems that a significant number of changes were made to the boost.iostreams library on the RC_1_33_0 branch, but never merged into the trunk. There are also a few changes on the RC_1_34_0 branch that have not been merged to into the trunk. There has also been some work on the trunk, some of which is on one of those branches, a few cases of merges between one of those branches and the trunk, and I found at least one case of apparent merging with code rearrangement or other changes (at least, diff seemed to not match up the (similar by eye) changes). So basically there is a bit of a mess in the iostreams library. I'm volunteering to help clean it up. I'm planning to put together a patch to the trunk, and another patch to the RC_1_34_0 branch, such that * changes that are presently only on the RC_1_33_0 or RC_1_34_0 branch are merged to trunk * changes that are presently only on the RC_1_33_0 branch are merged to the RC_1_34_0 branch. A preliminary skim of differences doesn't look too bad; hopefully I won't find anything too icky. Some issues / questions: * I can test these changes against a couple of versions of gcc. I can't test against anything else. So I'll need help with that. * Somebody else should probably review the patches. * I don't have commit privilages, so someone else will need to take care of that step. * Thomas would of course need to approve any changes to the RC_1_34_0 branch. The library including the changes on the RC_1_33_0 branch tested as part of the 1.33.x series of releases, but testing with those changes stopped once testing resources were redirected away from that series. So there is some risk that some of these changes might prove incompatible with other parts of the 1.34.0 release. From a quick skim, that doesn't look to likely, but it is a risk. * Obviously 1.34.0 has gone out. So any changes on the RC_1_34_0 branch would only be picked up by a 1.34.1 release.

3 5

Re: [boost] "beyond graphs"
by Jeremy Siek 16 May '07

16 May '07

Hi Gordon, On May 14, 2007, at 11:59 PM, boost-request(a)lists.boost.org wrote: > From: Gordon Woodhull <gordon(a)woodhull.com> > Date: May 14, 2007 11:45:23 PM MDT > To: boost(a)lists.boost.org > Subject: [boost] "beyond graphs" > Reply-To: boost(a)lists.boost.org > > > Hullo fellow Boosters, > > I am writing especially to those of you in Aspen, but also to > anyone out there who is interested in, or who has already > implemented, any kind of "meta" graph (network). I would like to > create or contribute to some Boost libraries for graphlike > structures / "metagraphs" / higher order graphs / whatchamacallits. > > Below I describe some ideas simplistically/vaguely, both for lack > of time and to try to grab the interest of people who have thought > about these things but perhaps not in quite the same way. > > So far I have thought of three general types of graphs which are > beyond the scope of graph libraries I know about: > - Graphs in metadata, i.e. graphs of C++ types. This seems to be > pretty easy to implement using MPL and I did this a couple of years > ago, though poorly. I.e. it's easy to create a BGL-like interface > with angle brackets instead of parentheses. :-) > - Graphlike structures which are not graphs. Actually any objects > which point to other objects form a graph of sorts; what we know as > "graph" happens to be the special case where an edge points to two > nodes and nodes point to a bunch of edges. What if there are more > types than just Node and Edge, or they don't look quite like that? > This is something like a Fusion for heterogeneous/polymorphic graphs. > - (Here is my root problem.) Graphs that refer to other graphs, > such as subgraphs, graphs at different layers of detail (where a > node/edge at one level corresponds to a subgraph at another level), > constraints on graphs... > I have maybe mostly figured out a system for the last, which relies > on the other two. Any of the three might be generally useful; I > really need the last because it's prohibitively difficult and/or > inefficient to maintain correspondences between graphs, and all of > my dynamic graph drawing problems keep spawning more corresponding > graphs! All very interesting stuff! On the graphs in metadata/metaprogramming... I'm about to embark on a project to enable the use of normal run-time language features during compile time. Perhaps ultimately this would mean we could use the BGL as-is to manipulate type information at compile time. Of course, this won't be achieved for some years, so looking at what can be done in current C++ is also very interesting. > Disclaimer: because I'm interested in dynamic (changing) graphs, > I'm looking at the problem as a bunch of node and edge objects > pointing to each other, and using intrusive containers for > efficiency/locality of reference. But I'd like to generalize > wherever possible. > > Anyone who is here in Aspen who's interested in these ideas, please > seek me out. Anyone else, please write me. I think I have some > good ideas about how to proceed, and I will write up more specific > descriptions, but first I would like to know what of this space has > already been explored, additional requirements from similar > applications, etc. > My impression is that, with the reuse of MPL, Fusion, BGL, STL, and > intrusive containers, none of this would require a lot of code, but > there is a LOT to be designed and abstracted. I see it as at least > three libraries, each depending on the last in the order above. Wish I was still in Aspen to talk with you more about this! Cheers, Jeremy ______________________________________ Jeremy Siek <jeremy.siek(a)colorado.edu> http://www.cs.colorado.edu/~siek/ Visiting Assistant Professor Department of Computer Science University of Colorado at Boulder

1 0

[lexical_cast] doc update
by Alexander Nasonov 16 May '07

16 May '07

I'm going to commit to HEAD two new sections 'Frequently Asked Questions' and 'References' and also update 'Changes' section. Any objections, corrections etc? New documentation is here http://194.6.223.221/~nasonov/lexical_cast.htm Frequently Asked Questions Q: Why lexical_cast<int8_t>("127") throws bad_lexical_cast? A: The type int8_t is a typedef to char or signed char. Lexical conversion to these types is simply reading a byte from source but since the source has more than one byte, the exception is thrown. Please use other integer types such as int or short int. If bounds check is important, you can also call numeric_cast: numeric_cast<int8_t>(lexical_cast<int>("127")); Q: The implementation always resets the ios_base::skipws flag of an underlying stream object. It breaks my operator>> that works only in presence of this flag. Can you remove code that resets the flag? A: May be in a future version. The is no requirement in [N1973] to reset the flag but remember that [N1973] is not yet accepted by the commitee. By the way, it's a greate opportunity to make your operator>> conform to the standard. Read a good C++ book, study std::sentry and ios_state_saver. References * [N1973] Kevlin Henney, Beman Dawes, Lexical Conversion Library * Proposal for TR2, N1973. * [Tuning] Alexander Nasonov, Fine Tuning for lexical_cast, * Overload #74, August 2006. Changes August, October 2006: * Better performance for many combinations of Source and Target * types. Refer to [Tuning] for more details. -- Alexander Nasonov http://nasonov.blogspot.com

5 5

Boost Logging library - first draft
by JD 16 May '07

16 May '07

Hello, So here is the question: "Is there any interest in a logging library for boost?" John Torjo did not answer my mail, beside I looked at pantheios. it seems a little bit complex... My idea is that a logging library should be _simple_ to use. Here is a small example: // snippet on #include <fstream> #include <boost/logging.hpp> int main(int argc, char **argv) { BOOST_LOG_INIT(("[" >> boost::logging::level >> "]," >> boost::logging::filename >> "(" >> boost::logging::line >> ")," >> boost::logging::time >> "," >> boost::logging::trace >> boost::logging::eol), // log format 2); // log level BOOST_LOG_ADD_OUTPUT_STREAM(new std::ofstream("./output.log")); BOOST_LOG_ADD_OUTPUT_STREAM(&std::cout); BOOST_LOG(1, "something"); BOOST_LOG(2, "something else"); BOOST_LOG(3, "doesn't matter"); char you_want[256] = "you want"; BOOST_LOG(1, "Let's say " << you_want << " to display " << 2); return 0; } // snippet off You can find the first draft of a logging library in the boost Sandbox vault. It consists of a header files, some examples and documentation. Put the file at your boost root folder and unzip it. It compiles with msvc and vc-8_0. I'll try with gcc asap. So let me know if you think it worth something or not. JD

15 34

Improving Boost Build?
by John Maddock 16 May '07

16 May '07

Irrespective of what happens with the CMake vs BBv2 debate, it's apparent that there is still plenty of support for bbv2: indeed, I would echo comments that it's a pleasure to use, provided you don't need to dig in and write new rules yourself :-) So, can we improve things to the point where 99% of the remaining issues are dealt with? I think so, the things that come to mind are: 1) Consistent command line options (as Vladimir has already brought up): use "feature=xyz" or "--feature=xyz" consistently throughout. The first of these looks to be the more commonly used within BBv2 at present, so I'd vote for that, and keep "-" and "--" options for controlling how bjam itself behaves (as in the -d and -a options). 2) Better docs. Yes, I know it's been said before, but we really must get the existing toolsets and their options documented. This need not take too long if someone would step up and volunteer to do it. 3) Most of the current problems seem to stem from folks trying to build with non-default options. Can we have a consistent way (across toolsets) to inject compiler or linker specific flags into the command line: actually I suspect we may have this already? If so it needs documenting and pointing to from the getting started docs. Likewise a consistent way of name custom-name-mangling the resulting libraries. 4) Relating to the above, I wonder if we could have a "generic" toolset that used the environment variables CXX, CXXFLAGS, LDFLAGS in much the same way that the autotools do. If necessary the top-level configure script could make use of this to behave in a more autotools-like manner. 5) More BBv2 developers :-) I actually think we do tools rather well - both quickbook and BBv2 are so very nearly where they need to be, but just need that final push that only more developers (and a wider audience) can bring. Part of the problem here is that Boost attracts folks interested in C++ libraries, and who don't necessarily want to spend their time hacking Jamfiles or whatever. I'm not sure how solve this, unless maybe these tools can acquire a life of their own outside of Boost as well as within it. Anyway these are just a few random thoughts, hopefully presented in the spirit of trying to find a positive way forward. I'll look forward to seeing what people think, Regards, John Maddock.

5 4

1.34 RC3
by Christian Henning 16 May '07

16 May '07

Hi there, I'm compiling RC3 using VC7.1 SP1 and it's looks quite good. Although I got several batches of "Could not find .... " I compiled boost using: bjam --build-dir=c:\boost_temp --toolset=msvc stage > log.txt cl : Command line warning D4025 : overriding '/GR' with '/GR-' Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_date_time-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_filesystem-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_graph-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_iostreams-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_program_options-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_python-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_regex-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_serialization-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_wserialization-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_signals-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_prg_exec_monitor-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_test_exec_monitor-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_unit_test_framework-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_thread-vc71-mt.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\boost_wave-vc71-mt.lib cl : Command line warning D4025 : overriding '/GR' with '/GR-' Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_date_time-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_filesystem-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_graph-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_iostreams-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_program_options-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_python-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_regex-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_serialization-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_wserialization-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_signals-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_prg_exec_monitor-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_unit_test_framework-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_thread-vc71-mt-gd.lib Could Not Find C:\boost_1.34\boost_1_34_0\stage\lib\libboost_wave-vc71-mt-gd.lib [snip] In the end I had 260 libs in my stage/lib folder. Is that about right? Thanks a lot to all people in this effort. Christian

4 4

Boost inspection notification (2007-05-16/RC_1_34_0) *X*
by Rene Rivera 16 May '07

16 May '07

Boost Inspection Report Run Date: 16:05:58 UTC, Wednesday 16 May 2007 An inspection program <http://www.boost.org/tools/inspect/index.html> checks each file in the current Boost CVS for various problems, generating this as output. Problems detected include tabs in files, missing copyrights, broken URL's, and similar misdemeanors. Totals: 11453 files scanned 909 directories scanned (including root) 193 problems reported Problem counts: 0 files with invalid line endings 0 bookmarks with invalid characters 3 invalid urls 101 broken links 22 unlinked files 22 file/directory names issues 1 files with tabs 9 violations of the Boost min/max guidelines 35 usages of unnamed namespaces in headers (including .ipp files) Summary: archive (3) bind (1) boost-root (1) build (1) date_time (1) doc (2) filesystem (33) graph (2) iostreams (3) lambda (3) math (8) more (4) mpl (4) multi_array (2) ptr_container (1) python (8) regex (1) regression (32) serialization (1) test (81) type_traits (1) Details: *R* invalid (cr only) line-ending *A* invalid bookmarks, invalid urls, broken links, unlinked files *N* file/directory names issues *T* tabs in file *M* uses of min or max that have not been protected from the min/max macros, or unallowed #undef-s *U* unnamed namespace in header |archive| boost/archive/basic_streambuf_locale_saver.hpp: *N* name exceeds 31 characters boost/archive/impl/xml_wiarchive_impl.ipp: *U* unnamed namespace at line 53 boost/archive/iterators/remove_whitespace.hpp: *U* unnamed namespace at line 57 |bind| boost/bind/placeholders.hpp: *U* unnamed namespace at line 25 |boost-root| index.htm: *A* broken link: doc/hmtl/date_time/details.html#changes |build| tools/build/v2/test/test_system.html: *A* unlinked file |date_time| libs/date_time/xmldoc/date_time_docs_howto.html: *A* unlinked file |doc| doc/html/boost_math/inverse_complex.html: *A* unlinked file doc/html/jam.html: *A* unlinked file |filesystem| libs/filesystem/doc/do-list.htm: *A* invalid URL (hardwired file): file://?/ *A* invalid URL (hardwired file): file://?/UNC/ libs/filesystem/doc/i18n.html: *A* broken link: convenience.htm#basic_recursive_directory_iterator *A* broken link: exception.htm *A* broken link: operations.htm *A* broken link: operations.htm#Do-the-right-thing *A* broken link: operations.htm#is_directory *A* broken link: operations.htm#is_file *A* broken link: operations.htm#status libs/filesystem/doc/index.htm: *A* broken link: ../build/Jamfile *A* broken link: convenience.htm *A* broken link: operations.htm#create_directory *A* broken link: operations.htm#create_hard_link *A* broken link: operations.htm#current_path *A* broken link: operations.htm#equivalent *A* broken link: operations.htm#file_size *A* broken link: operations.htm#initial_path *A* broken link: operations.htm#is_file *A* broken link: operations.htm#is_symlink *A* broken link: operations.htm#status *A* broken link: operations.htm#symlink_status *A* broken link: path.htm#Canonical *A* broken link: path.htm#Normalized *A* broken link: path.htm#default_name_check *A* broken link: path.htm#name_check_mechanism *A* broken link: path.htm#normalize *A* broken link: path.htm#operator_eq libs/filesystem/doc/portability_guide.htm: *A* broken link: path.htm#name_check_typedef libs/filesystem/doc/tr2_proposal.html: *A* invalid URL (hardwired file): file:///C|/boost/site/libs/filesystem/doc/operations.htm#complete_note |graph| libs/graph/example/file_dependencies.cpp: *M* violation of Boost min/max guidelines on line 139 libs/graph/test/serialize.cpp: *T* |iostreams| libs/iostreams/doc/acknowledgments.html: *A* unlinked file libs/iostreams/doc/concepts/multi-character.html: *A* unlinked file libs/iostreams/doc/installation.html: *A* broken link: ../../../tools/build/v1/build_system.htm |lambda| boost/lambda/core.hpp: *U* unnamed namespace at line 62 boost/lambda/detail/lambda_functors.hpp: *U* unnamed namespace at line 25 boost/lambda/exceptions.hpp: *U* unnamed namespace at line 24 |math| libs/math/test/common_factor_test.cpp: *M* violation of Boost min/max guidelines on line 146 *M* violation of Boost min/max guidelines on line 147 *M* violation of Boost min/max guidelines on line 193 *M* violation of Boost min/max guidelines on line 194 |more| more/cvs.html: *A* unlinked file more/getting_started/unix-variants.html: *A* broken link: ../../doc/html/thread/build.html#thread.build more/getting_started/windows.html: *A* broken link: ../../doc/html/thread/build.html#thread.build more/separate_compilation.html: *A* broken link: ../libs/config/test/link/test/Jamfile.v2 |mpl| boost/mpl/alias.hpp: *U* unnamed namespace at line 17 libs/mpl/doc/refmanual/for-each.html: *A* broken link: ./value-initialized.html |multi_array| boost/multi_array/base.hpp: *U* unnamed namespace at line 69 libs/multi_array/test/generative_tests.hpp: *U* unnamed namespace at line 57 |ptr_container| libs/ptr_container/doc/tutorial_example.html: *A* unlinked file |python| libs/python/doc/building.html: *A* broken link: ../index.htm libs/python/doc/tutorial/doc/html/python/hello.html: *A* broken link: ../../../../../example/tutorial/Jamrules libs/python/doc/tutorial/index.html: *A* broken link: ../../../LICENSE_1_0.txt libs/python/doc/v2/May2002.html: *A* broken link: ../../../../tools/build/v1/build_system.htm *A* broken link: ../../../../tools/build/v1/gen_aix_import_file.py libs/python/doc/v2/faq.html: *A* broken link: ../../../../tools/build/v1/build_system.htm |regex| libs/regex/performance/input.html: *A* unlinked file |regression| regression/.htaccess: *N* leading character of ".htaccess" is not alphabetic tools/regression/test/test-cases/incremental/bjam.log.1: *N* name contains more than one dot character ('.') tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/compile-fail.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/completed.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/compile-fail.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/completed.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/lib.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/misfire.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/no-run.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/run_pyd.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/expected/test-case.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/test-case.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_is_test_log_complete/test-driver.xsl: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_re_match/expected/test_re_match.xml: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ tools/regression/xsl_reports/test/test-components/test_test_case_status/explicit-failures-markup.xml.test: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ *N* name contains more than one dot character ('.') *N* name exceeds 31 characters tools/regression/xsl_reports/test/test-components/test_test_structure/explicit-failures-markup.xml.test: *N* file path will exceed 100 characters in a directory tree with a root of the form boost_X_XX_X/ *N* name contains more than one dot character ('.') *N* name exceeds 31 characters tools/regression/xsl_reports/xsl/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/html/summary_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/issues_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/library_user_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/make_tinyurl.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_developer_legend.html: *A* unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_user_legend.html: *A* unlinked file |serialization| libs/serialization/src/basic_xml_grammar.ipp: *U* unnamed namespace at line 43 |test| boost/test/floating_point_comparison.hpp: *U* unnamed namespace at line 206 *U* unnamed namespace at line 228 boost/test/impl/cpp_main.ipp: *U* unnamed namespace at line 42 boost/test/impl/exception_safety.ipp: *U* unnamed namespace at line 400 boost/test/impl/framework.ipp: *U* unnamed namespace at line 199 boost/test/impl/plain_report_formatter.ipp: *U* unnamed namespace at line 45 boost/test/impl/progress_monitor.ipp: *U* unnamed namespace at line 38 boost/test/impl/results_collector.ipp: *U* unnamed namespace at line 106 boost/test/impl/results_reporter.ipp: *U* unnamed namespace at line 48 boost/test/impl/unit_test_log.ipp: *U* unnamed namespace at line 79 boost/test/impl/unit_test_monitor.ipp: *U* unnamed namespace at line 35 boost/test/impl/unit_test_parameters.ipp: *U* unnamed namespace at line 50 boost/test/results_collector.hpp: *U* unnamed namespace at line 40 boost/test/test_tools.hpp: *U* unnamed namespace at line 262 boost/test/utils/iterator/token_iterator.hpp: *U* unnamed namespace at line 166 boost/test/utils/named_params.hpp: *U* unnamed namespace at line 216 boost/test/utils/runtime/cla/dual_name_parameter.ipp: *U* unnamed namespace at line 43 boost/test/utils/runtime/cla/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/env/modifier.hpp: *U* unnamed namespace at line 34 boost/test/utils/runtime/file/config_file.hpp: *U* unnamed namespace at line 169 *U* unnamed namespace at line 64 *U* unnamed namespace at line 74 boost/test/utils/runtime/file/config_file_iterator.hpp: *U* unnamed namespace at line 68 boost/test/utils/trivial_singleton.hpp: *U* unnamed namespace at line 52 *U* unnamed namespace at line 61 libs/test/build/msvc71_proj/config_file_iterator_test.vcproj: *N* name exceeds 31 characters libs/test/doc/components/prg_exec_monitor/compilation.html: *A* broken link: ../../../build/Jamfile libs/test/doc/components/prg_exec_monitor/index.html: *A* broken link: ../../../../../boost/test/cpp_main.hpp libs/test/doc/components/test_tools/index.html: *A* broken link: ../../tests/boost_check_equal_str.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_CLOSE.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_MESSAGE.html: *A* broken link: BOOST_MESSAGE.html libs/test/doc/components/test_tools/reference/BOOST_CHECK_SMALL.html: *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/test_tools/reference/tools_list.html: *A* broken link: ../../btl1.gif *A* broken link: BOOST_CHECK_CLOSE_FRACTION.html libs/test/doc/components/utf/compilation.html: *A* broken link: ../../../build/Jamfile libs/test/doc/components/utf/components/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/components/test_case/abstract_interface.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/auto_register_facility.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_boost_function_tc.html: *A* broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_class_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/param_function_tc.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_case/tc_template.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/custom_log_formatter.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_log/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_result/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/components/test_suite/index.html: *A* broken link: ../../../btl1.gif libs/test/doc/components/utf/index.html: *A* broken link: getting_started/index.html libs/test/doc/components/utf/parameters/build_info.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/catch_system_errors.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/detect_memory_leaks.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/index.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/log_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/no_result_code.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/output_format.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/random.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_format.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/report_level.html: *A* broken link: ../../btl1.gif libs/test/doc/components/utf/parameters/show_progress.html: *A* broken link: ../../btl1.gif libs/test/doc/examples/unit_test_example1.html: *A* broken link: ../../example/unit_test_example1.cpp libs/test/doc/examples/unit_test_example2.html: *A* broken link: ../../example/unit_test_example2.cpp libs/test/doc/examples/unit_test_example3.html: *A* broken link: ../../example/unit_test_example3.cpp libs/test/doc/examples/unit_test_example4.html: *A* broken link: ../../example/unit_test_example4.cpp libs/test/doc/examples/unit_test_example5.html: *A* broken link: ../../example/unit_test_example5.cpp *A* broken link: ../../example/unit_test_example5.input libs/test/doc/tests/auto_unit_test_test.html: *A* broken link: ../../test/auto_unit_test_test.cpp libs/test/doc/tests/auto_unit_test_test_mult.html: *A* broken link: ../../test/auto_unit_test_test_mult1.cpp *A* broken link: ../../test/auto_unit_test_test_mult2.cpp libs/test/doc/tests/unit_test_suite_ex_test.html: *A* broken link: ../../test/unit_test_suite_ex_test.cpp libs/test/doc/tutorials/hello_the_testing_world.html: *A* broken link: ../../../../../LICENSE_1_0.txt *A* broken link: ../execution_monitor/index.html libs/test/doc/tutorials/new_year_resolution.html: *A* broken link: ../../../../../../LICENSE_1_0.txt |type_traits| libs/type_traits/cxx_type_traits.htm: *A* unlinked file

1 0