- Boost - lists.preview.boost.org

[tokenizer] Any expert in bjam?
by Joaquín Mª López Muñoz 29 Sep '04

29 Sep '04

tokenizer is regressing for msvc-stlport as shown in http://tinyurl.com/3mkvx The same kind of problem happens at the following cells wich are marked as expected failures: http://tinyurl.com/44pbx http://tinyurl.com/5xd8z I've built these tests locally for msvc-stlport locally (from my IDE) and they work just fine. No fundamental problem with this platform. So I guess the problem lies in the corresponding Jamfile entries (located directly in boost/status/Jamfile): test-suite tokenizer : [ run libs/tokenizer/examples.cpp <lib>../libs/test/build/boost_test_exec_monitor ] [ run libs/tokenizer/simple_example_1.cpp ] [ run libs/tokenizer/simple_example_2.cpp ] [ run libs/tokenizer/simple_example_3.cpp ] [ run libs/tokenizer/simple_example_4.cpp ] [ run libs/tokenizer/simple_example_5.cpp ] ; I'm pretty sure this is related to some messing up of stdlibs binaries (I vaguely recall that STLPort does not work with single-thread static runtime lib), but my skills of Jamfile are lousy. Could somebody please have a look at it? Another thing that left me wondering is that examples 1, 2 and 4 have the same structure as 3 and 5, and yet they do not fail. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

failures with intel-win32-7.1-vc6-stlport-4.5.3 Toolset?
by John Maddock 29 Sep '04

29 Sep '04

I've been trying to track down a couple of regex test failures that appear for this toolset, but can't build even build STLPort never mind the tests with Intel 7.1, I consistently get errors like: c:\download\open\stlport\STLport-4.5.3\stlport\cstdlib(42): error: namespace "st d" has no member "div_t" using _STLP_VENDOR_CSTD::div_t; ^ c:\download\open\stlport\STLport-4.5.3\stlport\cstdlib(43): error: namespace "st d" has no member "ldiv_t" using _STLP_VENDOR_CSTD::ldiv_t; ^ So is this test being run with a modified STLport version or something? Thanks, John.

2 1

Re:Re: [boost] serialization: buffers
by Robert Ramey 29 Sep '04

29 Sep '04

Darren Cook wrote: >> Or you might try the following (non-portable) idea >> >> ar & BOOST_SERIALIZATION_NVP( >> make_binary_object(str, (p - str)* sizeof(int)) >> ); >Thanks, that is closest to what I was after; I don't need a portable >version here. >> But really, I think you might be best off replacing the class above >> with >> >> class Example { >> std::slist<int> str; // or maybe std::vector<int> str } >It was done using a fixed size buffer to avoid dynamic memory allocation >(mainly for speed reasons). >However as I worked through the class some more I found it can output a >string representation, which uses fewer bytes. So in future I might add a >parser for input and then switch to using that (though I'll be back to >needing separate load/save functions then won't I, oh well :-). A couple final observations: a) the make_binary .. implementation is maximal speed on a binary archive. It just streams the bytes to the i/o buffer. b) If you're concerned about binary portability and file size, take a look at the demo binary portable. It implements saving/loading of integers as variable length binary bytes so that a lot of the zeros are eliminated. c) if you're concerned about file size. You might consider using the streams library - currently pending review - to compress/de-compress the i/o on the fly as the data is saved/loaded. Robert Ramey

1 0

date_time formatting
by Martin 29 Sep '04

29 Sep '04

I'm trying to understand the date_time formatting via iostreams but got problems with a few things. I tried to search the archive but didn't find answers to these questions. 1. Why doesn't date_time use the standard time facet (time_put.do_put etc) if the special greg_date_facet isn't available? 2. Why do I need to specify the names of all months and weekdays in the greg_date_facet just to use a different separator than '-' or another ordering? 3. How do I specify the format of a ptime (date-separator, time-separator and decimal separator)? -------------------------------------------- I also got some compile warnings on VC70 (latest CVS) 1: in the function "from_time_t" on this line return start + seconds(t); boost\date_time\posix_time\conversion.hpp(27) warning C4244: 'argument' : conversion from 'time_t' to 'long', possible loss of data 2: in the function "from_stream_type" ss << ss.narrow(*beg++, 'X'); // 'X' will cause exception to be thrown boost\date_time\date_parsing.hpp(211): warning C4244: 'argument' : conversion from 'wchar_t' to 'char', possible loss of data

2 3

New numeric cast
by Fernando Cacciola 29 Sep '04

29 Sep '04

Hi, According to the regression summary, the new numeric conversion library is in pretty good shape(thanks to Joaquín Muñoz for his latest fixes!) I want to test how far can the new "numeric_cast<>" replace the old one. For that, I want to put the exact same test that's currently used for the old numeric_cast in the new library. Right now, cast_test.cpp contains numeric_cast<> test with other conversions. I will factor it out, but I have a doubt: it is not using the Test framework at all, it's just printing the test result to std out. Does the regression scripts parse the output, or these test are just wrongly integrated? Should I update those test to use the Unit Test Framework? Fernando Cacciola SciSoft

3 6

[type_traits] fixes for GCC 2.95
by Joaquín Mª López Muñoz 29 Sep '04

29 Sep '04

The following regressions in gcc-2.95.3-linux http://tinyurl.com/638l6 http://tinyurl.com/3k6hu are IMHO due to the fact that bad_alloc is defined in <new>, and this header is not included by the corresponding test programs. I'd say it's only out of sheer luck (dependant inclusions) that these tests works for the rest of compilers, but I might be wrong. In any case, #including <new> solves the problem. If noone sees a problem with these patches, I'll commit them. Joaquín M Lópz Muñoz Telefónica, Investigación y Desarrollo 16d15 < #include <new> 22d21 < #include <new>

2 1

Boost.Test token_iterator_test failure
by Gennadiy Rozental 29 Sep '04

29 Sep '04

Hi, Looks like subject test fails at runtime on following line: std::list<char> l; // here I populate l; std::string s; s.assign( l.begin(), l.end() ); // <---------- HERE Funny things is that it start working if I change list to vector. Is this some kind of gcc STL bug? Gennadiy.

2 4

Suspicious warning message python/src/object/function.cpp
by Neal D. Becker 29 Sep '04

29 Sep '04

Current boost.cvs, gcc-3.4.2: /usr/local/src/boost.cvs/libs/python/build/../src/object/function.cpp:101: warning: right-handoperand of comma has no effect

6 7

most boost.python tests fail on Tru64
by Markus Schöpflin 29 Sep '04

29 Sep '04

After I finally got the regression tests running again on my machine, I would like to figure out, why most of the python tests are failing. For an example error message see http://tinyurl.com/46he3 . Has anybody any idea as to where I should start looking for this? Markus

2 3

RE: [boost] Re: [shared_ptr] Interlocked* - possible bug?
by Ben Hutchings 29 Sep '04

29 Sep '04

John Torjo <john.lists(a)torjo.com> wrote: > Ben Hutchings wrote: <snip> > > expired() may read the count as still being 1 and so return false, > > but I believe the wnd_shared_ptr constructor will catch the fact > > that the pointer really has expired. Unfortunately I can't yet > > see the code to confirm this! > > By looking at the code, I would think not. But I may be wrong. > Anyway, I've posted the code in my other post. Thanks for that. Supposing that expired() wrongly returns false because use_count is really 0 but it gets an old non-zero value. Then lock() attempts to construct a shared_ptr: calls shared_ptr<T>::shared_ptr<T>(weak_ptr<T> const &) calls detail::shared_count::shared_count(weak_count const &) calls detail::sp_counted_base::add_ref_lock() calls detail::atomic_conditional_increment( long volatile &) either reads the count as 0 or calls _InterlockedCompareExchange fails and returns 0 then loops around and reads the count as 0 returns 0 throws bad_weak_ptr catches bad_weak_ptr returns 0 OK?

3 2