- Boost - lists.boost.org

thread: Checking for thread termination?
by Johannes 25 Nov '05

25 Nov '05

Hi, In my applications I frequently need to check to see if a thread or thread group has terminated. What is the best (or any) way of doing this in boost::thread? /Johannes

1 0

[serialization][documentation] character encoding oddity
by Martin Wille 25 Nov '05

25 Nov '05

Hi, http://boost.org/libs/serialization/doc/contents.html shows three strange characters at the top of the page (ï»¿). Apparently, those characters have the values EF BB BF in hexadecimal notation. Interpreted as UTF-8 sequence, they encode the Unicode codepoint FFFE. This codepoint is used as a marker for the endianness in encodings other than UTF-8. I doubt such a marker would be legal in or would make sense for an UTF-8 encoded document. Also, the document's content-type meta-tag claims the document uses ISO-8859-1. I suspect there's a problem in the toolchain used to create the document (oherwise, I would have fixed it in the repository). Regards, m Send instant messages to your online friends http://au.messenger.yahoo.com

6 6

[Boost-bugs] [ boost-Bugs-1365752 ] problem with boost::iostreams when compiled with Visual C++
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365752, was opened at 2005-11-24 10:37 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=1365752&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: problem with boost::iostreams when compiled with Visual C++ Initial Comment: There seems to be a problem with boost::iostreams when compiled with Visual C++ 7.1 (Boost Release 1.33.1 Beta). The following code results in a compile error: char array[100]; typedef code_converter<array_sink, Dinkum::conversions::codecvt_utf8<wchar_t> > MyArrayDevice; stream<MyArrayDevice> wCharOut(array, 100); error C2665: 'boost::iostreams::detail::io_mode_impl_helper' : none of the 9 overloads can convert parameter 1 from type 'boost::iostreams::detail::array_adapter<Mode,Ch> ::category' .... The same lines work just fine when compiled with gcc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365752&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

Boost regression notification (2005-11-24 [RC_1_33_0])
by Douglas Gregor 24 Nov '05

24 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-24T15:09:10Z 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… 0 failure in 0 library:

1 0

Boost regression notification (2005-11-24 [HEAD])
by Douglas Gregor 24 Nov '05

24 Nov '05

Boost regression test failures ------------------------------ Report time: 2005-11-24T06:00:26Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 131 failures in 13 libraries: concept_check (13) foreach (1) graph (3) io (1) math (2) mpl (1) multi_array (1) parameter (12) serialization (31) spirit (2) tr1 (45) typeof (18) wave (1) |concept_check| stl_concept_covering: cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux 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-9_0 intel-win32-9_0 mingw-3_4_2 vc-7_1 vc-7_1 |foreach| rvalue_const: intel-win32-9_0 |graph| 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 log1p_expm1_test: gcc-3_4_3-sunos |mpl| size_t: gcc-4_0-darwin |multi_array| concept_checks: mingw-3_4_2 |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 |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_mi_xml_archive: mingw-3_4_2 |spirit| traverse_tests: intel-win32-9_0 traverse_tests_debug: intel-win32-9_0 |tr1| run_complex_overloads: gcc-2.95.3-linux gcc-3_4_3-sunos std_run_complex_overloads: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux gcc-3_4_3-sunos std_run_random: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_boost: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_complex: gcc-2.95.3-linux std_test_hash: gcc-2.95.3-linux std_test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux std_test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_algorithm: gcc-2.95.3-stlport-4.6.2-linux test_complex: gcc-2.95.3-linux test_exception: gcc-2.95.3-stlport-4.6.2-linux test_hash: gcc-2.95.3-linux test_ios: gcc-2.95.3-linux test_istream: gcc-2.95.3-linux test_iterator: gcc-2.95.3-linux test_limits: gcc-2.95.3-linux test_locale: gcc-2.95.3-linux test_new: gcc-2.95.3-stlport-4.6.2-linux test_ostream: gcc-2.95.3-linux test_regex: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_result_of: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_streambuf: gcc-2.95.3-linux test_tr1_include: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_tuple: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_type_traits: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux test_utility: gcc-2.95.3-linux gcc-2.95.3-stlport-4.6.2-linux |typeof| data_member_native: cw-9_4 function_native: cw-9_4 function_ptr_native: cw-9_4 function_ref_native: cw-9_4 lvalue_native: cw-9_4 member_function_native: cw-9_4 modifiers_emulation: cw-9_4 modifiers_native: cw-9_4 noncopyable_native: cw-9_4 std_emulation: 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 template_type_native: cw-9_4 type_native: cw-9_4 |wave| testwave_dll: mingw-3_4_2

1 0

[Boost-bugs] [ boost-Bugs-1365698 ] serialization demo example can't be used
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365698, was opened at 2005-11-24 08:47 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=1365698&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: serialization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Robert Ramey (ramey) Summary: serialization demo example can't be used Initial Comment: I want to use boost.serialization module in my project, but I found that I can't use it. Because i test the demo.cpp in \boost_1_33_1 \libs\serialization\example\, it can't run normally in msvc7.1 environment. It always pop memory alloc error. Who know the reason. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365698&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

lexical_cast on the pocket pc
by Matt Comi 24 Nov '05

24 Nov '05

Hi, I've written a functor (primarily for use with a std::map<string, ?>) that sorts numerically first and alphabetically second using lexical_cast. It looks like this: try { return lexical_cast<double>(lhs) < lexical_cast<double>(rhs); } catch (bad_lexical_cast&) { return lhs < rhs; } ...and it's been working nicely so far. However on the Pocket PC, each time an exception is raised by the lexical_cast, it takes about a quarter of a second to move on to the catch. Not very nice when the map is huge. As far as I can tell, there is no way to say to ensure that a lexical_cast is going to be valid until you actually perform it. I'm hoping that I won't need to resort to duplicating the innards of lexical_cast in order to implement this function on the Pocket PC. Any ideas? Thanks all, Matt. ------------------------------------------------------------------------ -------- Big Bucket Amusement http://members.iinet.net.au/~mattcomi/mt/bigbucket

1 0

Re: [boost] Full MS compiler version info?
by Martin Bonner 24 Nov '05

24 Nov '05

----Original Message---- From: Paul A Bristow [mailto:pbristow@hetp.u-net.com] Sent: 24 November 2005 14:51 To: boost(a)lists.boost.org Subject: Re: [boost] Full MS compiler version info? >> -----Original Message----- >> From: boost-bounces(a)lists.boost.org >> [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov >> Sent: 24 November 2005 12:46 To: boost(a)lists.boost.org >> Subject: Re: [boost] Full MS compiler version info? >> >> Paul A Bristow wrote: >> >>> Indeed - but I didn't see the MS BUILD number - needed to >>> distinguish between 8.0 beta 1, 2, 2.5 ... and final(s). >> >> Why is it needed? Beta versions don't exist as far as >> official support is concerned. > > Of course, but I am sure I am not alone in wanting to anticipate > problems and improvements in testing new versions before the release. > > Indeed this is how Boost gives 'official' support to new versions as > quickly as it does? > > It may be too, that there is more than one release of "8.0". Indeed. The advice used to be: "don't use Visual C++ unless you have SP2 installed". The advice was good even if SP2 hadn't been released for that version! > The > build number gives assurance that this is NOT a cause of mysterious > differences. > -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

[Boost-bugs] [ boost-Bugs-1365338 ] format_paragraph in options_description.cpp
by SourceForge.net 24 Nov '05

24 Nov '05

Bugs item #1365338, was opened at 2005-11-23 23:37 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=1365338&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: format_paragraph in options_description.cpp Initial Comment: function format_paragraph in options_description.cpp triggered assertion _SCL_SECURE_VALIDATE_RANGE failure in microsoft vc8. at line #379, it looks for a space backword to avoid chopping a word in the middle. the expression line_begin - 1 causes assertion failure if line_begin is at the beginning of the description string. here is suggested fix @@ -378,3 +378,3 @@ find(reverse_iterator<string::const_iterator>(line_end - 1), - reverse_iterator<string::const_iterator>(line_begin - 1), + reverse_iterator<string::const_iterator>(line_begin), ' ') @@ -382,3 +382,3 @@ - if (last_space != line_begin - 1) + if (last_space != line_begin) { ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1365338&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

[serialization] non-virtual destructors in 1.33.1
by Kim Barrett 23 Nov '05

23 Nov '05

Between 1.33 and 1.33.1_beta, several classes in the serialization library were changed from having virtual destructors to having non-virtual destructors. An example is basic_oserializer. Many of these classes have virtual functions, with the result that "g++ -Wall" now complains about them ("has virtual functions but non-virtual destructor"), so that I now get tons of warnings when compiling code that uses the serialization library. My guess would be that none of these warnings are actually interesting, but that belief doesn't really help all that much. Was there a good reason for this change? Could it be reverted? If not, is there some other thing that could be done to eliminate these warnings? For 1.33.1 release?

8 13