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

Re: [boost] Interest in a flyweight library?
by JOAQUIN LOPEZ MU?Z 03 Jul '06

03 Jul '06

----- Mensaje original ----- De: "Steven E. Harris" <seh(a)panix.com> Fecha: Viernes, Junio 30, 2006 7:32 pm Asunto: Re: [boost] Interest in a flyweight library? > Joaquín Mª López Muñoz <joaquin(a)tid.es> writes: > > > Anyway, naming discussions aside, do you see value in such a thing > > being elaborated and eventually proposed to Boost? > > From my brief examination of the implementation and examples > provided,yes, it looks useful. I have no qualms with the idea and > I have full confidence you'll implement it well. > However, I don't think you should > cast the naming problem aside as immaterial. Of course naming issues are important, excuse me if I gave the impression I was belittling your concern. Only that in these preliminary stage I want to gauge people's interest in the stuff, regardless of final names [...] > We're both arguing that there's prior art here to justify the > name. Your implementation includes both a reference mechanism and a > pooling mechanism. "Flyweight" describes the former, but the pattern, > at least by my reading, doesn't speak to comparing candidate instances > and ensuring that there are no duplicates in the pool. That > duplicate-avoidance policy is specifically addressed by interning. I do think the pattern also includes the interning thing, but of cours our readings can differ. I must say in support of your terminology that "flyweight" also covers some aspects I'm uneasy about, namely the intrinsic/extrinsic stuff, which my lib proposal does not endorse nor facilitate --and which I'm not fond of either BTW. > My concern is that I might overlook this library because its name does > not capture what I would value about it most. Clearly I have biases, > having been exposed to the "intern" terminology for years, so perhaps > we can hear from others as to whether the name is appropriate. Yes, this would be good. At the time of my writing this seems like some more people are supporting the intern terminology. It'd be great if name proposals cover these three: lib name/namespace name/main facility So, you'd be supporting something like Boost.Intern / boost::intern / boost::interned<> right? > -- > Steven E. Harris Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

my complaint on asynchronous programming, and my suggestion on coroutine
by 李慧霸 03 Jul '06

03 Jul '06

I have used the recent asio library in my small project, the project is successful, but I think debuging the asynchronous code was a nightmare. I am a programmer of 13 years, I have taken part in ACM/ICPC Asia regional contest many times, I take myself as a skillful programmer, but I found it difficult to write asynchronous programme. I believe many other people have the same feeling with me. Asynchronous program have to pass many state data between different operations, so it is bothering to implement, and it is difficult to debug(due to the loss of many other information), and the most important, it conflicts with normal thinking habit of straight line code. I have been considering this problem for a period of time, and I find a approach that looks better. The basic idea is to utilize coroutine to simulate a logically synchronized program in the upper layer, and maintain the asynchronous model in the lower layer, using the completion callback to do coroutine switch. This approach is as efficient as asynchronous model in performance, and is also as simple (to use) as the synchronized approach. With this approach, we can imagine a programe using boost::asio like this: void foo() { boost::asio::ipv4::host_resolver resolver(demuxer); boost::asio::ipv4::host host; resolver.get_host_by_name(host, "www.sohu.com"); boost::asio::ipv4::tcp::endpoint addr(80, host.address(0)); boost::asio::stream_socket sock(demuxer); sync_connect(sock, addr); //using asynchronous IO model in the underlying layer static char request[]="GET /\r\n\r\n"; //using asynchronous IO model in the underlying layer size_t sw=sync_write(sock, boost::asio::buffer(request, sizeof(request)-1)); char buf[10*1024]; //using asynchronous IO model in the underlying layer size_t sr=sync_read(sock, boost::asio::buffer(buf)); buf[sr]=0; cout<<buf<<endl; } I have tried to implement this feature on windows using fiber, but it's not portable at all. So I suggest boost implement a coroutine library, so that this asynchronous model would come true.

2 1

[bug?] boost::format and user locale
by Olaf Krzikalla 03 Jul '06

03 Jul '06

Hi, I had to use a user-defined locale with boost::format and had to add the following lines: version: 1.33.0 file: format/feed_args.hpp function: put 133 basic_oaltstringstream<Ch, Tr, Alloc> oss( &buf); 134 specs.fmtstate_.apply_on(oss, loc_p); 133 basic_oaltstringstream<Ch, Tr, Alloc> oss( &buf); + if (loc_p) + { + oss.imbue (*loc_p); + } 134 specs.fmtstate_.apply_on(oss, loc_p); I'm not sure if this is the right fix nor I am sure, if there are other uses of basic_oaltstringstream, which need to be fixed. At least for me it works after that change. Best regards Olaf Krzikalla

1 0

problems using build 2
by Arkadiy Vertleyb 03 Jul '06

03 Jul '06

Hi, If I understand correctly, regression tests are now run using build 2. I would also like to use it, but I am getting an error (see below). Jamfile.v2 was created by Vladimir Prus some time ago, and apparently works fine for regressions. What's wrong with my setup? Regards, Arkadiy C:\ark\boost-cvs\boost\libs\typeof\test>bjam --v2 --debug-generators 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 (and if you don't know what ICU is then you probably don't need it). warning: no toolsets are configured. warning: you won't be able to build C++ programs. warning: please consult the documentation at warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html *** construct COMPILE from { data_member.cpp.CPP } properties: <asynch-exceptions>off <debug-symbols>on <define>BOOST_ALL_ NO_LIB=1 <define>BOOST_TYPEOF_COMPLIANT <exception-handling>on <extern-c-nothrow >off <hardcode-dll-paths>true <include>../../.. <inlining>off <install-dependenc ies>off <link>shared <location-prefix>data_member_emulation.test <main-target-ty pe>COMPILE <optimization>off <os>NT <profiling>off <rtti>on <runtime-debugging>o n <runtime-link>shared <stdlib>native <symlink-location>project-relative <tag>@J amfile</C:/ark/boost-cvs/boost>%Jamfile</C:/ark/boost-cvs/boost>.tag <threading> single <user-interface>console <variant>debug <warnings-as-errors>off <warnings> on find-viable-generators target-type= COMPILE property-set= debug trying type COMPILE there are generators for this type trying generator testing.expect-success ( OBJ -> COMPILE ) is viable *** 1 viable generators ** generator 'testing.expect-success' pruned error: unable to construct ./data_member_emulation find-viable-generators target-type= COMPILE property-set= debug trying type COMPILE there are generators for this type trying generator testing.expect-success ( OBJ -> COMPILE ) is viable To debug this problem, try the --debug-generators option.

2 1

Re: [boost] [RC_1_34_0] MSVC 8.0 link looking for lib*
by Reece Dunn 03 Jul '06

03 Jul '06

Rene Rivera wrote: > Reece Dunn wrote: > > BBv2 also chokes when doing: > > > > bjam --v2 install msvc-7.1 link=static,shared > > > > I have posted this (with a proposed solution several times), but haven't > > had a response. > > Yea, noticed :-) Just hadn't had a chance to think about it yet. No worries, I was just ensuring that it didn't get lost. > > (1) The stage.jam tag rule doesn't propagate the <rtti> option which > > Boost.Wave turns of, causing a duplicate target for Boost.FileSystem. > > Adding 'r' for rtti=on solves this issue. This will produce: > > > > boost_filesystem-vc71-gd-r.lib > > boost_filesystem-vc71-gd.lib > > I don't think this is the right solution for this problem. Although it > might be a solution for people who turn off rtti overall. If I remember > from previous discussions we don't want to encourage turning off what > are supposed to be standard features of the language. And for that > matter have to test such variants. There's also the problem of changing > the auto-link code to account for these new names. So it's not just a > matter of changing the jam code. That means that since we are not adding > new features to code anymore we can't change the auto-link code to > account for those new names. I agree. > Personally I think turning off rtti for the whole wave library to > workaround a vc71 bug is the wrong solution, read that as it's a kludge. > So I would consider it a bug in wave that needs to get fixed. Something needs to be done, because BBv2 is choking when installing for msvc-7.1. Also, there is nothing (apart from BBv2 generating a duplicate target error ;)) stopping someone from saying: bjam --v2 install msvc-7.1 rtti=on,off I agree with what you are saying above about auto-link, testing, etc., however the BBv2 toolset doesn't stop a user from doing this. How does BBv1 solve this with respect to wave/filesystem? Can you install both rtti-on and rtti-off with BBv1? If you can, this needs to be supported in V2. I don't have any answers for this :(. > > (2) Again in the stage rule, link=shared generates an IMPORT_LIB > > target that conflicts with the STATIC_LIB target generated by > > link=static. Adding 'i' or '-imp' for IMPORT_LIB fixes this issue. > > This I will fix by making it behave as BBv1 does, and what is > documented, and what the auto-link code expects of using the "lib" prefix. Great! - Reece _________________________________________________________________ Be one of the first to try Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-49…

3 3

[filter_iterator] Why do filter_iterator constructors use default parameter values?
by Jurko Gospodneti� 02 Jul '06

02 Jul '06

Hi all. I was wondering why filter_iterator constructors allow default parameter values? More precisely, if the end iterator parameter is not given then the constructor silently uses a default generated iterator as its internal end iterator. This interface seems dangerous to me and has caused us one hard-to-track-down bug... because the filter_iterator silently used an incorrect end iterator and so sometimes managed to iterate passed the end of its container... causing of course all sorts of cute behaviour... :-) (access violations, random API call failures, gibberish values read through the iterator...) The failures themselves were also random enough to make tracking this baby down a real pain in the behind... :-) Now we are bigger & wiser, but I was still wandering what the rationale was for using this interface? Why not simply make the end iterator parameter be mandatory? That would make it explicitly clear to the novice user that he needs to specify the end iterator. If there actually is some reason for implementing filter_iterators this way, could someone add a warning or a rationale explanation regarding this in the official documentation? Hope this helps... Best regards, Jurko Gospodnetiæ

1 0

Re: [boost] [RC_1_34_0] MSVC 8.0 link looking for lib*
by Reece Dunn 02 Jul '06

02 Jul '06

Rene Rivera wrote: > It's yet another discrepancy between the BBv1 and BBv2 build files. > Which I guess I'll have to fix. Incidentally I had also just noticed > that problem when I was trying to solve the first discrepancy :-) BBv2 also chokes when doing: bjam --v2 install msvc-7.1 link=static,shared I have posted this (with a proposed solution several times), but haven't had a response. The problem is two-fold: (1) The stage.jam tag rule doesn't propagate the <rtti> option which Boost.Wave turns of, causing a duplicate target for Boost.FileSystem. Adding 'r' for rtti=on solves this issue. This will produce: boost_filesystem-vc71-gd-r.lib boost_filesystem-vc71-gd.lib (2) Again in the stage rule, link=shared generates an IMPORT_LIB target that conflicts with the STATIC_LIB target generated by link=static. Adding 'i' or '-imp' for IMPORT_LIB fixes this issue. This will produce (with rtti=on above): boost_filesystem-vc71-gd-ri.lib boost_filesystem-vc71-gd-r.dll or boost_filesystem-vc71-gd-r-imp.lib boost_filesystem-vc71-gd-r.dll However, before committing the patch (available from by "bjam install issues" post) I want to see if this is the right solution. - Reece _________________________________________________________________ Be one of the first to try Windows Live Mail. http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-49…

3 5

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

02 Jul '06

Boost Regression test failures Report time: 2006-07-02T09:52:42Z 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… The following platforms have a large number of failures: vc-6_5-stlport 689 failures in 57 libraries (451 are from non-broken platforms) algorithm/minmax (0 of 2 failures are from non-broken platforms) algorithm/string (1) any (0 of 1 failures are from non-broken platforms) array (0 of 3 failures are from non-broken platforms) assign (0 of 7 failures are from non-broken platforms) bind (0 of 17 failures are from non-broken platforms) concept_check (1) config (0 of 5 failures are from non-broken platforms) conversion (0 of 4 failures are from non-broken platforms) crc (0 of 1 failures are from non-broken platforms) date_time (5) disjoint_sets (0 of 1 failures are from non-broken platforms) dynamic_bitset (0 of 3 failures are from non-broken platforms) filesystem (2 of 7 failures are from non-broken platforms) foreach (0 of 10 failures are from non-broken platforms) format (0 of 4 failures are from non-broken platforms) function (0 of 8 failures are from non-broken platforms) functional (0 of 1 failures are from non-broken platforms) functional/hash (0 of 22 failures are from non-broken platforms) graph (9) integer (2 of 5 failures are from non-broken platforms) io (1) iostreams (39 of 67 failures are from non-broken platforms) iterator (0 of 14 failures are from non-broken platforms) lambda (1) logic (0 of 2 failures are from non-broken platforms) math (1 of 5 failures are from non-broken platforms) mpl (6 of 11 failures are from non-broken platforms) multi_array (0 of 14 failures are from non-broken platforms) multi_index (0 of 20 failures are from non-broken platforms) numeric/conversion (4 of 6 failures are from non-broken platforms) numeric/interval (1) numeric/ublas (8) optional (0 of 4 failures are from non-broken platforms) parameter (25 of 38 failures are from non-broken platforms) pool (2) program_options (9) property_map (0 of 1 failures are from non-broken platforms) python (21 of 87 failures are from non-broken platforms) random (1) range (1 of 9 failures are from non-broken platforms) rational (3 of 5 failures are from non-broken platforms) regex (0 of 32 failures are from non-broken platforms) serialization (29 of 44 failures are from non-broken platforms) signals (10 of 15 failures are from non-broken platforms) smart_ptr (0 of 11 failures are from non-broken platforms) spirit (1) static_assert (0 of 2 failures are from non-broken platforms) test (1 of 15 failures are from non-broken platforms) thread (0 of 16 failures are from non-broken platforms) tokenizer (0 of 6 failures are from non-broken platforms) tr1 (48) tuple (0 of 2 failures are from non-broken platforms) type_traits (0 of 43 failures are from non-broken platforms) typeof (5 of 8 failures are from non-broken platforms) utility (1 of 13 failures are from non-broken platforms) variant (0 of 10 failures are from non-broken platforms) Test failures marked with a (*) represent tests that failed on platforms that are considered broken. They are likely caused by misconfiguration by the regression tester or a failure in a core library such as Test or Config. |algorithm/minmax| minmax: vc-6_5-stlport* minmax_element: vc-6_5-stlport* |algorithm/string| replace: vc-7_1-stlport |any| any_test: vc-6_5-stlport* |array| array1: vc-6_5-stlport* array2: vc-6_5-stlport* array5: vc-6_5-stlport* |assign| basic: vc-6_5-stlport* email_example: vc-6_5-stlport* list_inserter: vc-6_5-stlport* list_of_workaround: vc-6_5-stlport* my_vector_example: vc-6_5-stlport* static_list_of: vc-6_5-stlport* std: vc-6_5-stlport* |bind| bind_const_test: vc-6_5-stlport* bind_cv_test: vc-6_5-stlport* bind_dm_test: vc-6_5-stlport* bind_eq_test: vc-6_5-stlport* bind_function_test: vc-6_5-stlport* bind_lookup_problem_test: vc-6_5-stlport* bind_not_test: vc-6_5-stlport* bind_rel_test: vc-6_5-stlport* bind_rv_sp_test: vc-6_5-stlport* bind_stateful_test: vc-6_5-stlport* bind_test: vc-6_5-stlport* bind_visit_test: vc-6_5-stlport* mem_fn_derived_test: vc-6_5-stlport* mem_fn_eq_test: vc-6_5-stlport* mem_fn_rv_test: vc-6_5-stlport* mem_fn_test: vc-6_5-stlport* mem_fn_void_test: vc-6_5-stlport* |concept_check| class_concept_check_test: vc-7_1-stlport |config| abi_test: vc-6_5-stlport* config_info: vc-6_5-stlport* config_link_test: vc-6_5-stlport* config_test: vc-6_5-stlport* math_info: vc-6_5-stlport* |conversion| cast_test: vc-6_5-stlport* implicit_cast: vc-6_5-stlport* lexical_cast_test: vc-6_5-stlport* numeric_cast_test: vc-6_5-stlport* |crc| crc_test: vc-6_5-stlport* |date_time| testdate_facet_new: vc-7_1-stlport testdate_facet_new_dll: vc-7_1-stlport testdate_input_facet: vc-7_1-stlport testdate_input_facet_dll: vc-7_1-stlport testwposix_time_zone: vc-7_1-stlport |disjoint_sets| disjoint_set_test: vc-6_5-stlport* |dynamic_bitset| dyn_bitset_unit_tests2: vc-6_5-stlport* dyn_bitset_unit_tests3: vc-6_5-stlport* dyn_bitset_unit_tests4: vc-6_5-stlport* |filesystem| convenience_test: vc-6_5-stlport* fstream_test: vc-6_5-stlport* large_file_support_test: vc-6_5-stlport* operations_test: vc-7_1-stlport operations_test_dll: vc-7_1-stlport path_test: vc-6_5-stlport* path_test_dll: vc-6_5-stlport* |foreach| array_byref: vc-6_5-stlport* array_byval: vc-6_5-stlport* call_once: vc-6_5-stlport* cstr_byref: vc-6_5-stlport* cstr_byval: vc-6_5-stlport* dependent_type: vc-6_5-stlport* pair_byref: vc-6_5-stlport* pair_byval: vc-6_5-stlport* stl_byref: vc-6_5-stlport* stl_byval: vc-6_5-stlport* |format| format_test1: vc-6_5-stlport* format_test2: vc-6_5-stlport* format_test3: vc-6_5-stlport* format_test_wstring: vc-6_5-stlport* |function| contains2_test: vc-6_5-stlport* function_arith_portable: vc-6_5-stlport* function_n_test: vc-6_5-stlport* function_ref_portable: vc-6_5-stlport* mem_fun_portable: vc-6_5-stlport* stateless_test: vc-6_5-stlport* std_bind_portable: vc-6_5-stlport* sum_avg_portable: vc-6_5-stlport* |functional| function_test: vc-6_5-stlport* |functional/hash| container_fwd_test: vc-6_5-stlport* hash_built_in_array_test: vc-6_5-stlport* hash_custom_test: vc-6_5-stlport* hash_deque_test: vc-6_5-stlport* hash_float_test: vc-6_5-stlport* hash_friend_test: vc-6_5-stlport* hash_fwd_test_1: vc-6_5-stlport* hash_fwd_test_2: vc-6_5-stlport* hash_global_namespace_test: vc-6_5-stlport* hash_list_test: vc-6_5-stlport* hash_map_test: vc-6_5-stlport* hash_no_ext_macro_1: vc-6_5-stlport* hash_no_ext_macro_2: vc-6_5-stlport* hash_number_test: vc-6_5-stlport* hash_pointer_test: vc-6_5-stlport* hash_range_test: vc-6_5-stlport* hash_set_test: vc-6_5-stlport* hash_string_test: vc-6_5-stlport* hash_vector_test: vc-6_5-stlport* link_ext_test: vc-6_5-stlport* link_test: vc-6_5-stlport* portable: vc-6_5-stlport* |graph| adjacency_matrix_test: vc-7_0 bidir_remove_edge: vc-7_0 csr_graph_test: msvc-8.0 msvc-8.0 vc-7_0 dominator_tree_test: vc-7_0 graphviz_test: qcc-3.3.5_gpp vc-7_1-stlport matching_test: vc-7_0 |integer| cstdint_test: vc-6_5-stlport* integer_test: vc-6_5-stlport* integer_traits_test: qcc-3.3.5_gpp qcc-3.3.5_gpp vc-6_5-stlport* |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| array_test: vc-6_5 vc-6_5-stlport* auto_close_test: vc-6_5 vc-6_5-stlport* buffer_size_test: vc-6_5 vc-6_5-stlport* bzip2_test: msvc-7.1 msvc-8.0 code_converter_test: vc-6_5 vc-6_5-stlport* component_access_test: vc-6_5 vc-6_5-stlport* compose_test: borland-5_6_4 vc-6_5 vc-6_5-stlport* copy_test: vc-6_5 vc-6_5-stlport* counter_test: vc-6_5 vc-6_5-stlport* direct_adapter_test: vc-6_5 vc-6_5-stlport* example_test: vc-6_5 vc-6_5-stlport* file_descriptor_test: vc-6_5 vc-6_5-stlport* file_test: vc-6_5 vc-6_5-stlport* filtering_stream_test: vc-6_5 vc-6_5-stlport* vc-7_1-stlport finite_state_filter_test: cw-9.4 flush_test: vc-6_5 vc-6_5-stlport* gzip_test: msvc-7.1 msvc-8.0 invert_test: vc-6_5 vc-6_5-stlport* line_filter_test: vc-6_5 vc-6_5-stlport* vc-7_1-stlport mapped_file_test: vc-6_5 vc-6_5-stlport* newline_test: vc-6_5 vc-6_5-stlport* null_test: vc-6_5 vc-6_5-stlport* pipeline_test: vc-6_5 vc-6_5-stlport* positioning_test: vc-6_5 vc-6_5-stlport* regex_filter_test: vc-6_5 vc-6_5-stlport* restrict_test: vc-6_5 vc-6_5-stlport* seekable_file_test: vc-6_5 seekable_filter_test: vc-6_5 vc-6_5-stlport* stdio_filter_test: vc-6_5 vc-6_5-stlport* symmetric_filter_test: vc-6_5 vc-6_5-stlport* tee_test: vc-6_5 vc-6_5-stlport* wide_stream_test: vc-6_5 vc-6_5-stlport* zlib_test: msvc-7.1 msvc-8.0 |iterator| concept_tests: vc-6_5-stlport* counting_iterator_test: vc-6_5-stlport* filter_iterator_test: vc-6_5-stlport* indirect_iterator_test: vc-6_5-stlport* interoperable: vc-6_5-stlport* iterator_adaptor_cc: vc-6_5-stlport* iterator_adaptor_test: vc-6_5-stlport* iterator_facade: vc-6_5-stlport* iterator_traits_test: vc-6_5-stlport* permutation_iterator_test: vc-6_5-stlport* reverse_iterator_test: vc-6_5-stlport* transform_iterator_test: vc-6_5-stlport* unit_tests: vc-6_5-stlport* zip_iterator_test: vc-6_5-stlport* |lambda| member_pointer_test: qcc-3.3.5_cpp |logic| tribool_rename_test: vc-6_5-stlport* tribool_test: vc-6_5-stlport* |math| common_factor_test: vc-6_5-stlport* hypot_test: vc-6_5-stlport* log1p_expm1_test: vc-6_5-stlport* quaternion_mult_incl_test: vc-6_5-stlport* special_functions_test: vc-7_1-stlport |mpl| apply: gcc-4.1.0_linux_x86_64 bool: vc-6_5-stlport* for_each: vc-6_5-stlport* int: vc-6_5-stlport* integral_c: vc-6_5-stlport* multiset: gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4_0_3_tru64 size_t: vc-6_5-stlport* |multi_array| access: vc-6_5-stlport* assign: vc-6_5-stlport* assign_to_array: vc-6_5-stlport* compare: vc-6_5-stlport* constructors: vc-6_5-stlport* idxgen1: vc-6_5-stlport* index_bases: vc-6_5-stlport* iterators: vc-6_5-stlport* range1: vc-6_5-stlport* reshape: vc-6_5-stlport* resize: vc-6_5-stlport* slice: vc-6_5-stlport* stl_interaction: vc-6_5-stlport* storage_order: vc-6_5-stlport* |multi_index| test_basic: vc-6_5-stlport* test_capacity: vc-6_5-stlport* test_comparison: vc-6_5-stlport* test_composite_key: vc-6_5-stlport* test_conv_iterators: vc-6_5-stlport* test_copy_assignment: vc-6_5-stlport* test_hash_ops: vc-6_5-stlport* test_iterators: vc-6_5-stlport* test_key_extractors: vc-6_5-stlport* test_list_ops: vc-6_5-stlport* test_modifiers: vc-6_5-stlport* test_mpl_ops: vc-6_5-stlport* test_observers: vc-6_5-stlport* test_projection: vc-6_5-stlport* test_range: vc-6_5-stlport* test_rearrange: vc-6_5-stlport* test_safe_mode: vc-6_5-stlport* test_set_ops: vc-6_5-stlport* test_special_set_ops: vc-6_5-stlport* test_update: vc-6_5-stlport* |numeric/conversion| bounds_test: vc-6_5-stlport* converter_test: borland-5_8_2 traits_test: borland-5_8_2 vc-6_5-stlport* 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 test6: vc-7_1-stlport |optional| optional_test: vc-6_5-stlport* optional_test_inplace: vc-6_5-stlport* optional_test_io: vc-6_5-stlport* optional_test_tie: vc-6_5-stlport* |parameter| basics: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* duplicates: borland-5_6_4 borland-5_8_2 earwicker: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* efficiency: vc-6_5-stlport* macros: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* maybe: vc-6_5 vc-6_5-stlport* vc-7_0 mpl: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* preprocessor: borland-5_6_4 borland-5_8_2 vc-6_5 vc-6_5-stlport* python-parameter-test: vc-6_5 vc-6_5-stlport* vc-7_0 sfinae: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* singular: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* tutorial: vc-6_5-stlport* unnamed: borland-5_6_4 borland-5_8_2 vc-6_5-stlport* unnamed_fail: vc-6_5 vc-6_5-stlport* vc-7_0 |pool| test_pool_alloc: qcc-3.3.5_cpp qcc-3.3.5_cpp |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 |property_map| dynamic_properties_test: vc-6_5-stlport* |python| andreas_beyer: vc-6_5-stlport* args: vc-6_5-stlport* auto_ptr: vc-6_5-stlport* back_reference: vc-6_5-stlport* bases: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux vc-6_5-stlport* ben_scott1: vc-6_5-stlport* bienstman1: vc-6_5-stlport* bienstman2: vc-6_5-stlport* bienstman3: vc-6_5-stlport* builtin_converters: vc-6_5-stlport* callbacks: vc-6_5-stlport* const_argument: vc-6_5-stlport* crossmod_exception: vc-6_5-stlport* data_members: vc-6_5-stlport* defaults: vc-6_5-stlport* destroy_test: vc-6_5-stlport* dict: vc-6_5-stlport* docstring: vc-6_5-stlport* enum: vc-6_5-stlport* exception_translator: vc-6_5-stlport* exec: cw-9.4 gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux msvc-8.0 qcc-3.3.5_cpp qcc-3.3.5_gpp vc-6_5-stlport* extract: vc-6_5-stlport* if_else: vc-6_5-stlport* implicit: vc-6_5-stlport* injected: vc-6_5-stlport* iterator: vc-6_5-stlport* keywords: vc-6_5-stlport* list: vc-6_5-stlport* long: vc-6_5-stlport* map_indexing_suite: vc-6_5-stlport* minimal: vc-6_5-stlport* multi_arg_constructor: vc-6_5-stlport* nested: vc-6_5-stlport* numpy: vc-6_5-stlport* object: vc-6_5-stlport* opaque: vc-6_5-stlport* operators: vc-6_5-stlport* pearu1: vc-6_5-stlport* pickle1: vc-6_5-stlport* pickle2: vc-6_5-stlport* pickle3: vc-6_5-stlport* pickle4: vc-6_5-stlport* pointee: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux vc-6_5-stlport* pointer_type_id_test: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux vc-6_5-stlport* pointer_vector: vc-6_5-stlport* polymorphism: vc-6_5-stlport* polymorphism2: vc-6_5-stlport* polymorphism2_auto_ptr: vc-6_5-stlport* properties: vc-6_5-stlport* raw_ctor: vc-6_5-stlport* result: vc-6_5-stlport* return_arg: vc-6_5-stlport* select_from_python_test: qcc-3.3.5_cpp qcc-3.3.5_gpp vc-6_5-stlport* shared_ptr: vc-6_5-stlport* slice: vc-6_5-stlport* staticmethod: vc-6_5-stlport* stl_iterator: vc-6_5-stlport* str: vc-6_5-stlport* test_pointer_adoption: vc-6_5-stlport* try: vc-6_5-stlport* tuple: vc-6_5-stlport* upcast: gcc-3.2.3_linux gcc-3.3.6_linux gcc-3.4.5_linux vc-6_5-stlport* vector_indexing_suite: vc-6_5-stlport* virtual_functions: vc-6_5-stlport* voidptr: vc-6_5-stlport* wrapper_held_type: vc-6_5-stlport* |random| random_test: intel-linux-9.0 |range| algorithm_example: vc-6_5-stlport* array: vc-6_5-stlport* const_ranges: vc-6_5-stlport* iterator_pair: vc-6_5-stlport* partial_workaround: vc-6_5-stlport* reversible_range: vc-6_5-stlport* std_container: vc-6_5-stlport* string: vc-6_5-stlport* sub_range: vc-7_1-stlport |rational| rational_example: vc-6_5-stlport* rational_test: borland-5_6_4 vc-6_5 vc-6_5-stlport* vc-7_0 |regex| bad_expression_test: vc-6_5-stlport* captures_example: vc-6_5-stlport* captures_test: vc-6_5-stlport* collate_info: vc-6_5-stlport* credit_card_example: vc-6_5-stlport* icu_example: vc-6_5-stlport* mfc_example: vc-6_5-stlport* object_cache_test: vc-6_5-stlport* partial_regex_grep: vc-6_5-stlport* partial_regex_match: vc-6_5-stlport* posix_api_check: vc-6_5-stlport* posix_api_check_cpp: vc-6_5-stlport* recursion_test: vc-6_5-stlport* regex_config_info: vc-6_5-stlport* regex_dll_config_info: vc-6_5-stlport* regex_grep_example_1: vc-6_5-stlport* regex_grep_example_2: vc-6_5-stlport* regex_grep_example_3: vc-6_5-stlport* regex_iterator_example: vc-6_5-stlport* regex_match_example: vc-6_5-stlport* regex_merge_example: vc-6_5-stlport* regex_regress: vc-6_5-stlport* regex_regress_dll: vc-6_5-stlport* regex_replace_example: vc-6_5-stlport* regex_search_example: vc-6_5-stlport* regex_split_example_1: vc-6_5-stlport* regex_split_example_2: vc-6_5-stlport* regex_token_iterator_eg_1: vc-6_5-stlport* regex_token_iterator_eg_2: vc-6_5-stlport* static_mutex_test: vc-6_5-stlport* unicode_iterator_test: vc-6_5-stlport* wide_posix_api_check_cpp: vc-6_5-stlport* |serialization| test_codecvt_null: qcc-3.3.5_gpp qcc-3.3.5_gpp test_demo_portable_archive_dll: vc-6_5 test_demo_shared_ptr: vc-7_1-stlport test_deque_xml_archive_dll: mingw-3_4_2 test_inclusion: vc-6_5-stlport* test_iterators: vc-6_5-stlport* test_iterators_base64: vc-6_5-stlport* test_non_default_ctor2_text_archive: 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 test_non_default_ctor2_text_warchive: 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 test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_shared_ptr_132_binary_archive: vc-6_5-stlport* test_shared_ptr_132_text_archive: vc-6_5-stlport* test_shared_ptr_132_text_warchive: vc-6_5-stlport* test_shared_ptr_132_xml_archive: vc-6_5-stlport* test_shared_ptr_132_xml_warchive: vc-6_5-stlport* test_shared_ptr_xml_warchive_dll: gcc-4.1.0_linux_x86_64 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_smart_cast: vc-6_5-stlport* test_static_warning: vc-6_5-stlport* test_utf8_codecvt: qcc-3.3.5_gpp qcc-3.3.5_gpp test_variant_binary_archive: vc-6_5-stlport* test_variant_text_archive: vc-6_5-stlport* test_variant_text_warchive: vc-6_5-stlport* test_variant_xml_archive: borland-5_8_2 vc-6_5-stlport* test_variant_xml_archive_dll: borland-5_8_2 test_variant_xml_warchive: borland-5_8_2 vc-6_5-stlport* test_variant_xml_warchive_dll: borland-5_8_2 test_vector_text_archive: gcc-3.4.5_linux_x86_64 test_vector_text_archive_dll: gcc-3.4.5_linux_x86_64 |signals| dead_slot_test: gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp vc-6_5-stlport* deletion_test: vc-6_5-stlport* ordering_test: vc-6_5-stlport* signal_n_test: vc-6_5-stlport* trackable_test: gcc-3.3.6_linux qcc-3.3.5_cpp qcc-3.3.5_cpp qcc-3.3.5_gpp qcc-3.3.5_gpp vc-6_5-stlport* |smart_ptr| atomic_count_test: vc-6_5-stlport* auto_ptr_rv_test: vc-6_5-stlport* get_deleter_test: vc-6_5-stlport* intrusive_ptr_test: vc-6_5-stlport* lw_mutex_test: vc-6_5-stlport* pointer_cast_test: vc-6_5-stlport* shared_from_this_test: vc-6_5-stlport* shared_ptr_basic_test: vc-6_5-stlport* shared_ptr_test: vc-6_5-stlport* smart_ptr_test: vc-6_5-stlport* weak_ptr_test: vc-6_5-stlport* |spirit| scanner_value_type_tests: intel-linux-9.0 |static_assert| static_assert_example_2: vc-6_5-stlport* static_assert_test: vc-6_5-stlport* |test| algorithms_test: vc-6_5-stlport* basic_cstring_test: vc-6_5-stlport* boost_check_equal_str: vc-6_5-stlport* class_properties_test: vc-6_5-stlport* errors_handling_test: vc-6_5-stlport* fixed_mapping_test: vc-6_5-stlport* foreach_test: vc-6_5-stlport* ifstream_line_iterator_test: vc-6_5-stlport* online_test: vc-6_5-stlport* output_test_stream_test: vc-6_5-stlport* parameterized_test_test: vc-6_5 vc-6_5-stlport* result_report_test: vc-6_5-stlport* test_case_template_test: vc-6_5-stlport* test_tools_test: vc-6_5-stlport* |thread| test_barrier: vc-6_5-stlport* test_barrier_lib: vc-6_5-stlport* test_condition: vc-6_5-stlport* test_condition_lib: vc-6_5-stlport* test_mutex: vc-6_5-stlport* test_mutex_lib: vc-6_5-stlport* test_once: vc-6_5-stlport* test_once_lib: vc-6_5-stlport* test_read_write_mutex: vc-6_5-stlport* test_read_write_mutex_lib: vc-6_5-stlport* test_thread: vc-6_5-stlport* test_thread_lib: vc-6_5-stlport* test_tss: vc-6_5-stlport* test_tss_lib: vc-6_5-stlport* test_xtime: vc-6_5-stlport* test_xtime_lib: vc-6_5-stlport* |tokenizer| examples: vc-6_5-stlport* simple_example_1: vc-6_5-stlport* simple_example_2: vc-6_5-stlport* simple_example_3: vc-6_5-stlport* simple_example_4: vc-6_5-stlport* simple_example_5: vc-6_5-stlport* |tr1| run_complex_overloads: vc-7_0 run_random: vc-7_0 std_run_complex_overloads: vc-7_0 std_run_random: vc-7_0 std_test_array: vc-7_0 std_test_array_tricky: vc-7_0 std_test_bind: vc-7_0 std_test_complex: vc-7_0 std_test_function: vc-7_0 std_test_hash: qcc-3.3.5_gpp qcc-3.3.5_gpp std_test_random: vc-7_0 std_test_reference_wrapper: vc-7_0 std_test_regex: vc-7_0 std_test_result_of: vc-7_0 std_test_shared_ptr: vc-7_0 std_test_tuple: vc-7_0 std_test_tuple_tricky: vc-7_0 std_test_type_traits: vc-7_0 test_array: vc-7_0 test_array_tricky: vc-7_0 test_bind: vc-7_0 test_boost: vc-7_1-stlport test_complex: vc-7_0 test_function: vc-7_0 test_hash: qcc-3.3.5_gpp qcc-3.3.5_gpp vc-7_1-stlport test_random: vc-7_0 vc-7_1-stlport test_reference_wrapper: vc-7_0 test_regex: vc-7_0 vc-7_1-stlport test_result_of: vc-7_0 test_shared_ptr: vc-7_0 test_tuple: vc-7_0 test_tuple_tricky: vc-7_0 test_type_traits: vc-7_0 tr1_aligned_storage_test: vc-7_0 tr1_is_array_test: vc-7_0 tr1_is_const_test: vc-7_0 tr1_is_floating_point_test: vc-7_0 tr1_is_integral_test: vc-7_0 tr1_is_reference_test: vc-7_0 tr1_is_void_test: vc-7_0 tr1_is_volatile_test: vc-7_0 tr1_tricky_function_type_test: vc-7_0 tr1_tricky_partial_spec_test: vc-7_0 |tuple| io_test: vc-6_5-stlport* tuple_test_bench: vc-6_5-stlport* |type_traits| add_const_test: vc-6_5-stlport* add_cv_test: vc-6_5-stlport* add_pointer_test: vc-6_5-stlport* add_reference_test: vc-6_5-stlport* add_volatile_test: vc-6_5-stlport* aligned_storage_test: vc-6_5-stlport* alignment_of_test: vc-6_5-stlport* has_nothrow_assign_test: vc-6_5-stlport* has_nothrow_constr_test: vc-6_5-stlport* has_nothrow_copy_test: vc-6_5-stlport* has_trivial_assign_test: vc-6_5-stlport* has_trivial_constr_test: vc-6_5-stlport* has_trivial_copy_test: vc-6_5-stlport* has_trivial_destructor_test: vc-6_5-stlport* has_virtual_destructor_test: vc-6_5-stlport* is_arithmetic_test: vc-6_5-stlport* is_base_and_derived_test: vc-6_5-stlport* is_base_of_test: vc-6_5-stlport* is_class_test: vc-6_5-stlport* is_compound_test: vc-6_5-stlport* is_convertible_test: vc-6_5-stlport* is_enum_test: vc-6_5-stlport* is_float_test: vc-6_5-stlport* is_floating_point_test: vc-6_5-stlport* is_function_test: vc-6_5-stlport* is_fundamental_test: vc-6_5-stlport* is_integral_test: vc-6_5-stlport* is_member_func_test: vc-6_5-stlport* is_member_obj_test: vc-6_5-stlport* is_member_pointer_test: vc-6_5-stlport* is_object_test: vc-6_5-stlport* is_pod_test: vc-6_5-stlport* is_pointer_test: vc-6_5-stlport* is_polymorphic_test: vc-6_5-stlport* is_same_test: vc-6_5-stlport* is_scalar_test: vc-6_5-stlport* is_signed_test: vc-6_5-stlport* is_stateless_test: vc-6_5-stlport* is_void_test: vc-6_5-stlport* tricky_abstract_type_test: vc-6_5-stlport* tricky_incomplete_type_test: vc-6_5-stlport* type_with_alignment_test: vc-6_5-stlport* udt_specialisations: vc-6_5-stlport* |typeof| function_binding_native: vc-6_5 vc-6_5-stlport* vc-7_0 nested_typedef_emulation: cw-9.4 odr_native: vc-6_5-stlport* odr_no_uns: vc-6_5 vc-6_5-stlport* vc-7_0 |utility| addressof_test: vc-6_5-stlport* assert_test: vc-6_5-stlport* base_from_member_test: vc-6_5-stlport* binary_search_test: vc-6_5-stlport* call_traits_test: vc-6_5-stlport* compressed_pair_test: vc-6_5-stlport* current_function_test: vc-6_5-stlport* next_prior_test: vc-6_5-stlport* numeric_traits_test: vc-6_5-stlport* operators_test: gcc-3.4.5_linux_x86_64 vc-6_5-stlport* ref_test: vc-6_5-stlport* shared_iterator_test: vc-6_5-stlport* |variant| variant_comparison_test: vc-6_5-stlport* variant_test1: vc-6_5-stlport* variant_test2: vc-6_5-stlport* variant_test3: vc-6_5-stlport* variant_test4: vc-6_5-stlport* variant_test5: vc-6_5-stlport* variant_test6: vc-6_5-stlport* variant_test7: vc-6_5-stlport* variant_test8: vc-6_5-stlport* variant_visit_test: vc-6_5-stlport*

1 0

[Boost-bugs] [ boost-Bugs-1515830 ] regex_match fails, but regex_search works fine
by SourceForge.net 02 Jul '06

02 Jul '06

Bugs item #1515830, was opened at 2006-07-02 05:28 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=1515830&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: regex Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: John Maddock (johnmaddock) Summary: regex_match fails, but regex_search works fine Initial Comment: I encountered this when I tried to upgrade from 1.32 to 1.33.1 I search through a text with regex_search, and pass the results to regex_match. I would expect them to yield the same result, but they don't. Here is a sample code: std::string pattern = "xx-{0,2}([+-][0-9])?"; boost::regex reg(pattern.begin(), pattern.end (), boost::regex::perl_syntax_group ); char* buf = "xx-- "; boost::cmatch what; regex_search(buf,what,reg, boost::regex_constants::match_default); bool match = regex_match(what[0].first, what [0].second,reg, boost::regex_constants::match_any); regex_search returns the [0,4), as I expected, but regex_match returns false! Am I doing something wrong? Is there a workaround? Thanks, Moddy. moddyt(a)itemfield.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1515830&group_… Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[RC_1_34_0] [boostbook] Boost Book recommended xsltproc for Win32 choking?
by Dean Michael Berris 02 Jul '06

02 Jul '06

Hi Everyone, I've just recently decided to use Boost.Book on Win32 and at the end of the python script, there was a URL pointing to the patched xsltproc for windows. I tried accessing the link and it seems like it's broken (or it doesn't let me download the xsltproc referred to). I also checked the documentation ( http://tinyurl.com/quh3t ), and it refers to http://tinyurl.com/m4pz4 -- however this produces a set of errors like the following: warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl" compilation error: file file:///C%3A/src/RC_1_34_0/boost/tools/boostbook/xsl/html.xsl line 8 element import I'm noticing that the colon character is being URL encoded as %3A -- I'm not sure if that's supposed to be the case. I'm not even sure if this is a bug in boostbook's configuration for Boost.Jam (RC_1_34_0) or xsltproc but I thought it might be worth mentioning. Any workarounds to get this working in Windows? HTH -- Dean Michael C. Berris C/C++ Software Architect Orange and Bronze Software Labs http://3w-agility.blogspot.com/ http://cplusplus-soup.blogspot.com/ Mobile: +639287291459 Email: dean [at] orangeandbronze [dot] com

1 0