- Boost - lists.boost.org

[boost.build]: docs for the --layout option
by Stefan Seefeld 18 Apr '06

18 Apr '06

I'v just built boost using 'bjam -sBUILD="release <threading>multi" --layout=system' and I notice that all library names contain an 'mt' tag, which I thought would be suppressed with the --layout=system option. Unfortunately, I'm unable to find documentation for the --layout option, so I can't verify whether I remembered it wrongly. Thus I have two questions: * Where can I find complete documentation for options such as --layout ? (I'm not even sure this is part of bjam, or boost.build, or something entirely different.) * What is the correct use of --layout, and what does it actually do ? Shouldn't 'mt' be suppressed, too ? (Did the actual behavior change recently ?) Thanks, Stefan

2 2

[serialization] Exported class names
by Marcin Kalicinski 18 Apr '06

18 Apr '06

Is there a way to force serialization library only input/output exported class names, not class id numbers? I'm trying to make serialization lib read a file created by a human, and human obviously cannot be supposed to type class-id integers. Best regards, Marcin

1 0

CVS
by Arkadiy Vertleyb 17 Apr '06

17 Apr '06

Hi all. I just got back from vacation, and, looking at the Sourceforge site, CVS is still not in a great shape. Does Boost have its own recommendations on what to do in this situation? Should we just wait until things get normal once again? Or should we take some extra precaution, like making extra copies of our libraries, etc.? (sorry if I missed any posts on a similar subject) Regards, Arkadiy

3 5

[shared_ptr] mutex in quick_allocator
by Boris 17 Apr '06

17 Apr '06

If you define BOOST_SP_DISABLE_THREADS class boost::detail::sp_counted_base doesn't use a mutex (see http://www.boost.org/libs/smart_ptr/shared_ptr.htm#ThreadSafety) However boost::detail::quick_allocator still uses a mutex as it checks BOOST_HAS_THREADS but not BOOST_SP_DISABLE_THREADS (see http://www.boost.org/boost/detail/quick_allocator.hpp) Is this intentional (as quick_allocator might be used by other classes)? Boris

2 4

metacomm borland 5_8_* results
by Vladimir Prus 17 Apr '06

17 Apr '06

Hi, at the moment, results for borland_5_8_1 and borland_5_8_2b compiler on RC_1_34_0 branch are pretty bad. See: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/s… Unless a user of borland can step forward and look into those failures, we'll essentially have no support for those toolsets in 1.34. Any volunteers? Thanks, Volodya

7 12

[ublas] scalar_vector documentation
by Chris Weed 17 Apr '06

17 Apr '06

The scalar_vector documentation shows as example with a constructor taking only one argument; however, the constructor does not exist in the documentation just below. I suspect the example must be wrong. The web page is here: http://www.boost.org/libs/numeric/ublas/doc/vector.htm Chris

1 0

Re: [boost] Report from Berlin C++ Standards Committee meeting
by Reece Dunn 17 Apr '06

17 Apr '06

Steve Hutton wrote: > The idea is that to select all rows, you fetch within a loop. The > vector gets resized to contain the number of rows returned. > > const int BATCH_SIZE = 30; > std::vector<int> valsOut(BATCH_SIZE); > Statement st = (sql.prepare << "select value from numbers", > into(valsOut)); > st.execute(); > while (st.fetch()) > { > std::vector<int>::iterator pos; > for(; pos != valsOut.end(); ++pos) > { > cout << *pos << '\n'; > } > } > > http://soci.sourceforge.net/doc/statements.html How abouit something like: sql::statement query; query << "select value from numbers"; sql::rowset< int > rows(query); cout << "found = " << rows.size() << endl; std::vector< int > values; std::copy( rows.begin(), rows.end(), values ); Multi-item row searches could use tuple: sql::rowset< int, std::wstring, int > rows( query ); std::tr1::tuple< int, std::wstring, int > value = rows.begin(); - Reece _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

9 14

[iterator] Test patch for BCB2006
by Nicola Musatti 17 Apr '06

17 Apr '06

Hallo, libs/iterator/test/iterator_traits_test.cpp should be updated for the latest Borland compiler. Patch attached. Cheers, Nicola Musatti ******Index: iterator_traits_test.cpp =================================================================== RCS file: /cvsroot/boost/boost/libs/iterator/test/iterator_traits_test.cpp,v retrieving revision 1.4 diff -d -u -r1.4 iterator_traits_test.cpp --- iterator_traits_test.cpp 20 Feb 2006 15:45:08 -0000 1.4 +++ iterator_traits_test.cpp 12 Apr 2006 07:34:10 -0000 @@ -153,7 +153,7 @@ input_iterator_test<std::istream_iterator<int>, int, std::ptrdiff_t, int*, int&, std::input_iterator_tag> istream_iterator_test; -#if defined(__BORLANDC__) && !defined(__SGI_STL_PORT) +#if BOOST_WORKAROUND(__BORLANDC__, <= 0x564) && !defined(__SGI_STL_PORT) typedef ::std::char_traits<char>::off_type distance; non_pointer_test<std::ostream_iterator<int>,int, distance,int*,int&,std::output_iterator_tag> ostream_iterator_test;

2 2

[Boost-bugs] [ boost-Support Requests-1471723 ] support new 2007 DST rules for timezone db
by SourceForge.net 17 Apr '06

17 Apr '06

Support Requests item #1471723, was opened at 2006-04-17 06:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1471723&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: support new 2007 DST rules for timezone db Initial Comment: The boost time library supports processing of the timezone database file as a .csv, with one entry per time zone, such as "America/New_York". However, in 2007, the daylight savings time rules will change. The contents of the csv need to change, to incorporate a range of effective years. Since DST is a spring and fall event (in both north and south hemispheres) only a year need be recorded. I suggest adding two values at the beginning of the line, (as one field in the form nnnn-nnnn) for the low effective-year and high effective-year, as 4-digit values. Let 0000 be used for "all previous years" and 9999 be used for all subsequent years. [If the '-' separator is a problem, ':' could be used instead.] Then, the change in 2007 can be recorded as two lines: "2007-9999","America/New_York", ... "0000-2006","America/New_York", ... Lines unaffected by the change would have "0000-9999" as the first field. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1471723&group_… ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] [type_traits] is_convertible<noncopyable,To> crashes
by JOAQUIN LOPEZ MU?Z 17 Apr '06

17 Apr '06

----- Mensaje original ----- De: John Maddock <john(a)johnmaddock.co.uk> Fecha: Viernes, Abril 14, 2006 12:19 pm Asunto: Re: [boost] [type_traits] is_convertible<noncopyable,To> crashes > > In a post from yesterday (see http://tinyurl.com/hzk5w) > > Alexei Alexandrov found a rather serious problem with > > is_convertible in at least MSVC 7.1 and Intel 9.0, namely > > that is_convertible<From,To> fails to compile when > >> From is non-copyable, emitting an error message like this: > > Wait a second, I've just looked at the original error messages, > and the test > case is very specific, it fails for: > > is_convertible<const noncopyable, const noncopyable> > > That is known not to work, *and will never work*, there is no way > we can > define a trait that detects whether a type is copy-constructable > or not. In > other words the From and To parameters must be different types. OK, I've carefully read the standard and I understand now that convertiblity between X and itself is tantamount to X being copy constructible (my naive understanding was that X is always convertible to X by definition.) For the purposes of my code, I can then replace the calls of the form is_convertible<X,Y> with calls to template<typename From,typename From> struct is_same_or_convertible: mpl::or_< is_same<From,To> is_convertible<From,To> > {}; and thus avoid executing is_convertible<From,To> whith From=To. [On a side note, if From must be different to To, why is this is not stated in the docs? There's even a case whith From=To in is_convertible_test.cpp: BOOST_CHECK_INTEGRAL_CONSTANT( (::tt::is_convertible<Base,Base>::value), true); end of side note.] So, if we exclude the case where From=To, is is_convertible supposed to work for the call pattern is_convertible<const X,Y> where X is non-copyable and Y!=X? From Alexei tests seems like this could be failing too, and does not fall under the forbidden From=To case. I don't have any compiler handy right now, will try to check out by myself in a few days. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2