- Boost - lists.boost.org

More bad line endings?
by Daryle Walker 07 Dec '05

07 Dec '05

As I'm wont to do, I compared the folders created by the 1.33.0 and 1.33.1 archives to see the changes myself. I used the Metrowerks CodeWarrior Pro 8.3 IDE on my Mac OS X 10.4 system for the comparison. The IDE complained about mismatched line endings for the file ROOT/boost/iostreams/chain.hpp, but I don't know which version (1.33.0 or 1.33.1) of the file has the bad line endings. I didn't check every changed file, so there may be others with this problem. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

1 0

[Tokenizer] A hybrid between char_separator and escaped_list_separator
by Zvi Tarem 07 Dec '05

07 Dec '05

It would be very useful to have a tokenizer that operates similar to the regular char_separator, but also handles delimiters in quoted portions like escaped_list_separator. For example: Input: model name = "My Model" label="A short label = A good label" parts= 3 Output: <model> <name> <=> <My Model> <label> <=> <A short label = A good label> <parts> <=> <3> Regards, Zvi Tarem (zvi.tarem(a)cern.ch)

1 0

Problem building boost under vc_7.1
by Andrew Maclean 07 Dec '05

07 Dec '05

Has anyone been able to build boost under vc_7.1? I seem to be getting the following error when running bjam: ---------------------------------------------------------------------------- Jamfile:278: in load-jamfiles *** argument error * rule stage ( name : sources + : requirements * : local-build * ) * called with: ( : C:\boost\boost_1_33_1\boost\compatibility\cpp_c_headers ................. lots and lots of files .............................. C:\boost\boost_1_33_1\boost\wave\util\unput_queue_iterator.hpp : <locate>C:\Boost <tree-subdirs>C:\boost\boost_1_33_1 <target>all : <suppress>true ) * missing argument name C:\boost\boost_1_33_1\tools/build/v1\boost-base.jam:2330:see definition of rule 'stage' being called C:\boost\boost_1_33_1\tools\build\v1\bootstrap.jam:21: in boost-build C:\boost\boost_1_33_1\boost-build.jam:16: in module scope ---------------------------------------------------------------------------- I downloaded both boost_1_33_1.exe and boost_1_33_1.tar.gz and ran bjam on them with the same result as above. I am using bjam from boost-jam-3.1.11-1-ntx86.zip. Note that boost_1_33_0 runs OK with bjam so I ma pretty sure it is problem in the jam files. Just after missing argument name in the above output "/" are appearing along with the usual "\"Microsoft OS path separator. Is this the problem. Thanks in advance for any help. Andrew ___________________________________________ Andrew J. P. Maclean Centre for Autonomous Systems The Rose Street Building J04 The University of Sydney 2006 NSW AUSTRALIA Ph: +61 2 9351 3283 Fax: +61 2 9351 7474 URL: http://www.cas.edu.au/ ___________________________________________

1 0

[1.33.0][date_time] Yr 1900 issue on x64 Win
by Norian N 07 Dec '05

07 Dec '05

I'm trying to use Boost 1.33 libs on x64 Windows platform. Have assert break when try to use date below year 1900. Is it known issue? To reproduce: #include "stdafx.h" #include <iostream> #include <boost/date_time/local_time/local_time.hpp> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost::gregorian; using namespace std; date d(1899, Jan, 1); stringstream ss; ss << d; cout << ss << endl; return 0; } The cause located in conversion.hpp module and strftime() assert : boost::gregorian::date::ymd_type ymd = d.year_month_day(); datetm.tm_year = ymd.year-1900; _VALIDATE_RETURN( ( timeptr->tm_year >=0 ), EINVAL, FALSE) Thanks, Dmitry Solodkiy, SW engineer

3 2

[Boost-bugs] [ boost-Feature Requests-1374957 ] Boost.Ruby
by SourceForge.net 07 Dec '05

07 Dec '05

Feature Requests item #1374957, was opened at 2005-12-06 17:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1374957&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Boost.Ruby Initial Comment: Hi, it would be great if ruby developpers could have a bridge between C++ and ruby like the one for python. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1374957&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] Permanently retire VC++ 6?
by Martin Bonner 06 Dec '05

06 Dec '05

----Original Message---- From: Peter Dimov [mailto:pdimov@mmltd.net] Sent: 05 December 2005 13:19 To: boost(a)lists.boost.org Subject: Re: [boost] Permanently retire VC++ 6? > Paul A Bristow wrote: >>> -----Original Message----- >>> From: boost-bounces(a)lists.boost.org >>> [mailto:boost-bounces@lists.boost.org] On Behalf Of Victor A. >>> Wagner Jr. Sent: 05 December 2005 01:02 >>> To: boost(a)lists.boost.org; boost(a)lists.boost.org >>> Subject: Re: [boost] Permanently retire VC++ 6? >>> (was:Re:Math/Quaternions compile problem in VC++6) >>> >>> and I'm all for retiring vc++6.0 support from boost (I've argued >>> this before). >> >> This is long overdue and now that we have a reasonably compliant >> MSVC compiler that works on Windows 2000 up I can't see any excuse >> for not dropping support. Things that this work will still work, >> but if not - tough. (I am not proposing ripping out all the #ifdefs >> relating the MSVC 6, despite the improvement in readability that >> might result). >> >> Should we have a straw poll of the lurkers - so that diehards can >> have their say - and then make a decision? > > What do you mean by "dropping support"? Excellent question. > > I am against dropping VC 6 regression tests in general because I want > to see what works on it, either for not introducing a regression, or > for ensuring compatibility where it's reasonably easy to do so. I agree with this. > I do not oppose dropping VC 6 and 7 from the list of "release" > compilers. I think it is too soon to drop VC 7.1 from the list of "release" compilers. (But VC7.0 could probably go). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

16 33

seeking commonality in futures/threader/demuxer/defer/etc models
by simon meiklejohn 06 Dec '05

06 Dec '05

Q. Is it possible to isolate a core thread execution model from the various libs currently on offer, and re-express those libs in terms of the core model? The core service amonst these libraries is "Execution of abstracted tasks in an appropriate threads" Task seems to be in common expressible as a function object Major extension/variations include - waitable return object (future/threader) vs. ad hoc reverse direction task execution (asio::demuxer/defer) - threads resources shareable amongst different tasks (threader/demuxer/defer) vs thread created per action (futures, also possible with defer & threader styles) - some guarantees given about which thread will do a given task (threader/demuxer/defer) vs guaranteed new thread (future) - able to extend callbacks into windows message pump (defer) I think the different return styles can be unified to some extent by wrapper objects which operate like a void(void) function for exection, but which package up a wrapped function with return values and expose a wait() method on which the caller can wait for the result (essentially what threader/futures do) Futures autocreation of threads for each task is clearly implementable on top of any of the others, though perhaps not as efficiently. Guarantees about how a task will execute may not matter to all applications but it critical to others. The asio::demuxer gives a guarantee that the task will execute in a thread that has called demuxer::run, which may include the thread which is doing the requesting - implication being that the call may take place immediately. This is an excellent performance optimisation, but the programmer may require stronger guarantees, perhaps against that very optimisation. Vague Conclusions. I think its doable, I'd like to use such a boost library, i'd like it to be flexible in terms of strategising the thread allocation, i'd like to be able to use different models of thread allocator to solve different problems from distruting load amongst threads to solving thread deadlock issues to integrating my networking library with my GUI application. I'd prefer it if someone smarter than myself could write the code, but if they'd keep my requirements in mind while doing so (and treat my defer submission as an extension to those requirements) then i'd be happy. Cheers Simon Meiklejohn

2 7

Boost regression notification (2005-12-06 [RC_1_33_0])
by Douglas Gregor 06 Dec '05

06 Dec '05

Boost regression test failures ------------------------------ Report time: 2005-12-06T11:57:08Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_0/developer/i… 6 failures in 2 libraries: graph (5) serialization (1) |graph| layout_test: cw-8_3 cw-9_4 gcc-3_4_3-sunos intel-win32-8_1 vc-7_0 |serialization| test_simple_class_ptr_text_warchive_dll: vc-8_0

1 0

Boost regression notification (2005-12-06 [HEAD])
by Douglas Gregor 06 Dec '05

06 Dec '05

Boost regression test failures ------------------------------ Report time: 2005-12-06T06:00:12Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 294 failures in 18 libraries: bind (1) concept_check (15) date_time (19) foreach (5) graph (5) io (1) math (1) mpl (1) multi_array (7) parameter (1) python (59) serialization (36) smart_ptr (1) spirit (3) tr1 (89) typeof (24) wave (2) xpressive (24) |bind| bind_dm3_test: msvc |concept_check| stl_concept_covering: cw-9_4 cw-9_4 gcc-3.3.6-linux gcc-3.4.4-linux gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin intel-win32-8_1 intel-win32-9_0 intel-win32-9_0 intel-win32-9_0 mingw-3_4_2 msvc vc-7_1 vc-7_1 |date_time| testc_local_adjustor: msvc testclock: msvc testdst_rules: msvc testfiletime_functions: msvc testgreg_duration_operators: msvc testgreg_serialize_dll: cw-9_4 intel-win32-8_1 intel-win32-9_0 vc-7_1 vc-7_1 testiterator: msvc testlocal_adjustor: msvc testmicrosec_time_clock: msvc testparse_time: msvc testtime: msvc testtime_formatters: msvc testtime_period: msvc testwcustom_time_zone: msvc testwposix_time_zone: msvc |foreach| array_byref: intel-win32-8_1 array_byval: intel-win32-8_1 rvalue_const: intel-win32-9_0 stl_byref: intel-win32-8_1 stl_byval: intel-win32-8_1 |graph| dominator_tree_test: intel-win32-9_0 vc-7_1 graphviz_test: vc-7_1 vc-7_1 layout_test: intel-win32-9_0 |io| ios_state_unit_test: intel-win32-9_0 |math| complex_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |multi_array| access: cw-9_4 assign: cw-9_4 assign_to_array: cw-9_4 idxgen1: cw-9_4 index_bases: cw-9_4 iterators: cw-9_4 slice: cw-9_4 |parameter| sfinae: msvc |python| andreas_beyer: gcc-3_4_3-sunos args: gcc-3_4_3-sunos auto_ptr: gcc-3_4_3-sunos back_reference: gcc-3_4_3-sunos ben_scott1: gcc-3_4_3-sunos bienstman1: gcc-3_4_3-sunos bienstman2: gcc-3_4_3-sunos bienstman3: gcc-3_4_3-sunos builtin_converters: gcc-3_4_3-sunos callbacks: gcc-3_4_3-sunos const_argument: gcc-3_4_3-sunos crossmod_exception: gcc-3_4_3-sunos data_members: gcc-3_4_3-sunos defaults: gcc-3_4_3-sunos dict: gcc-3_4_3-sunos docstring: gcc-3_4_3-sunos enum: gcc-3_4_3-sunos exception_translator: gcc-3_4_3-sunos exec: gcc-3_4_3-sunos extract: gcc-3_4_3-sunos implicit: gcc-3_4_3-sunos injected: gcc-3_4_3-sunos iterator: gcc-3_4_3-sunos keywords: gcc-3_4_3-sunos list: gcc-3_4_3-sunos long: gcc-3_4_3-sunos map_indexing_suite: gcc-3_4_3-sunos minimal: gcc-3_4_3-sunos multi_arg_constructor: gcc-3_4_3-sunos nested: gcc-3_4_3-sunos numpy: gcc-3_4_3-sunos object: gcc-3_4_3-sunos opaque: gcc-3_4_3-sunos operators: gcc-3_4_3-sunos pearu1: gcc-3_4_3-sunos pickle1: gcc-3_4_3-sunos pickle2: gcc-3_4_3-sunos pickle3: gcc-3_4_3-sunos pickle4: gcc-3_4_3-sunos pointer_vector: gcc-3_4_3-sunos polymorphism: gcc-3_4_3-sunos polymorphism2: gcc-3_4_3-sunos polymorphism2_auto_ptr: gcc-3_4_3-sunos properties: gcc-3_4_3-sunos raw_ctor: gcc-3_4_3-sunos return_arg: gcc-3_4_3-sunos select_from_python_test: gcc-3_4_3-sunos shared_ptr: gcc-3_4_3-sunos slice: gcc-3_4_3-sunos staticmethod: gcc-3_4_3-sunos stl_iterator: gcc-3_4_3-sunos msvc str: gcc-3_4_3-sunos test_pointer_adoption: gcc-3_4_3-sunos try: gcc-3_4_3-sunos tuple: gcc-3_4_3-sunos vector_indexing_suite: gcc-3_4_3-sunos virtual_functions: gcc-3_4_3-sunos wrapper_held_type: gcc-3_4_3-sunos |serialization| test_class_info_load_binary_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_binary_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_text_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_archive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_class_info_load_xml_warchive_dll: gcc-3_3-darwin gcc-3_4_3-sunos gcc-4_0-darwin test_const_save_fail1: msvc test_const_save_fail2: msvc test_const_save_fail3: msvc test_map_binary_archive_dll: msvc test_map_text_archive_dll: msvc test_map_text_warchive_dll: msvc |smart_ptr| shared_ptr_alloc2_test: msvc |spirit| multi_pass_compile_tests: intel-win32-8_1 traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: cw-9_4 gcc-3_4_3-sunos std_run_complex_overloads: cw-9_4 gcc-3_4_3-sunos std_run_random: cw-9_4 std_test_array: cw-9_4 std_test_bind: cw-9_4 std_test_complex: cw-9_4 std_test_function: cw-9_4 std_test_hash: cw-9_4 std_test_mem_fn: cw-9_4 std_test_random: cw-9_4 std_test_regex: cw-9_4 std_test_result_of: cw-9_4 std_test_tr1_include: cw-9_4 std_test_tuple: cw-9_4 std_test_type_traits: cw-9_4 test_bind: cw-9_4 test_complex: cw-9_4 test_function: cw-9_4 test_hash: cw-9_4 test_mem_fn: cw-9_4 test_random: cw-9_4 test_reference_wrapper: cw-9_4 test_result_of: cw-9_4 test_shared_ptr: cw-9_4 test_tr1_include: cw-9_4 test_tuple: cw-9_4 tr1_add_const_test: cw-9_4 tr1_add_cv_test: cw-9_4 tr1_add_pointer_test: cw-9_4 tr1_add_reference_test: cw-9_4 tr1_add_volatile_test: cw-9_4 tr1_aligned_storage_test: cw-9_4 tr1_alignment_of_test: cw-9_4 tr1_extent_test: cw-9_4 tr1_has_nothrow_assign_test: cw-9_4 tr1_has_nothrow_constr_test: cw-9_4 tr1_has_nothrow_copy_test: cw-9_4 tr1_has_tr1_ref_wrap_fail: cw-9_4 tr1_has_tr1_shared_ptr_fail: cw-9_4 tr1_has_tr1_tuple_fail: cw-9_4 tr1_has_trivial_assign_test: cw-9_4 tr1_has_trivial_constr_test: cw-9_4 tr1_has_trivial_copy_test: cw-9_4 tr1_has_trivial_destructor_test: cw-9_4 tr1_has_virtual_destructor_test: cw-9_4 tr1_is_arithmetic_test: cw-9_4 tr1_is_array_test: cw-9_4 tr1_is_base_of_test: cw-9_4 tr1_is_class_test: cw-9_4 tr1_is_compound_test: cw-9_4 tr1_is_const_test: cw-9_4 tr1_is_convertible_test: cw-9_4 tr1_is_empty_test: cw-9_4 tr1_is_enum_test: cw-9_4 tr1_is_floating_point_test: cw-9_4 tr1_is_function_test: cw-9_4 tr1_is_fundamental_test: cw-9_4 tr1_is_integral_test: cw-9_4 tr1_is_member_func_test: cw-9_4 tr1_is_member_obj_test: cw-9_4 tr1_is_member_pointer_test: cw-9_4 tr1_is_object_test: cw-9_4 tr1_is_pod_test: cw-9_4 tr1_is_pointer_test: cw-9_4 tr1_is_polymorphic_test: cw-9_4 tr1_is_reference_test: cw-9_4 tr1_is_same_test: cw-9_4 tr1_is_scalar_test: cw-9_4 tr1_is_signed_test: cw-9_4 tr1_is_union_test: cw-9_4 tr1_is_unsigned_test: cw-9_4 tr1_is_void_test: cw-9_4 tr1_is_volatile_test: cw-9_4 tr1_rank_test: cw-9_4 tr1_remove_all_extents_test: cw-9_4 tr1_remove_const_test: cw-9_4 tr1_remove_cv_test: cw-9_4 tr1_remove_extent_test: cw-9_4 tr1_remove_pointer_test: cw-9_4 tr1_remove_reference_test: cw-9_4 tr1_remove_volatile_test: cw-9_4 tr1_tricky_abstract_type_test: cw-9_4 tr1_tricky_add_pointer_test: cw-9_4 tr1_tricky_function_type_test: cw-9_4 tr1_tricky_incomplete_type_test: cw-9_4 tr1_tricky_is_enum_test: cw-9_4 tr1_tricky_partial_spec_test: cw-9_4 |typeof| data_member_native: cw-9_4 function_native: cw-9_4 msvc function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 msvc member_function_native: cw-9_4 modifiers_emulation: cw-9_4 cw-9_4 modifiers_native: cw-9_4 cw-9_4 noncopyable_native: cw-9_4 std_emulation: cw-9_4 cw-9_4 std_native: cw-9_4 template_dependent_native: cw-9_4 template_enum_native: cw-9_4 template_int_native: cw-9_4 template_multiword_native: cw-9_4 template_tpl_native: cw-9_4 msvc template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave: cw-9_4 testwave_dll: cw-9_4 |xpressive| misc1: cw-9_4 test1: cw-9_4 test1u: cw-9_4 test2: cw-9_4 test2u: cw-9_4 test3: cw-9_4 test3u: cw-9_4 test4: cw-9_4 test4u: cw-9_4 test5: cw-9_4 test5u: cw-9_4 test6: cw-9_4 test6u: cw-9_4 test7: cw-9_4 test7u: cw-9_4 test8: cw-9_4 test8u: cw-9_4 test9: cw-9_4 test9u: cw-9_4 test_cycles: cw-9_4 test_dynamic: cw-9_4 test_non_char: cw-9_4 test_regex_primitives: cw-9_4 test_static: cw-9_4

1 0

When's 1.33.1 being merged into HEAD? (a.k.a. My ancient history got obliterated!)
by Daryle Walker 06 Dec '05

06 Dec '05

I noticed that 1.33.1 was just posted. I noticed that the 1.33.1 notes were posted on our front web page <http://www.boost.org> and the old 1.33.0 notes were moved to the version history page <http://www.boost.org/more/version_history.html>. Then I scrolled to the bottom and noticed that all the extra entries of ancient Boost history I added were gone! I realized what happened: I put my entries on the HEAD branch then uploaded them to our web space. The 1.33.1 manager did the same thing, but those files are based off the older 1.33.x branch. Any changes made since that branch (that were uploaded) got paved over on the web site. Looking at the CVS history for the page <http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/version_history.html ?rev=1.9&view=log>, you can see that my last change (r1.9) is the latest on the HEAD, but some of the 1.33.x changes (r1.4.2.x) are newer. We should solve this by merging the 1.33.1 changes into the HEAD then upload web pages as appropriate. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1