- Boost - lists.boost.org

Where is typeof downloadable?
by Andy Little 23 Jan '06

23 Jan '06

Where is it possible to download a version of typeof.zip library, apart from cvs. It used to be in the vault. Is it possible to put a version back there or cant I find it? regards Andy Little

2 6

[typeof-users] Looking for a consistent scheme for adding Typeof support to Boost libraries
by Tobias Schwinger 22 Jan '06

22 Jan '06

Dear Boost developers, based on some experiments which I recently made with Typeof and Spirit, Joel de Guzman asked me if I would like to add "official" Typeof support to Spirit and got me in touch with Dan Marsden, who recently added experimental Typeof support to Phoenix2. Dan and I started discussing how Typeof support could look like for the two libraries and agreed in one important point: things should be consistent. Dan pointed out to me that it would be best to use a consistent scheme for adding Typeof support not only for Spirit and Phoenix2 but for all Boost libraries and therefore suggested shifting the discussion (previously in private email) to the Boost developers mailinglist. There are some suggestion on how such a scheme could look like at the end of this post. I'm looking forward to your comments. Thanks, Tobias Suggestions on possible schemes: ( 'a_lib' in the examples denotes a placholder for the name of the library, 'a_component.hpp' denotes the name of a public header of the library. ) 1. Create a 'typeof_support' directory reflecting the public headers of the library. The user enables Typeof support by including additional headers. Example: #include <boost/a_lib/a_component.hpp> // ^^^ usual library header #include <boost/a_lib/typeof_support/a_component.hpp> // ^^^ contains the registration for the header above 2. The Typeof registration is done in one separate header per library (module) that checks the include guards to register the components, where the registration is guarded by "registration guards" (as suggested by Arkadiy Vertleyb in the "Typeof and MPL" thread). The user enables Typeof support for the whole library by including a single header. Example: #include <boost/a_lib/a_component.hpp> #include <boost/a_lib/typeof_support.hpp> // The typeof_support header would do the following: // - Check the include guard macros to see which files have been // included // +-- For each of these files: register the components defined within // (guarded by a "registration guard macro") // - Define a macro to notify library headers #includeD later that the // Typeof support header has to be re-#includeD // (for large libraries this approach can be applied on a per-module basis) 3. The Typeof registration is put into the library's headers protected by some conditional. The user enables (or disables) Typeof support by defining a macro. Example: #define BOOST_A_LIB_TYPEOF_SUPPORT // ^^^ (or even do it in the Jamfile) #include <boost/a_lib/a_component.hpp>

6 31

[iostreams] file_descriptor openmode bug
by Takeshi Mouri 22 Jan '06

22 Jan '06

Hello, On Windows platform, I noticed that how to treat boost::file_descriptor and std::fstream's openmode was different. Here's the test code: (I tested on VC++8.0 with Boost 1.33.1) #include <boost/test/unit_test.hpp> #include <boost/iostreams/detail/ios.hpp> #include <windows.h> DWORD make_create_flags(BOOST_IOS::openmode m) { // copy from file_descriptor::open() DWORD dwDesiredAccess; DWORD dwCreationDisposition; if ( (m & (BOOST_IOS::in | BOOST_IOS::out)) == (BOOST_IOS::in | BOOST_IOS::out) ) { assert(!(m & BOOST_IOS::app)); dwDesiredAccess = GENERIC_READ | GENERIC_WRITE; dwCreationDisposition = (m & BOOST_IOS::trunc) ? #ifndef FIX OPEN_ALWAYS : #else CREATE_ALWAYS : #endif OPEN_EXISTING; } else if (m & BOOST_IOS::in) { assert(!(m & (BOOST_IOS::app |BOOST_IOS::trunc))); dwDesiredAccess = GENERIC_READ; dwCreationDisposition = OPEN_EXISTING; } else if (m & BOOST_IOS::out) { dwDesiredAccess = GENERIC_WRITE; #ifndef FIX dwCreationDisposition = OPEN_ALWAYS; #else dwCreationDisposition = (m & BOOST_IOS::app) ? OPEN_ALWAYS : CREATE_ALWAYS; #endif } return dwCreationDisposition; } struct test : BOOST_IOS { static void run() { BOOST_CHECK_EQUAL(make_create_flags(out), CREATE_ALWAYS); BOOST_CHECK_EQUAL(make_create_flags(out|app), OPEN_ALWAYS); BOOST_CHECK_EQUAL(make_create_flags(out|trunc), CREATE_ALWAYS); BOOST_CHECK_EQUAL(make_create_flags(in), OPEN_EXISTING); BOOST_CHECK_EQUAL(make_create_flags(in|out), OPEN_EXISTING); BOOST_CHECK_EQUAL(make_create_flags(in|out|trunc), CREATE_ALWAYS); // binary modes are omitted... } }; using boost::unit_test::test_suite; test_suite* init_unit_test_suite(int, char*[]) { test_suite* test = BOOST_TEST_SUITE("openmode test"); test->add(BOOST_TEST_CASE(&test::run)); return test; } These test cases are the one having derived it from the standard and some implementation of std::fstream. If a macro "FIX" is defined, all test cases are passed. Regards, Takeshi Mouri

1 0

[wave] pp-number bug?
by Alberto Ganesh Barbati 22 Jan '06

22 Jan '06

Hi, this post originates from thread "concatenation of power of negative number" in comp.std.c++ (http://tinyurl.com/asn95) Consider this file: ---- #include <boost/preprocessor/cat.hpp> BOOST_PP_CAT(1e, -1) ---- According to Paul Mensonides' reply in the thread, it should be eventually interpreted as <1e> ## <-> <1> thus the pp-number "1e" is concatenated with "-" obtaining the pp-number "1e-" and then "1" is appended as a separate token. The final result would thus be "1e- 1" (notice the blank between "-" and "1"). However, if run into Wave, the program above produces the error message: error: pasting the following two tokens does not give a valid preprocessing token: "e" and "-" Who's right? I'd agree with Paul Mensonides, because "1e" is a valid pp token which is to be formed before applying the ## operator. But my understanding is quite limited in this area so I commit myself to the Gurus. Ganesh

4 5

[regex]compiling error
by Wang Weiwei 21 Jan '06

21 Jan '06

hello, On VS.net 2003 compiler, I'm building the boost library using the following commands/setitngs/procedure: 1. build bjam.exe using build.bat; 2. build boost with a .bat file with the following contents, under the boost root folder: SET PYTHON_ROOT="D:\Python24" SET PYTHON_VERSION=2.4.2 SET STLPORT_PATH="D:\" SET STLPORT_50_PATH="D:\STLport_50" SET STLPORT_VERSION=5.0 SET STLPORT_VERSIONS=5.0 SET VC71_ROOT="d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" Bjam.exe -sBOOST_ROOT=. -sTOOLS=vc-7_1 "-sBUILD=debug release <runtime-link>static/dynamic <threading>single/multi" stage Bjam.exe -sBOOST_ROOT=. -sTOOLS=vc-7_1-stlport "-sBUILD=debug release <runtime-link>static/dynamic <threading>single/multi" stage 3. I get the lib files in <boost>\stage\lib folder. In my test app, I'm using boost::regex lib and some others. And I'm using STLport 5.0 by placing the STLport include file path before the vender's default include path. But I'm getting the following compiling error: e:\Lib\boost_1_33_1\boost\config\auto_link.hpp(211) : fatal error C1189: #error : "Build options aren't compatible with pre-built libraries" After commenting out the code related to boost::regex, every thing seems to be OK. And after I disable linking to STLport by changing the include file searching order, it's also OK. Can anybody give me some hint on this? Thanks a lot. Max

2 1

Boost regression notification (2006-01-21 [HEAD])
by Douglas Gregor 21 Jan '06

21 Jan '06

Boost Regression test failures Report time: 2006-01-21T13:56:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 404 failures in 19 libraries xpressive (24) date_time (6) python (3) graph (5) random (1) numeric/interval (3) signals (30) concept_check (21) smart_ptr (2) rational (4) filesystem (31) test (5) program_options (7) serialization (182) wave (3) parameter (12) spirit (34) iostreams (23) typeof (8) |xpressive| c_traits: cw-9_5-darwin misc1: cw-9_5-darwin regress: cw-9_5-darwin test1: cw-9_5-darwin test10: cw-9_5-darwin test10u: cw-9_5-darwin test1u: cw-9_5-darwin test2: cw-9_5-darwin test2u: cw-9_5-darwin test3: cw-9_5-darwin test3u: cw-9_5-darwin test4: cw-9_5-darwin test4u: cw-9_5-darwin test5: cw-9_5-darwin test5u: cw-9_5-darwin test6: cw-9_5-darwin test6u: cw-9_5-darwin test7: cw-9_5-darwin test7u: cw-9_5-darwin test8: cw-9_5-darwin test8u: cw-9_5-darwin test9: cw-9_5-darwin test9u: cw-9_5-darwin test_non_char: cw-9_5-darwin |date_time| testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 vc-7_1 |python| docstring: cw-9_4 numpy: gcc-4_0-darwin slice: gcc-4_0-darwin |graph| csr_graph_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux graphviz_test: vc-7_1 vc-7_1 vc-7_1 |random| random_test: intel-9.0-linux |numeric/interval| det: tru64cxx71-006 mul: tru64cxx71-006 overflow: tru64cxx71-006 |signals| dead_slot_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 trackable_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 vc-7_1 vc-7_1 vc-7_1 |concept_check| stl_concept_covering: cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 mingw-3_4_2 mingw-3_4_2 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |smart_ptr| auto_ptr_rv_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |rational| rational_test: gcc-2.95.3-stlport-4.6.2-linux vc-7_1 vc-7_1 vc-7_1 |filesystem| convenience_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux fstream_test: gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux large_file_support_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mbcopy: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mingw-3_4_2 mingw-3_4_2 mbpath: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux mingw-3_4_2 mingw-3_4_2 operations_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux operations_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux path_test_dll: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux simple_ls: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux wide_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3.2.3-linux mingw-3_4_2 mingw-3_4_2 tru64cxx71-006 |test| test_fp_comparisons: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tools_test: gcc-4_0-darwin mingw-3_4_2 mingw-3_4_2 |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: cw-9_4 variable_map_test_dll: cw-9_4 winmain_dll: cw-9_4 |serialization| test_array_binary_archive_dll: cw-9_4 test_array_text_archive_dll: cw-9_4 test_array_text_warchive_dll: cw-9_4 test_array_xml_archive_dll: cw-9_4 test_array_xml_warchive_dll: cw-9_4 test_binary_binary_archive_dll: cw-9_4 test_binary_text_archive_dll: cw-9_4 test_binary_text_warchive_dll: cw-9_4 test_binary_xml_archive_dll: cw-9_4 test_binary_xml_warchive_dll: cw-9_4 test_class_info_load_binary_archive_dll: cw-9_4 test_class_info_load_text_archive_dll: cw-9_4 test_class_info_load_text_warchive_dll: cw-9_4 test_class_info_load_xml_archive_dll: cw-9_4 test_class_info_load_xml_warchive_dll: cw-9_4 test_class_info_save_binary_archive_dll: cw-9_4 test_class_info_save_text_archive_dll: cw-9_4 test_class_info_save_text_warchive_dll: cw-9_4 test_class_info_save_xml_archive_dll: cw-9_4 test_class_info_save_xml_warchive_dll: cw-9_4 test_contained_class_binary_archive_dll: cw-9_4 test_contained_class_text_archive_dll: cw-9_4 test_contained_class_text_warchive_dll: cw-9_4 test_contained_class_xml_archive_dll: cw-9_4 test_contained_class_xml_warchive_dll: cw-9_4 test_cyclic_ptrs_binary_archive_dll: cw-9_4 test_cyclic_ptrs_text_archive_dll: cw-9_4 test_cyclic_ptrs_text_warchive_dll: cw-9_4 test_cyclic_ptrs_xml_archive_dll: cw-9_4 test_cyclic_ptrs_xml_warchive_dll: cw-9_4 test_delete_pointer_binary_archive_dll: cw-9_4 test_delete_pointer_text_archive_dll: cw-9_4 test_delete_pointer_text_warchive: vc-7_1 test_delete_pointer_text_warchive_dll: cw-9_4 test_delete_pointer_xml_archive_dll: cw-9_4 test_delete_pointer_xml_warchive_dll: cw-9_4 test_demo_auto_ptr_dll: cw-9_4 test_demo_fast_archive_dll: cw-9_4 test_demo_pimpl_dll: cw-9_4 test_demo_polymorphic_dll: cw-9_4 test_demo_portable_archive_dll: cw-9_4 test_deque_binary_archive_dll: cw-9_4 test_deque_text_archive_dll: cw-9_4 test_deque_text_warchive_dll: cw-9_4 test_deque_xml_archive_dll: cw-9_4 test_deque_xml_warchive_dll: cw-9_4 test_derived_binary_archive_dll: cw-9_4 test_derived_class_binary_archive_dll: cw-9_4 test_derived_class_ptr_binary_archive_dll: cw-9_4 test_derived_class_ptr_text_archive_dll: cw-9_4 test_derived_class_ptr_text_warchive_dll: cw-9_4 test_derived_class_ptr_xml_archive_dll: cw-9_4 test_derived_class_ptr_xml_warchive_dll: cw-9_4 test_derived_class_text_archive_dll: cw-9_4 test_derived_class_text_warchive_dll: cw-9_4 test_derived_class_xml_archive_dll: cw-9_4 test_derived_class_xml_warchive_dll: cw-9_4 test_derived_text_archive_dll: cw-9_4 test_derived_text_warchive_dll: cw-9_4 test_derived_xml_archive_dll: cw-9_4 test_derived_xml_warchive_dll: cw-9_4 test_diamond_binary_archive_dll: cw-9_4 test_diamond_text_archive_dll: cw-9_4 test_diamond_text_warchive_dll: cw-9_4 test_diamond_xml_archive_dll: cw-9_4 test_diamond_xml_warchive_dll: cw-9_4 test_list_binary_archive_dll: cw-9_4 test_list_ptrs_binary_archive_dll: cw-9_4 test_list_ptrs_text_archive_dll: cw-9_4 test_list_ptrs_text_warchive_dll: cw-9_4 test_list_ptrs_xml_archive_dll: cw-9_4 test_list_ptrs_xml_warchive_dll: cw-9_4 test_list_text_archive_dll: cw-9_4 test_list_text_warchive_dll: cw-9_4 test_list_xml_archive_dll: cw-9_4 test_list_xml_warchive_dll: cw-9_4 test_map_binary_archive_dll: cw-9_4 test_map_text_archive_dll: cw-9_4 intel-win32-8_1 test_map_text_warchive: intel-win32-8_1 test_map_text_warchive_dll: cw-9_4 test_map_xml_archive_dll: cw-9_4 test_map_xml_warchive_dll: cw-9_4 test_multiple_ptrs_binary_archive_dll: cw-9_4 test_multiple_ptrs_text_archive_dll: cw-9_4 test_multiple_ptrs_text_warchive_dll: cw-9_4 test_multiple_ptrs_xml_archive_dll: cw-9_4 test_multiple_ptrs_xml_warchive_dll: cw-9_4 test_non_default_ctor_binary_archive_dll: cw-9_4 test_non_default_ctor_text_archive_dll: cw-9_4 test_non_default_ctor_text_warchive_dll: cw-9_4 test_non_default_ctor_xml_archive_dll: cw-9_4 test_non_default_ctor_xml_warchive_dll: cw-9_4 test_non_intrusive_binary_archive_dll: cw-9_4 test_non_intrusive_text_archive_dll: cw-9_4 test_non_intrusive_text_warchive_dll: cw-9_4 test_non_intrusive_xml_archive_dll: cw-9_4 test_non_intrusive_xml_warchive_dll: cw-9_4 test_null_ptr_binary_archive_dll: cw-9_4 test_null_ptr_text_archive_dll: cw-9_4 test_null_ptr_text_warchive_dll: cw-9_4 test_null_ptr_xml_archive_dll: cw-9_4 test_null_ptr_xml_warchive_dll: cw-9_4 test_nvp_binary_archive_dll: cw-9_4 test_nvp_text_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_nvp_text_archive_dll: cw-9_4 test_nvp_text_warchive_dll: cw-9_4 test_nvp_xml_archive_dll: cw-9_4 test_nvp_xml_warchive_dll: cw-9_4 test_object_binary_archive_dll: cw-9_4 test_object_text_archive_dll: cw-9_4 test_object_text_warchive_dll: cw-9_4 test_object_xml_archive_dll: cw-9_4 test_object_xml_warchive_dll: cw-9_4 test_optional_binary_archive_dll: cw-9_4 test_optional_text_archive_dll: cw-9_4 test_optional_text_warchive_dll: cw-9_4 test_optional_xml_archive_dll: cw-9_4 test_optional_xml_warchive_dll: cw-9_4 test_polymorphic_binary_archive_dll: cw-9_4 test_polymorphic_text_archive_dll: cw-9_4 test_polymorphic_text_warchive_dll: cw-9_4 test_polymorphic_xml_archive_dll: cw-9_4 test_polymorphic_xml_warchive_dll: cw-9_4 test_primitive_binary_archive_dll: cw-9_4 test_primitive_text_archive_dll: cw-9_4 test_primitive_text_warchive_dll: cw-9_4 test_primitive_xml_archive_dll: cw-9_4 test_primitive_xml_warchive_dll: cw-9_4 test_private_ctor_dll: cw-9_4 test_recursion_binary_archive_dll: cw-9_4 test_recursion_text_archive_dll: cw-9_4 test_recursion_text_warchive_dll: cw-9_4 test_recursion_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_recursion_xml_archive_dll: cw-9_4 gcc-3.4.4-linux test_recursion_xml_warchive: gcc-3.3.6-linux gcc-3.4.4-linux test_recursion_xml_warchive_dll: cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux test_reset_object_address_dll: cw-9_4 test_set_binary_archive_dll: cw-9_4 test_set_text_archive_dll: cw-9_4 test_set_text_warchive_dll: cw-9_4 test_set_xml_archive_dll: cw-9_4 test_set_xml_warchive_dll: cw-9_4 test_shared_ptr_132_text_archive: intel-win32-8_1 test_shared_ptr_132_text_archive_dll: intel-win32-8_1 test_simple_class_binary_archive_dll: cw-9_4 test_simple_class_ptr_binary_archive_dll: cw-9_4 test_simple_class_ptr_text_archive_dll: cw-9_4 test_simple_class_ptr_text_warchive_dll: cw-9_4 test_simple_class_ptr_xml_archive_dll: cw-9_4 test_simple_class_ptr_xml_warchive_dll: cw-9_4 test_simple_class_text_archive_dll: cw-9_4 test_simple_class_text_warchive_dll: cw-9_4 test_simple_class_xml_archive_dll: cw-9_4 test_simple_class_xml_warchive_dll: cw-9_4 test_split_binary_archive_dll: cw-9_4 test_split_text_archive_dll: cw-9_4 test_split_text_warchive_dll: cw-9_4 test_split_xml_archive_dll: cw-9_4 test_split_xml_warchive_dll: cw-9_4 test_tracking_binary_archive_dll: cw-9_4 test_tracking_text_archive_dll: cw-9_4 test_tracking_text_warchive_dll: cw-9_4 test_tracking_xml_archive_dll: cw-9_4 test_tracking_xml_warchive_dll: cw-9_4 test_variant_binary_archive_dll: cw-9_4 test_variant_text_archive_dll: cw-9_4 test_variant_text_warchive_dll: cw-9_4 test_variant_xml_archive_dll: cw-9_4 test_variant_xml_warchive_dll: cw-9_4 test_vector_binary_archive_dll: cw-9_4 test_vector_text_archive_dll: cw-9_4 test_vector_text_warchive_dll: cw-9_4 test_vector_xml_archive_dll: cw-9_4 test_vector_xml_warchive_dll: cw-9_4 test_void_cast_dll: cw-9_4 |wave| testwave: cw-9_5-darwin testwave_dll: cw-9_4 cw-9_5-darwin |parameter| basics: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux efficiency: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux macros: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux sfinae: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux tutorial: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux unnamed: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |spirit| scanner_value_type_tests: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 scanner_value_type_tests_debug: cw-9_4 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux gcc-3.4.4-linux gcc-3.4.5-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4.0.2-linux gcc-4_0-darwin intel-9.0-linux intel-win32-8_1 intel-win32-9_0 tru64cxx71-006 vc-7_1 vc-7_1 vc-7_1 |iostreams| auto_close_test: tru64cxx71-006 bzip2_test: vc-7_1 code_converter_test: tru64cxx71-006 component_access_test: tru64cxx71-006 compose_test: tru64cxx71-006 copy_test: tru64cxx71-006 counter_test: tru64cxx71-006 example_test: tru64cxx71-006 filtering_stream_test: tru64cxx71-006 finite_state_filter_test: tru64cxx71-006 flush_test: tru64cxx71-006 invert_test: tru64cxx71-006 line_filter_test: tru64cxx71-006 newline_test: tru64cxx71-006 pipeline_test: tru64cxx71-006 regex_filter_test: tru64cxx71-006 restrict_test: tru64cxx71-006 seekable_file_test: tru64cxx71-006 seekable_filter_test: tru64cxx71-006 stdio_filter_test: tru64cxx71-006 symmetric_filter_test: tru64cxx71-006 tee_test: tru64cxx71-006 wide_stream_test: tru64cxx71-006 |typeof| function_ptr_from_tpl_emulation: vc-7_1 vc-7_1 vc-7_1 function_ptr_from_tpl_native: vc-7_1 vc-7_1 vc-7_1 lvalue_emulation: gcc-4.0.2-linux lvalue_native: gcc-4.0.2-linux

1 0

Re: [boost] [multi_index] intrusive multi_index poll for interest
by JOAQUIN LOPEZ MU?Z 21 Jan '06

21 Jan '06

----- Mensaje original ----- De: David Abrahams <dave(a)boost-consulting.com> Fecha: Sábado, Enero 21, 2006 3:54 am Asunto: Re: [boost] [multi_index] intrusive multi_index poll for interest > "JOAQUIN LOPEZ MU?Z" <joaquin(a)tid.es> writes: > > >> > I will need another member function to return the > >> > position ordinal of a given element (that is, > >> > the inverse of operator[]), and for that "position" > >> > seems also a good candidate. > >> > >> IMO that should have been "index." > > > > But "index" already has a disparate meaning in the > > context of Boost.MultiIndex. > > I'm not sure that's a problem. But if it is, maybe you should rename > the library. I'm only half-kidding: if you can't use index to mean > what it usually means in the most basic computer programs, it > feels to > me like something is wrong. Well, choosing names for a library is like having a tattoo made, in so many ways --one has to live on bearing the errors of their youth. Seriously, it's not only the name of the lib, "index" is also part of some names of the API and changing those would break users' code. > > > > I need another synonim: > > ordinal, rank, situation? > > I would use ordinal if I had to pick one of those. > So we'd have iterator position(const value_type& x)const; size_type ordinal(const value_type& x)const; Isn't this a little hard to discern? Maybe the following is less confusing: iterator iterator_to(const value_type& x)const; size_type position(const value_type& x)const; Better? Joaquín M López Muñoz Teléfónica, Investigación y Desarrollo

1 0

type_traits/is_polymorphic g++ -Wall -W warnings
by Ralf W. Grosse-Kunstleve 21 Jan '06

21 Jan '06

I am in the process of cleaning up the boost tree such that we can compile all our code with g++ -Wall -W warnings. The required changes are mostly trivial, but here is one I am not sure about: .../boost/boost/type_traits/is_polymorphic.hpp:28: warning: `struct boost::detail::is_polymorphic_imp1<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >::d1' has virtual functions but non-virtual destructor .../boost/boost/type_traits/is_polymorphic.hpp:28: warning: `struct boost::detail::is_polymorphic_imp1<iotbx::detectors::Mar345Adaptor>::d1' has virtual functions but non-virtual destructor Could or should a virtual destructor be added here? Thank you in advance! Cheers, Ralf P.S.: Here is the complete warning #1: .../boost/boost/type_traits/is_polymorphic.hpp: At global scope: .../boost/boost/type_traits/is_polymorphic.hpp: In instantiation of `boost::detail::is_polymorphic_imp1<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >::d1': .../boost/boost/type_traits/is_polymorphic.hpp:56: instantiated from `boost::detail::is_polymorphic_imp1<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >' .../boost/boost/type_traits/is_polymorphic.hpp:91: instantiated from `boost::detail::is_polymorphic_imp<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >' .../boost/boost/type_traits/is_polymorphic.hpp:96: instantiated from `boost::is_polymorphic<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >' .../boost/boost/mpl/if.hpp:67: instantiated from `boost::mpl::if_<boost::is_polymorphic<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >, boost::python::objects::polymorphic_id_generator<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >, boost::python::objects::non_polymorphic_id_generator<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> > >' .../boost/boost/python/object/inheritance.hpp:65: instantiated from `boost::python::objects::dynamic_id_generator<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >' .../boost/boost/python/object/inheritance.hpp:72: instantiated from `void boost::python::objects::register_dynamic_id(T*) [with T = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>]' .../boost/boost/python/object/class_metadata.hpp:97: instantiated from `void boost::python::objects::register_shared_ptr_from_python_and_casts(T*, Bases) [with T = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, Bases = boost::python::bases<mpl_::void_, mpl_::void_>]' .../boost/boost/python/object/class_metadata.hpp:225: instantiated from `static void boost::python::objects::class_metadata<T, X1, X2, X3>::register_aux2(T2*, Callback) [with T2 = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, Callback = boost::integral_constant<bool, false>, T = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, X1 = boost::python::detail::not_specified, X2 = boost::python::detail::not_specified, X3 = boost::python::detail::not_specified]' .../boost/boost/python/object/class_metadata.hpp:219: instantiated from `static void boost::python::objects::class_metadata<T, X1, X2, X3>::register_aux(void*) [with T = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, X1 = boost::python::detail::not_specified, X2 = boost::python::detail::not_specified, X3 = boost::python::detail::not_specified]' .../boost/boost/python/object/class_metadata.hpp:205: instantiated from `static void boost::python::objects::class_metadata<T, X1, X2, X3>::register_() [with T = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, X1 = boost::python::detail::not_specified, X2 = boost::python::detail::not_specified, X3 = boost::python::detail::not_specified]' .../boost/boost/python/class.hpp:506: instantiated from `void boost::python::class_<T, X1, X2, X3>::initialize(boost::python::no_init_t) [with W = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, X1 = boost::python::detail::not_specified, X2 = boost::python::detail::not_specified, X3 = boost::python::detail::not_specified]' .../boost/boost/python/class.hpp:637: instantiated from `boost::python::class_<T, X1, X2, X3>::class_(const char*, boost::python::no_init_t) [with W = cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int>, X1 = boost::python::detail::not_specified, X2 = boost::python::detail::not_specified, X3 = boost::python::detail::not_specified]' .../cctbx/maptbx/boost_python/mapper.cpp:100: instantiated from here .../boost/boost/type_traits/is_polymorphic.hpp:28: warning: `struct boost::detail::is_polymorphic_imp1<cctbx::maptbx::mapper_factory<cctbx::maptbx::asu, double, long int> >::d1' has virtual functions but non-virtual destructor __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

Re: [boost] [multi_index] intrusive multi_index poll for interest
by JOAQUIN LOPEZ MU?Z 21 Jan '06

21 Jan '06

----- Mensaje original ----- De: David Abrahams <dave(a)boost-consulting.com> Fecha: Viernes, Enero 20, 2006 11:17 pm Asunto: Re: [boost] [multi_index] intrusive multi_index poll for interest > "JOAQUIN LOPEZ MU?Z" <joaquin(a)tid.es> writes: > [...] > > > > position() would be a perfect fit except for one thing: > > in the roadmapped ranked indices > > > > > (http://boost.org/libs/multi_index/doc/future_work.html#ranked_indices) > > > I will need another member function to return the > > position ordinal of a given element (that is, > > the inverse of operator[]), and for that "position" > > seems also a good candidate. > > IMO that should have been "index." > But "index" already has a disparate meaning in the context of Boost.MultiIndex. I need another synonim: ordinal, rank, situation? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 3

Re: [boost] [multi_index] intrusive multi_index poll for interest
by JOAQUIN LOPEZ MU?Z 21 Jan '06

21 Jan '06

----- Mensaje original ----- De: Bruno Martínez <br1(a)internet.com.uy> Fecha: Viernes, Enero 20, 2006 4:35 pm Asunto: Re: [boost] [multi_index] intrusive multi_index poll for interest > On Fri, 20 Jan 2006 05:52:22 -0200, Joaquín Mª López Muñoz > <joaquin(a)tid.es> wrote: > > > OK, you have shown a realistic scenario where the feature > > is valuable, so I'm putting this into my todo list --probably > > I can have it in time for 1.34, but I'm very slow writing and > checking> things :) Any suggestions about the name/syntax? > Something like: > > > > iterator iter_to(const value_type& x)const; > > iterator_from()? > > I don't know. I'm spanish speaking too. Pues ponemos entonces dame_el_iterador(const value_type& x); :) (sólo bromeaba, saludos desde España) > > > Alas, iterator() can't be used as the name of the member > function, since > > it is already a nested typedef of indices. > > How is this feature implemented? Substracting char*? > Nodes are derived from the following class template<typename Value> struct pod_value_holder { typename aligned_storage< sizeof(Value), alignment_of<Value>::value >::type space; }; where "space" is used to hold the value (guaranteed to serve this purpose by TR1). Given a value_type*, we are allowed to cast it to a aligned_storage<...>* (TR1) and then to a pod_value_holder<value_type>* (std 9.2.17). From here we only need a static_cast to downcast to a node_type* (nodes are derived from pod_value_holder). And indices only need such node_type* to make an iterator. Briefly put, nodes store the value field in their first position, and a careful leverage of aligned_storage<>, POD guarantees and downcasting allows us to *portably* convert a pointer to the value to a pointer to the whole node. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 3