- Boost-users - lists.boost.org

Re: [Boost-users] [BULK] Re: [range] From 1.33.0 gives newwarningvs 1.32
by Sohail Somani 16 Aug '05

16 Aug '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > David Abrahams > Sent: Monday, August 15, 2005 2:55 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [BULK] Re: [range] From 1.33.0 > gives newwarningvs 1.32 > > Thorsten, the difference is in fragility over time with > maintenance. That's why the compiler issues the warning. Any > decent beginner's book on C++ will advise you to eschew all > casts, and prefer the new-style ones. Do you really need to > have the fundamentals of good > C++ programming practice explained? > > Incidentally, if you find that the proper C++ construct is > "less portable. somehow." you should use BOOST_WORKAROUND to > isolate the compiler for which it fails to work, if only so > that the reason for the workaround is documented. I thought the same thing but my name isnt Dave Abrahams and I don't have an important email address. Doh.

2 1

Re: [Boost-users] [serialization][1.33.0?] xml_iarchive leak
by Richard Jennings 16 Aug '05

16 Aug '05

> > > b) If I recall correctly, the borland version of scoped_ptr > fails when > > the type is incomplete - which makes it not useful for implementing > > the PIMPL idiom. > > it always fails unless the destructor is included first in > the cpp file IIRC. > Sadly this does not work on BCB even if the destructor is defined in the cpp file, which means that scoped_ptr can't be used for pimpl with this compiler. The details are here: http://lists.boost.org/Archives/boost/2001/12/21796.php You can of course use shared_ptr, but then the intention is less clear.

2 1

Re: [Boost-users] Maybe a problem with boost::object_pool?
by Labour, Matthieu (MLPRO SF) 16 Aug '05

16 Aug '05

Thank you for your answer Sorry about the wrong info RedHat: uname -a : Linux ejecxapeqdtmad01 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 athlon i386 GNU/Linux /etc/redhat-release: Red Hat Enterprise Linux AS release 3 (Taroon Update 5) GNU gcc version: gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52) I'll try to update gcc and run the test again Did you try to run the test and and crash the program? Thank you -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Caleb Epstein Sent: Thursday, August 11, 2005 4:51 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Maybe a problem with boost::object_pool? On 8/9/05, Labour, Matthieu (MLPRO SF) <matthieu_labour(a)ml.com> wrote: > I use Red Hat linux 3.2.3-47 Are you sure that is the version you're using? That doesn't look like a RedHat version number. What does "uname -a" tell you, and what is the contents of /etc/redhat-release? I have: Linux scsefpldcs0213 2.4.21-27.0.4.ELhugemem #1 SMP Sat Apr 16 18:22:53 EDT 2005 i686 i686 i386 GNU/Linux Red Hat Enterprise Linux AS release 3 (Taroon Update 4) > Gcc version 3.2.3 20030502 Perhaps the compiler is at fault here. Thats an old-ish version of GCC. I use 3.3.4. It could also be a buggy GNU libc or libstdc++ if you're on an older RedHat version. -- Caleb Epstein caleb dot epstein at gmail dot com _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

2 1

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