- Boost - lists.boost.org

RE: [boost] Re: Lock unification [move]
by Batov, Vladimir 22 Jul '04

22 Jul '04

Does it have to be in 'std'? Cannot that be under 'scoped_lock'? Do not have the docs handy. Won't lookup mechanism pick it up? > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Howard Hinnant > Sent: Thursday, 22 July 2004 10:31 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Lock unification [move] > > On Jul 21, 2004, at 7:16 PM, David Abrahams wrote: > > > Howard Hinnant <hinnant(a)twcny.rr.com> writes: > > > >> <nod> How's: > >> > >> scoped_lock lk1(m, defer_lock); // not locked > > ^^^^ ^^^^ > > > > Redundant. "deferred" is better. > > I seriously thought about deferred. The word, whatever it is, if > standardized, would be at namespace scope in namespace std. I was > worried about it conflicting, or with its use not being easily > associated with locks if it was just "deferred". Otoh, it is only a > tag. Maybe it is a feature, not a bug for "deferred" to be able to > influence (conflict with) things other than locks! Thanks for the > second thought. > > -Howard > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

RE: [boost] Re: Lock unification [move]
by Batov, Vladimir 22 Jul '04

22 Jul '04

Howard, Thank you for taking on the task of shaping up the interface. That activity is of great importance. A few comments. explicit scoped_lock(mutex_type& m); scoped_lock(mutex_type& m, detail::defer_lock_type); scoped_lock(mutex_type& m, detail::try_lock_type); scoped_lock(mutex_type& m, const elapsed_time& elps_time); The problem (as I can see it) with the set above is that "deferred", "tried" and "timed" appear to be alternatives or mutually exclusive. However, "deferred" and, say, "try" functionalities are orthogonal. That is, as one might need to defer a blocking lock scoped_lock l(m, deferred); one might need a deferred try_lock as well. Therefore, as we are trying to provide one universal lock, it appears we have to have something complex like basic_lock(mutex_type&, const elapsed_time&, defer_type); that would address all the lock variability/configurability. Such a basic lock would not be for general consumption but rather the basis for something like: try_lock : private (?) basic_lock { ... try_lock(mutex_type& m, deferred d) : basic_lock(m, 0, d) {} } Best, V.

3 2

RE: [boost] Re: Boost.Test and mingw (Was: [1.32 release] Intel 8 .0/Mingw regression results)
by Rob Lievaart 22 Jul '04

22 Jul '04

Hi, > Fix is in cvs. Lets see what next regression test show. Thanks, Test is running again now with the fix, and so far no lines in bjam.log complaining about wcscmp. Rob.

1 0

Tom Brinkman to become the new Review Wizard
by John Maddock 22 Jul '04

22 Jul '04

Boosters, As you will know already, we recently advertised for a Review Wizard to take over from Thomas Witt, who pioneered the role and has done an excellent job, but now has other commitments. We have had several excellent applications giving the moderators a tough choice: but in the end an excellent application and a healthy dose of enthusiasm gave Tom Brinkman the job. On behalf of all the moderators I'd like to welcome Tom to the post, and look forward to the reviews once again progressing. Regards, John Maddock.

1 0

[bug, patch] Bashism in boost/tools/build/v2/tools/common.jam
by Philipp Frauenfelder 22 Jul '04

22 Jul '04

Hi There is a bashism in common.jam of Boost.Build v2. I have reported this problem to the jamboost mailing list but apparently, nobody picked it up (no reply whatsoever). The normal 'sh' shell does not allow 'export VAR=value' but only 'VAR=value;export VAR' instead. The patch against 1.24 is attached (I also removed some trailing white space, there is more 4 lines down but I did not correct it). Regards -- Philipp | work: pfrauenf(a)math.ethz.ch +41 44 632 60 38 Frauenfelder | home: pfrauenf(a)debian.org +41 44 862 73 14 [PGP] | http://www.math.ethz.ch/~pfrauenf/ Proudly running Debian GNU/Linux. See http://www.debian.org/

1 0

question regarding vacpp tests and mpl
by Robert Ramey 22 Jul '04

22 Jul '04

The serialization library is failing all tests with IBM visual age compiler. Errors occur within mpl. a) Can any one give me some hints to try to address this? b) Is there not a new version of mpl that is going to uploaded. Maybe if I just wait things will improve? Robert Ramey

2 1

RE: Boost.Test and mingw (Was: [boost] [1.32 release] Intel 8.0/M ingw regression results)
by Rob Lievaart 22 Jul '04

22 Jul '04

Hi, Hi Volodya, There are some lines in test_tools.cpp to work around this but are defined only for GCC 3.3 and I am using 3.2 :-( There was a discussion on this isssue (I think) 2 days ago: http://lists.boost.org/MailArchives/boost/msg67745.php Where Gennadiy says he wil fix it. But that has not made it into cvs yet. This is the cause of a lot of errors in the report. I "hacked" around it locally by also testing for GCC 3.2 and that clears up a lot of the problems. I could post a diff for what I changed locally, but it is not a nice solution. I simply changed the == sign in the test for minor version to <= . The test discussed in the mail is better I guess. Kind regards, Rob Lievaart. Vladimir Prus wrote: > > Aleksey Gurtovoy wrote: > > Stefan Slapeta's Intel 8.0 and Rob Lievaart's Mingw/gcc 3.2.3 results > > are now available in the Boost-wide summary reports: > > > > http://www.boost.org/regression-logs/developer/summary.html > > It shows that Boost.Test fails to build at mingw, with this error: > > Z:/regression/boost/libs/test/src/test_tools.cpp: In function `bool > > boost::test_tools::tt_detail::equal_and_continue_impl(const wchar_t*, const > > wchar_t*, boost::wrap_stringstream&, boost::unit_test::basic_cstring<const > > char>, unsigned int, boost::unit_test::log_level)': > > Z:/regression/boost/libs/test/src/test_tools.cpp:190: `wcscmp' undeclared in > > namespace `std' > > Any ideas how to fix this?

3 2

Problems with program_options using GCC 3.4 on FreeBSD
by Jonathan Wakely 22 Jul '04

22 Jul '04

Hi Boosters, I've just tried building the program_options library, using GCC 3.4.1 on FreeBSD 4.8 and hit a couple of compilation errors. One error is caused by the platform, one by the compiler's stdlib. The first problem is line 116 in libs/program_options/src/utf8_codecvt_facet.cpp gcc-C++-action bin/boost/libs/program_options/build/libboost_program_options.a/gcc/debug/utf8_codecvt_facet.o /data/development/jw/src/extcvs/boost/libs/program_options/build/../src/utf8_codecvt_facet.cpp: In member function `virtual std::codecvt_base::result boost::program_options::detail::utf8_codecvt_facet_wchar_t::do_out(mbstate_t&, const wchar_t*, const wchar_t*, const wchar_t*&, char*, char*, char*&) const': /data/development/jw/src/extcvs/boost/libs/program_options/build/../src/utf8_codecvt_facet.cpp:116: error: `WCHAR_MAX' undeclared (first use this function) /data/development/jw/src/extcvs/boost/libs/program_options/build/../src/utf8_codecvt_facet.cpp:116: error: (Each undeclared identifier is reported only once for each function it appears in.) WCHAR_MAX is not defined by FreeBSD's wchar.h. Can boost::numeric_limits<wchar_t> be used instead? The second problem is visible because I built GCC with concept-checks enabled, which means the STL containers use a version of Boost's concept checks. This reveals that boost/program_options/options_description.hpp uses an incomplete type on line 232: gcc-C++-action bin/boost/libs/program_options/build/libboost_program_options.a/gcc/debug/options_description.o In file included from /data/development/jw/src/extcvs/boost/libs/program_options/build/../src/options_description.cpp:9: /data/development/jw/gcc/3.4/bin/../lib/gcc/i386-unknown-freebsd4.8/3.4.1/../../../../include/c++/3.4.1/bits/boost_concept_check.h: In instantiation of `__gnu_cxx::_SGIAssignableConcept<boost::program_options::options_description>': /data/development/jw/gcc/3.4/bin/../lib/gcc/i386-unknown-freebsd4.8/3.4.1/../../../../include/c++/3.4.1/bits/stl_vector.h:144: instantiated from `std::vector<boost::program_options::options_description, std::allocator<boost::program_options::options_description> >' /data/development/jw/src/extcvs/boost/boost/program_options/options_description.hpp:232: instantiated from here /data/development/jw/gcc/3.4/bin/../lib/gcc/i386-unknown-freebsd4.8/3.4.1/../../../../include/c++/3.4.1/bits/boost_concept_check.h:216: error: `__gnu_cxx::_SGIAssignableConcept<_Tp>::__a' has incomplete type /data/development/jw/src/extcvs/boost/boost/program_options/options_description.hpp:142: error: forward declaration of `class boost::program_options::options_description' This error can be reproduced by compiling with -D_GLIBCXX_CONCEPT_CHECKS, or -D_GLIBCXX_DEBUG. Both the concept-checks and debug mode will reject std::vector< incomplete type >. jon -- "Nothing is true. Everything is permissible." - Hassan i Sabbah

3 9

Latest Boost.Threads regression results on meta-como-win32-4.3.3-vc7
by Michael Glassford 22 Jul '04

22 Jul '04

The Boost.Threads regression results for meta-como-win32-4.3.3-vc7 at http://boost.sourceforge.net/regression-logs/developer/thread.html all fail because: <quote> "C:\Users\Administrator\boost\main\boost\boost/config/requires_threads.hpp", line 29: catastrophic error #35: #error directive: "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" # error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" </quote> The reason BOOST_DISABLE_THREADS is defined is because -DBOOST_DISABLE_WIN32 being passed on the command line. Does anyone know whether this option is on the command line on purpose, or should I consider it a configuration error for that toolset? Mike

3 2

Re: [boost] Problems with program_options using GCC 3.4 on FreeBSD
by Robert Ramey 22 Jul '04

22 Jul '04

Jonathan Wakely wrote: >> Any chance we might convince you to run the whole test suite on the >> platform? I would be curious as to the results for the serialization >> library here. >Sure, but .. >I'm not able to compile it yet - more patches will be coming shortly. >The problems mostly stem from the fact that FreeBSD 4.x doesn't support >std::wstring, std::wstreambuf etc. >e.g. >libs/serialization/src/basic_text_wiprimitive.cpp should test >BOOST_NO_STD_WSTREAMBUF before using std::wistream >The wchar.h header is present, but incomplete, so GCC on FreeBSD doesn't >define the _GLIBCXX_USE_WCHAR_T macro, disabling all wchar_t support in >the C++ library. The serialization library is set up as two libraries. Serialization.lib and wserialization.lib. If there isn't proper support for wide chars, the later fails to build and the tests that depend upon fail to pass. This is what happens when I test gcc on cygwin. So the fact that there is no wide char support on a particular platform should be no problem as far as the serialization library is concerned. Of course in such environments wide char use has to be avoided. Robert Ramey

2 1