- Boost - lists.boost.org

boost log lib 1.3 compile failure w/gcc
by Neal Becker 10 May '05

10 May '05

I am looking at boost log library 1.3. I tried to compile "simple" example with gcc-3.4.3 (linux), here's what happens: g++ -o main main.cpp -I ../../../../ In file included from ../../../../boost/log/detail/ts.hpp:37, from ../../../../boost/log/log_fwd.hpp:34, from ../../../../boost/log/log.hpp:36, from ../../../../boost/log/log_impl.hpp:33, from main.cpp:4: ../../../../boost/log/detail/ts_posix.hpp: In constructor `boost::logging::threading::mutex::mutex()': ../../../../boost/log/detail/ts_posix.hpp:54: error: no matching function for call to `pthread_mutex_t::._10(int)' /usr/include/bits/pthreadtypes.h:87: note: candidates are: pthread_mutex_t::._10() /usr/include/bits/pthreadtypes.h:87: note: pthread_mutex_t::._10(const pthread_mutex_t&) In file included from ../../../../boost/log/log_impl.hpp:33, from main.cpp:4: ../../../../boost/log/log.hpp: At global scope: ../../../../boost/log/log.hpp:277: error: declaration of `bool boost::logging::logger_keeper_is_enabled<is_compile_time, is_enabled>::is_enabled(boost::logging::logger&) const' ../../../../boost/log/log.hpp:276: error: shadows template parm `bool is_enabled' ../../../../boost/log/log.hpp:277: error: declaration of `bool boost::logging::logger_keeper_is_enabled<is_compile_time, is_enabled>::is_enabled(boost::logging::logger&) const' ../../../../boost/log/log.hpp:276: error: shadows template parm `bool is_enabled' C

2 4

Re: [dynamic_bitset] Stream extraction failures on CodeWarrior 9.4
by Gennaro Prota 10 May '05

10 May '05

--- Howard Hinnant <hinnant(a)twcny.rr.com> wrote: > I know the Metrowerks library inside/out. I started looking at this > last night but I'm pretty lost in the test code. I see. It's not the clearest code in the world. It is logically simple but a bit hard to debug due to the high number of combinations (and workarounds) involved. > > Here's what I have so far: > > Failure inside of: > > template<typename Stream, typename String> > static void stream_extractor(Bitset& b, > Stream& is, > String& str > ) > > at: > > if(stream_was_good) > BOOST_CHECK(remainder == str.substr(after_digits)); > > At this point remainder is a zero-length string, after_digits is 0 and > str is length 359. That's odd. after_digits is the position of the first character that follows 1s and 0s. The 359-characters str parameter should be the long string defined in bitset.hpp, thus you should have at least after_digits==359. I may be wrong because I don't have the necessary time and calm to check the code from the office but it might be worth examining this part. In particular if, for some reason, is_one_or_zero() is immediately returning false. > > On entry to this routine b has length 1 and that element is true. I > believe, but I am not positive that str is unmodified through this > test, despite being passed by reference (as opposed to const ref). > > I've so far been unable to determine the state of the stream is on > entry. But it looks completely hosed by the time the BOOST_CHECK is > triggered. For example the iostate has the value 0x7E even though the > highest numerical state it can possibly have is 0x07. That's odd too. I'll continue reading this thread via mail. Please keep me informed and sorry for not being able to dig into this myself. -- Genny Discover Yahoo! Find restaurants, movies, travel and more fun for the weekend. Check it out! http://discover.yahoo.com/weekend.html

1 0

Standard Library Extension TR2 Call for Proposals
by Beman Dawes 10 May '05

10 May '05

The C++ Standards Committee has begun work on a second library technical report. A Call for Proposals is available at http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1810.html --Beman

1 0

When 1.33 is released...
by Gordon Smith 10 May '05

10 May '05

As soon a 1.33 is released can we up the version number to 1_33_1 or such like in CVS, as this will make switching between HEAD and gold a lot easier? Gordon.

2 3

two boost.org doc section requests
by Max Khesin 10 May '05

10 May '05

1) Boost version in which the library was introduced. 2) The required header and object lib. I think these will improve the usability of documentation. Thanks, Max. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

1 0

Allocators in VC 8.0?
by Doug Gregor 10 May '05

10 May '05

Does anyone know of any weird behavior from allocators in VC 8.0? The Function library uses allocators when available, but the two tests of allocators (allocator_test and function_test) are failing on VC 8.0 (but not 7.1). From the config info, I see that BOOST_HAS_PARTIAL_STD_ALLOCATOR is defined but BOOST_NO_STD_ALLOCATOR is not (boost::function uses the latter). The actual failure is here: http://tinyurl.com/dq3lh Could someone with access to VC 8.0 (beta 2, I guess) check to see what is happening here? Doug

4 3

RE: [boost] Critique of Boost.Threads
by Jon Kalb 10 May '05

10 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes > Sent: Wednesday, May 04, 2005 6:31 AM > To: Boost mailing list > Subject: [boost] Critique of Boost.Threads > > With Kevlin Henney's permission, the following is a repost of > a message he recently posted on the C++ committee's library > reflector. It gives his views on Boost.Threads in the context > of possible standardization. > > --Beman > > ------- I have a (newbie) question about the joiner API. > And usage as follows: > > void void_task(); > int int_task(); > ... > joiner<void> wait_for_completion = thread(void_task); > joiner<int> wait_for_value = thread(int_task); > ... > int result = wait_for_value(); > wait_for_completion(); In the code snippet above does the line "int result = wait_for_value();" block until the completion of the thread? (It must or there is no way of knowing if the value of result is valid.) Is there a way for the client to avoid the block by checking whether or not thread is completed so that the call won't block... Some sort of wait_for_value.is_done()? -- Jon Kalb jonkalb(a)microsoft.com

3 2

[Integer] Libraries needs to be taught about Compaq Tru64 UNIX
by Douglas Gregor 10 May '05

10 May '05

Someone with access to Compaq Tru64 UNIX could probably fix the two COMSOFT errors in the Integer library: http://www.meta-comm.com/engineering/boost-regression/cvs-head/ developer/integer.html in a manner of minutes. It's likely some preprocessor magic that needs to be introduced. Doug

3 2

Re: Singleton Review: GCC compiler errors
by Jason Hise 10 May '05

10 May '05

Tobias Schwinger wrote: > Jason Hise wrote: > >> Sorry about the duplicate messages, thunderbird seemed to be having a >> problem. Hoping it's fixed now. >> >> Jason Hise wrote: >> >>> Tom Brinkman wrote: >>> >>>> Was the "singleton" library tested on GCC. I'm getting many >>>> compiler errors on 3.34. >>> >>> >>> >>> It was a while back, but many changes have been made since then. >>> I'll see if I can track down a copy of gcc to try compiling with it >>> myself. >> >> >> >> Actually, now that I'm looking into it it appears that Dev C++ uses a >> port of GCC by default, and I have successfully tested the latest >> version with Dev C++, getting no warnings or errors. What error >> messages are you getting? >> > > Are you sure you had all warnings enabled (-Wall) ? > > It was rather loud on my system. However, I could successfully build > tests and example with both 3.2 and 3.4 (both MinGW32). > > I'll send the output to you in private mail. Thanks for the heads up that I needed to use the -Wall option (I'm not used to working with gcc). I am now getting the same warnings that you sent to me, and am working to correct them. In many cases I am getting the warning that specific classes have virtual functions, but non virtual destructors. This is intentional, because they only have virtual functions in debug mode (pure virtual, to make the singleton uncreatable by client code) and will never be destroyed through a pointer to base. I wanted to avoid the overhead of a vtable in release mode. Is there a way to disable this specific warning while compiling with gcc? -Jason

8 10

[dynamic_bitset] Stream extraction failures on CodeWarrior 9.4
by Doug Gregor 10 May '05

10 May '05

The stream extraction operators for dynamic_bitset are failing on CodeWarrior 9.4. See: http://tinyurl.com/addko Is anyone familiar enough with the quirks of Metrowerks' iostreams to fix this issue? Doug

1 0