August 2005 - Boost-users - lists.preview.boost.org

Problem with Comeau 4.3.3 (compilation)
by pisalmon＠numericable.fr 16 Aug '05

16 Aug '05

Hi, I have some problem with boost compilation when I use Comeau 4.3.3 Compiler (with gcc 3.3.5 on Ubuntu Hoary) and bjam tools : The signal librairy cant compile. Do you known why ???

1 0

Re: [Boost-users] [range] From 1.33.0 gives new warning vs 1.32
by Peter Foley 16 Aug '05

16 Aug '05

Hi, "Thorsten Ottosen" <nesotto(a)cs.aau.dk> wrote in message news:<ddqm49$tjf$1(a)sea.gmane.org>... > > what's the difference? A c-style cast is also a const-cast. > > -Thorsten I notice nobody has pointed you in this direction but Scott Meyers in more Effective C++ discusses in Item 2 ("Prefer C++ style casts") why it is preferable to use the new C++ style casts. Key points: * Easier to understand why a cast is happening * You can explicitly say what you are casting to * It is much easier to search for exactly where you are casting in your code * More fine grained control I am not a fantastic programmer but I feel that I have learnt a lot from his books. Out of all the reference/text books that I have purchased I think these books have been the best. Peter.

1 0

Re: [Boost-users] [serialization]save/load objects to/from a block of memory?
by Jasper, Alexander 16 Aug '05

16 Aug '05

Hi! >> Li Lirong wrote: > > How can I save/load my c++ objects to/from a block of memory using > > Boost.Serialization? Can anyone give some sample code? > > You can simply stream into a std::stringstream: > > std::stringstream stream; > { > boost::text_oarchive oa(stream); > oa << my_data; > } > But don't do that with to much data. I tried that with a similar approach, but it didn't work. It is far better to serialize to a lot of 'small' (e.g. 64K) blocks rather a huge one (100MB) that needs, even worse, to be realloced once and again. This completely fragmented the address space in my app. Of course this only important, if you are dealing with bigger amounts of data. If you are interested I could send you my implementation of a stream buffer that uses fixed size blocks. I'm not completely satisfied with it, though. I still suffers from scalability problems. kind regards Alex

1 0

[range] From 1.33.0 gives new warning vs 1.32
by Kevin Wheatley 16 Aug '05

16 Aug '05

I had some code that with 1.32 compiled fine when compiled with warnings as errors, but now with 1.33 I get: cc1plus: warnings being treated as errors boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp: In function `Char* boost::range_detail::str_end(Char*) [with Char = char]': boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/end.hpp:96: instantiated from here boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp:57: warning: cast from `const char*' to `char*' discards qualifiers from pointer target type boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp: In function `Char* boost::range_detail::str_end(Char*) [with Char = wchar_t]': boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/end.hpp:101: instantiated from here boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp:57: warning: cast from `const wchar_t*' to `wchar_t*' discards qualifiers from pointer target type Compiled with gcc 3.2.3 under Linux, perhaps something like this is needed? Thanks Kevin --- boost_1_33_0/boost/range/detail/implementation_help.hpp 2005-05-05 13:58:51.000000000 +0100 +++ boost_1_33_0_gcc_3.2.3/include/boost-1_33/boost/range/detail/implementation_help.hpp 2005-08-15 11:33:59.000000000 +0100 @@ -54,7 +54,7 @@ template< class Char > inline Char* str_end( Char* s ) { - return (Char*)str_end( s, s ); + return const_cast<Char*>(str_end( s, s )); } template< class T, std::size_t sz > -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself |

4 5

auto linking and 'system' layout
by Serge Skorokhodov 16 Aug '05

16 Aug '05

Hi, I attempted to use boost built with system layout (vc-7_1) to simplify deployment etc. Unfortunately, my code failed to link as the linker tried to link the date_time libraries with TOOLS and version marks (I'm not sure about other libraries as it was fatal enough:). Is this a known limitation of auto linking? Is there a workaround? I haven't search the documentation real thoroughly but no hints of how to turn auto linking off...:( TIA -- Serge

3 7

Re: [Boost-users] [BULK] Re: [BULK] Re: [range] From 1.33.0 gives new warningvs 1.32
by Sohail Somani 15 Aug '05

15 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Thorsten Ottosen > Sent: Monday, August 15, 2005 2:38 PM > To: boost-users(a)lists.boost.org > Subject: [BULK] Re: [Boost-users] [BULK] Re: [range] From > 1.33.0 gives new warningvs 1.32 > Importance: Low > > > > > > perhaps something like this is needed? > > > > > > > template< class Char > > > > > inline Char* str_end( Char* s ) > > > > { > > > > - return (Char*)str_end( s, s ); > > > > + return const_cast<Char*>(str_end( s, s )); > > > > > > what's the difference? A c-style cast is also a const-cast. > > > > You didn't just say that. > > Apparently I did. > > What's the difference in the generated object code? A small percentage of people read object code on a regular basis. I tend to read the source more.

1 0

[serialization]save/load objects to/from a block of memory?
by Li Lirong 15 Aug '05

15 Aug '05

Hi, How can I save/load my c++ objects to/from a block of memory using Boost.Serialization? Can anyone give some sample code? Thanks, Lirong

2 1

Troubles with Boost.Log
by martin f krafft 15 Aug '05

15 Aug '05

Dear all, I have been spending the last two days trying to get John Torjo's logging library[0] working, but I am failing even though I can already see the goal[1]. Unfortunately, John seems to be on vacation or is otherwise occupied so as to not find time to answer my emails. Thus I turn to you... I have two problems right now, one small and one rather large one. The small one may well be my own confusion. Like most Boost libraries, Boost.Jam turns Boost.Log into eight different libraries: the permutations of release or debug, threade or not, and static or shared. For my first tests, I chose the single-threaded, static, release library. However, even the simplest programme segfaults in the weirdest places until I tell the linker to also link in libpthread (or Boost.Thread). What gives? Why does a single-threaded library need pthreads? The larger problem is a heisenproblem, that is I cannot pin it down, which is largely a problem due to libpthread mucking about with gdb in a way I can't seem to control. In a nutshell though, log messages sometimes get written twice, sometimes not at all, and all this without any threads or caching. So once I figured out how to make it work without pthreads, I'll be back with more. Any hints? 0. http://www.torjo.com/code/logging.zip 1. http://lists.debian.org/debian-devel/2005/08/msg00768.html -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp (sub)keys? use subkeys.pgp.net as keyserver! spamtraps: madduck.bogus(a)madduck.net "a fundamentalist is someone who hates sin more than he loves virtue." -- john h. schaar

1 0

boost::xtime
by Luca Zappella 15 Aug '05

15 Aug '05

Hi all, I would like to use boost mutex with TimedLock concept but I ran into the boost::xtime type. The problem is that I can not understand the second parameter of the method: int xtime_get(xtime*, int) In the doc I can not find anything, can someone help me? Thanks a lot, Luca

2 1

Re: [Boost-users] Problems: Building Boost with VC7 and STLport4.6.2
by Jasper, Alexander 15 Aug '05

15 Aug '05

Hi! If you are using VC7 rather VC 7.1 you of course use -sTOOLS=vc-7-stlport instead of -sTOOLS=vc-7_1-stlport. But VC7 is crap. If it is possible I strongly recommend you to upgrade to 7.1 which really works a lot of better than any release before. Also make sure you do a clean rebuild to prevent old compiler switches being stored in the precompiled header files. Boost further requires you to enable the debug mode of stl-port, if I'm not mistakes. Adding the following to stl-user-config.h solved things for me. #ifdef NDEBUG #undef _STLP_DEBUG #else #define _STLP_DEBUG 1 #endif BTW. STLPort 4.6.2 does not work well in conjunction with boost.serialize. A bug in the ostream::write method prevents it from handling writing 0 bytes correctly. Unfortunately the serializer writes 0 bytes in case of empty strings for instance. kind regards Alex > > Thanks a lot for your reply! I tried your method and it > works! All the compiler errors disappeared. I think the > important thing is to turn the feature "stlport-iostreams" on. > But the linker still asks me for something like > "stlport_vc6.lib". I'm using vc7 now. And I built STLport > 4.6.2 also with vc7. But the linker still asks me for > something related to vc6. Does any one know the possible causes? > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0