- Boost - lists.boost.org

[Boost-bugs] [ boost-Support Requests-1530168 ] Bjam build should support attachment of individual build ids
by SourceForge.net 28 Jul '06

28 Jul '06

Support Requests item #1530168, was opened at 2006-07-28 06:57 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=1530168&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: Daniel Krügler (daniel_kruegler) Assigned to: Nobody/Anonymous (nobody) Summary: Bjam build should support attachment of individual build ids Initial Comment: The Boost library has very high reputation due to its code quality and is used in many companies and organizations as part of their own production code. Bug fixes are usually rarely necessary, but due (naturally understandable) longer release cycles, they tend to accumulate slightly, which raises the propability that individual organizations decide that they would like to use a non-official release version of boost: - They use selected parts from the current development code. - They use proposed fixes which were the result of newsgroup discussions. Due to these practices there exist need to extend the current naming scheme of boost libraries to allow the attachment of individual build id's to the current lib names, e.g. instead of the current example from http://boost.org/more/getting_started.html#Build_Install: libboost_date_time-gcc-mt-d-1_31.a I propose to extend the bjam action table with the option: -sBUILD_ID=string If this option is not used, the current naming scheme applies as usual, but if the proposed option is used, e.g. with -sBUILD_ID=M20060727-vgf3 the above output file is named to libboost_date_time-gcc-mt-d-1_31-M20060727-vgf3.a The very advantage of this proposal are: - Popular build id naming schemes tend to point themselves out of the regular version pattern and allow better discrimination from official boost release version. Build id do have a well-known tradition in many popular software products. - The proposal is non-intrusive and allows tagging boost output according to company-specific naming schemes. Users don't need to manually "hack" the current bjam input file to enforce such naming scheme. Users not interested in this scheme will not be influenced by this extension. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1530168&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] error in boost/config/platform/hpux.hpp (thread support)
by Oliver.Kowalke＠qimonda.com 28 Jul '06

28 Jul '06

Julien Delacroix wrote: > Maybe it will be necessary to check aCC version and set > BOOST_DISABLE_THREADS for old aCC version that do not have thread > suport... Boost did not compile under HP/UX 11.11 (PA-RISC) with aCC because only the old aCC version 3.x is shipped on PA-RISC systems. aCC 3.x is far away from the C++ standard - use instead gcc. regards, Oliver

1 0

pimpl pointer revisited
by Aljaz Noe 27 Jul '06

27 Jul '06

Hi! Recently there was a proposal to add a class template that simplifies the implementation of a PIMPL idiom to Boost. Unfortunately I missed the review deadline so I could not submit a proper review. But I do have some experience with PIMPL class template that I would like to share with you. I wrote similar class template a couple of years ago (see attached file). The basic idea is the same as in a proposed PIMPL class. I call it ImplWrapper, because it is used to wrap class implementation details. Besides automating the standard PIMPL functionality, it also addresses the following issues: 1. The Impl object can be allocated in a buffer that is provided by ImplWrapper class. The reason for this is to avoid unnecessary allocation of small objects on the heap and to increase performance. In fact, I believe that with proper compiler optimizations, there should be no difference between using ImplWrapper class and storing data members in class directly (additional pointer indirection normally associated with a PIMPL idiom is eliminated). The drawback is that the size of the Impl object must be known (guessed) in advance. Sometimes this is not possible, so there is also alternative implementation that allocates Impl object on the heap. 2. Arbitrary parameters can be passed to Impl constructor by wrapping them in a temporary struct. This struct Par, is forward declared within ImplWrapper class and can be specialized for each type of Impl class. There is no need for policies or other design complications. 3. Simplicity. The overall design seems simple, yet functional. But I do admit that this opinion may by biased. ;-) Since the above issues were not resolved within the proposed PIMPL class (I only quickly glanced over the implementation and a PIMPL thread in this list at the end of May, so I might have skipped something), I decided to post my implementation here. I believe that PIMPL idiom is so often used in C++, that it should have some support in Boost (maybe even in future versions of standard C++ library). Hopefully this post will contribute to that goal. Any comments are greatly appreciated. Regards, Aljaz

2 2

Re: [boost] Exception Visitor
by Sohail Somani 27 Jul '06

27 Jul '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Alexander Nasonov > > 2. catch(...) catches too many things on some compilers. I > know only one (very popular) compiler that also catches > system exceptions (aka SEH). Though, I don't remember how it > rethrows those exceptions. If you are talking about msvc, I think C++ exceptions are implemented on top of SEH. Sohail

1 0

[Boost-bugs] [ boost-Bugs-1529988 ] compile warning in token-functions.hpp
by SourceForge.net 27 Jul '06

27 Jul '06

Bugs item #1529988, was opened at 2006-07-27 14:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1529988&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: James W. Walker (jwwalker) Assigned to: Nobody/Anonymous (nobody) Summary: compile warning in token-functions.hpp Initial Comment: When compiling with -Wall in gcc 4, token-functions.hpp gives a warning about escaped_list_error. The warning is "declaration of 'what' shadows a member of 'this'". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1529988&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Concept traits
by Chad Parry 27 Jul '06

27 Jul '06

What is the fate of the operator_concept_traits library that Terje Slettebø introduced on the Boost mailing list in 2004? A "has_plus_op" metafunction would be immensely useful, if only as a foundation for other generic code. Is the source code in a vault somewhere? -- chad

1 0

[Random] Non-Deterministic Generator Not Included in Library
by Jill Stellman 27 Jul '06

27 Jul '06

I am using the non-deterministic random number generator from the Boost.Random library. I included nondet_random.hpp in my source code, but it does not contain the implementation. I attempted to use Bjam to build the Boost.Random library, but it did not build. I used the following command: bjam -sTOOLS=gcc --prefix=/usr --with-boost_random --without-python install which resulted in (only) the following output Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). ...found 6900 targets... and (obviously?) did not build the library for boost_random. I am using boost 1.33.1-4, bjam 3.1.11-1, g++ 4.1.2, Debian 64bit unstable. I eventually just built a library manually by making random_device.o from random_device.cpp and using ar, which seems to work. Unfortunately, this process will not work for me as a permanent solution. On searching the mailing list archives, I found the following thread: http://thread.gmane.org/gmane.comp.lib.boost.devel/106229/focus=106228 which unfortunately has no further responses. Does anyone know if anything has been done to address this issue or if there is some reason why the non-deterministic random number generator should not be used? Thanks, Jill

1 0

Computational Geometry Library
by Arash Partow 27 Jul '06

27 Jul '06

Hi all, I was wondering if there was anyone working on / managing the BOOST geometry libraries? I can't seem to see if anyone has already put their hand up or not. I've noticed that it was a contender for the 2006 SoC, and that there are a couple of code samples in the BOOST vault. In any case I'm planning on making a preliminary library submission sometime soon, I've been contact with one of the other code submitters, I just want to make sure there isn't an effort already underway, I've searched the mailing list, and have found anything of interest. If anyone has any information about this topic, please feel free to comment as it would help a great deal. As for a preliminary library design I propose the following: * primitive geometric structures 2D/3D only (point,line,segment,triangle...) * operations between primitives (intersection, distance, inclusion...) * higher level algorithms in a structured fashion similar to BGL: * hulls, rotating caliper * triangulation (point sets, polygons) * boolean operations over polygons Note: algorithms will be named based on method then algorithm type for example convex hull variations would be: 1. graham_scan_convex_hull(it_begin,it_end,out_it) 2. jarvis_march_convex_hull(it_begin,it_end,out_it) 3. gift_wrapping_convex_hull(it_begin,it_end,out_it) 4. quick_convex_hull(it_begin,it_end,out_it) * precision related issues to be dealt with mainly by user specified floating point type, and partially at the algorithm level * keep code bloat and over-engineering to a minimum. ie: in cgal to determine whether or not 2 segments intersect you need roughly 35 lines of source code. Should be something like the following: boost::geometry { segment<T,D> seg1 = make_segment(....); segment<T,D> seg2 = make_segment(....); . . if (intersect(seg1,seg2)) ...; else ...; } Arash Partow ________________________________________________________ Be one who knows what they don't know, Instead of being one who knows not what they don't know, Thinking they know everything about all things. http://www.partow.net

4 3

[system] system-0.2 request for comments
by Beman Dawes 27 Jul '06

27 Jul '06

system-0.2.zip has been posted in the file vault. See the "system" directory at http://boost-consulting.com/vault/ This is a major upgrade, reflecting comments and suggestions from many Boosters, but in particular Chris Kohlhoff and Peter Dimov. Important changes include: * Class error_code now supports additional categories of errors, such as those that may bubble up from asio. I'll be watching for for a response from Chris to make sure this meets asio's needs. * Refactoring into two headers, boost/system/error_code.hpp and boost/system/system_error.hpp, in line with the fine header granularity normal in Boost libraries. Docs refactored accordingly. * Addition of a header boost/identifier.hpp. For years I've used a similar class to provide the type safety and freedom from unwanted conversions that is missing when a simple int is used for an identifier. This is logically separate from the system stuff, but for convenience is included in the system package since error_code.hpp uses it. * More complete docs. * Jamfiles provided. * More extensive testing, with all tests passing for late-model GCC, CodeWarrior, Intel, and Microsoft compilers on Windows, and GCC on the Mac. Not tested yet on Linux. Comments welcome! --Beman

8 22

Boost regression notification (2006-07-27 [RC_1_34_0])
by Douglas Gregor 27 Jul '06

27 Jul '06

Boost Regression test failures Report time: 2006-07-27T08:00:00Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 277 failures in 25 libraries algorithm/string (1) concept_check (1) filesystem (4) graph (5) io (1) iostreams (10) mpl (5) multi_index (1) numeric/conversion (4) numeric/interval (1) numeric/ublas (7) parameter (20) program_options (9) python (90) random (1) rational (4) regex (4) serialization (27) signals (16) spirit (1) test (2) tr1 (51) typeof (9) utility (1) xpressive (2) |algorithm/string| regex: borland-5_6_4 |concept_check| class_concept_check_test: vc-7_1-stlport |filesystem| mbcopy: sun-5.8 operations_test: vc-7_1-stlport operations_test_dll: vc-7_1-stlport wide_test: sun-5.8 |graph| adjacency_matrix_test: vc-7_0 csr_graph_test: sun-5.8 graphviz_test: msvc-8.0 msvc-8.0 vc-7_1-stlport |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 compose_test: borland-5_6_4 example_test: vc-6_5-stlport filtering_stream_test: vc-7_1-stlport finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 zlib_test: msvc-7.1 msvc-8.0 |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 vector_c: sun-5.8 |multi_index| test_projection: gcc-4.0.3_linux |numeric/conversion| converter_test: borland-5_8_2 traits_test: borland-5_8_2 udt_example_0: borland-5_8_2 udt_support_test: borland-5_8_2 |numeric/interval| test_float: vc-7_1-stlport |numeric/ublas| concepts: vc-7_1-stlport vc-7_1-stlport test1: vc-7_1-stlport test2: vc-7_1-stlport test4: vc-7_1-stlport test5: vc-7_1-stlport vc-7_1-stlport |parameter| duplicates: borland-5_6_4 borland-5_8_2 maybe: vc-6_5 vc-6_5-stlport vc-7_0 preprocessor: borland-5_6_4 borland-5_8_2 sun-5.8 vc-6_5 vc-6_5-stlport python-parameter-test: vc-6_5 vc-6_5-stlport vc-7_0 sfinae: borland-5_8_2 vc-6_5-stlport singular: borland-5_6_4 borland-5_8_2 unnamed_fail: vc-6_5 vc-6_5-stlport vc-7_0 |program_options| cmdline_test_dll: cw-9.4 options_description_test_dll: cw-9.4 parsers_test_dll: cw-9.4 positional_options_test_dll: cw-9.4 unicode_test_dll: borland-5_8_2 cw-9.4 variable_map_test_dll: borland-5_8_2 cw-9.4 winmain_dll: cw-9.4 |python| andreas_beyer: sun-5.8 args: sun-5.8 auto_ptr: sun-5.8 back_reference: sun-5.8 bases: gcc-3_4_4_tru64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 sun-5.8 ben_scott1: sun-5.8 bienstman1: sun-5.8 bienstman2: sun-5.8 bienstman3: sun-5.8 borrowed: sun-5.8 callbacks: sun-5.8 const_argument: sun-5.8 crossmod_exception: sun-5.8 data_members: sun-5.8 defaults: sun-5.8 dict: sun-5.8 docstring: sun-5.8 enum: sun-5.8 exception_translator: sun-5.8 exec: cw-9.4 darwin-4.0.1 gcc-3_4_4_tru64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp sun-5.8 extract: sun-5.8 implicit: sun-5.8 indirect_traits_test: sun-5.8 injected: sun-5.8 iterator: sun-5.8 keywords: sun-5.8 list: sun-5.8 long: sun-5.8 minimal: sun-5.8 multi_arg_constructor: sun-5.8 nested: sun-5.8 numpy: sun-5.8 object: sun-5.8 object_manager: sun-5.8 opaque: sun-5.8 operators: sun-5.8 pearu1: sun-5.8 pickle1: sun-5.8 pickle2: sun-5.8 pickle3: sun-5.8 pickle4: sun-5.8 pointee: gcc-3_4_4_tru64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 sun-5.8 pointer_type_id_test: gcc-3_4_4_tru64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 sun-5.8 pointer_vector: sun-5.8 polymorphism: sun-5.8 polymorphism2: sun-5.8 polymorphism2_auto_ptr: sun-5.8 properties: sun-5.8 raw_ctor: sun-5.8 return_arg: sun-5.8 select_arg_to_python_test: sun-5.8 select_from_python_test: darwin-4.0.1 sun-5.8 select_holder: sun-5.8 shared_ptr: sun-5.8 slice: sun-5.8 staticmethod: sun-5.8 stl_iterator: sun-5.8 str: sun-5.8 string_literal: sun-5.8 test_pointer_adoption: sun-5.8 try: sun-5.8 tuple: sun-5.8 upcast: gcc-3_4_4_tru64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 sun-5.8 vector_indexing_suite: sun-5.8 virtual_functions: sun-5.8 voidptr: sun-5.8 wrapper_held_type: sun-5.8 |random| random_test: intel-linux-9.0 |rational| rational_test: borland-5_6_4 vc-6_5 vc-6_5-stlport vc-7_0 |regex| regex_regress: vc-6_5 vc-6_5-stlport regex_regress_dll: vc-6_5 vc-6_5-stlport |serialization| test_class_info_load_text_warchive: vc-6_5 test_demo_xml: msvc-8.0 test_list_binary_archive_dll: msvc-8.0 test_non_default_ctor2_text_archive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_archive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_non_default_ctor2_text_warchive_dll: qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_simple_class_binary_archive_dll: vc-6_5 test_simple_class_text_archive_dll: vc-6_5 test_simple_class_text_warchive_dll: vc-6_5 test_simple_class_xml_archive_dll: vc-6_5 test_simple_class_xml_warchive_dll: vc-6_5 test_variant_xml_archive: borland-5_8_2 test_variant_xml_archive_dll: borland-5_8_2 gcc-3.3.6_linux test_variant_xml_warchive: borland-5_8_2 test_variant_xml_warchive_dll: borland-5_8_2 |signals| dead_slot_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp trackable_test: gcc-3.3.6 gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp qcc-3.3.5_gpp |spirit| mix_and_match_trees: sun-5.8 |test| parameterized_test_test: vc-6_5 vc-6_5-stlport |tr1| run_random: sun-5.8 std_run_complex_overloads: sun-5.8 std_run_random: sun-5.8 std_test_bind: sun-5.8 std_test_complex: sun-5.8 std_test_function: sun-5.8 std_test_hash: sun-5.8 std_test_mem_fn: sun-5.8 std_test_random: sun-5.8 std_test_reference_wrapper: sun-5.8 std_test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp vc-7_1-stlport std_test_result_of: sun-5.8 std_test_shared_ptr: sun-5.8 std_test_tuple: sun-5.8 std_test_tuple_tricky: sun-5.8 std_test_type_traits: sun-5.8 test_boost: vc-7_1-stlport test_hash: vc-7_1-stlport test_random: sun-5.8 vc-7_1-stlport test_reference_wrapper_tricky: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux_x86_64 intel-linux-9.0 mingw-3_4_2 msvc-7.1 msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp test_regex: vc-7_1-stlport test_type_traits: sun-5.8 tr1_tky_function_type_test: sun-5.8 |typeof| function_binding_emulation: sun-5.8 function_binding_native: vc-6_5 vc-6_5-stlport vc-7_0 nested_typedef_emulation: cw-9.4 odr_no_uns: vc-6_5 vc-6_5-stlport vc-7_0 template_tpl_emulation: sun-5.8 |utility| operators_test: gcc-3.4.5_linux_x86_64 |xpressive| test2: msvc-8.0 test9: gcc-3.3.6_linux

2 1