- Boost - lists.boost.org

[shared_array] Initialisation - could this subtle user bug be avoided?
by Paul Giaccone 13 Mar '06

13 Mar '06

I had some code in my program that created and initialised a shared_array. When the shared_array was deleted, the program crashed with an exception that suggested I had written beyond the end of the array. I realised that the problem was I had written: boost::shared_array<double> foo(new double(num)); instead of: boost::shared_array<double> foo(new double[num]); (For those without sharp eyes, that's parentheses instead of square brackets.) The compiler was perfectly happy with this, of course, because new double(num) is perfectly good syntax. Is there any way that this bug could be caught at compile time? Perhaps the solution might be to provide a separate constructor (a convenience function) that took only a "size" parameter and did the "new" for you: boost::shared_array<double> foo(num); Paul

1 0

[type_traits]: is_movable
by Vaclav Vesely 13 Mar '06

13 Mar '06

This is a duplicate. I sent this to the wrong thread by mistake. I'm sorry. Hi, draft of the is_movable trait is attached. Notes: - Implicit implementation is based on the has_trivial_copy trait. - For STL configurations, which defines BOOST_HAS_MOVABLE_STL, is_movable.hpp declares STL containers (and their const versions) as movable. Partial template specialization is required (!defined(BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION)). Open issues: - I'm not sure with volatiles. has_trivial_copy declares volatile types explicitly as not has_trivial_copy. I don't know why but is_movable should probably follow this. - I have tested with MSVC (6, 7.1 and 8) and GCC (3.2.3 - MinGW) compilers. MSVC is fine but GCC complains with specializations for STL types. It seems to be related to a different macro expansion strategy of preprocessor. I'm not able to use BOOST_PP_COMMA macro correctly. I will appreciate any help. Regards, Vaclav

1 0

[cvs] waiting for vawjr's lock
by Johan Nilsson 13 Mar '06

13 Mar '06

Hi, I keep getting this message (for well over an hour now) when trying to update from cvs: cvs update: [11:30:16] waiting for vawjr's lock in /cvsroot/boost/boost/boost/spirit/fusion/iterator/detail/joint_view_iterator I guess this is some kind of stale lock. Is it possible to tell cvs to skip to the next file when encountering this? // Johan

2 2

XML data binding
by Agarwal, Abhishek 13 Mar '06

13 Mar '06

Hello, I was wondering with BOOST currently has any XML data binding library. Any comments? Thanks, Abhi

1 0

stale lock in CVS?
by Roland Schwarz 13 Mar '06

13 Mar '06

Currently the checkout or update hangs with the following message: cvs checkout: [11:41:50] waiting for vawjr's lock in /cvsroot/boost/boost/boost/spirit/fusion/iterator/detail/joint_view_iterator Is there anything that can be done about this? Roland

2 1

[asio] available port
by Jeff Flinn 13 Mar '06

13 Mar '06

I'm moving an MFC net app to asio. In that app CAsyncSocket/CSocket are created using port=0, which MFC docs states: 'Windows Sockets to select a port'. Is there a similar facility in asio? If not any suggestions on a portable technique to get an available port? Thanks, Jeff

4 6

[asio] static data member as buffer arg
by Jeff Flinn 13 Mar '06

13 Mar '06

Any obvious reason that supplying a static const data member to a buffer, for example: class Client { static const unsigned int sHandShakeGreeting = 0x01020304; ba::stream_socket mSock; ... void SomeFnc() { ba::async_write( aSocket , ba::buffer(&sHandShakeGreeting,4) , boost::bind( &Client::OnSent, this, _1, _2 ) ); } ... }; would behave differently from: const unsigned int sHandShakeGreeting = 0x01020304; class Client { ba::stream_socket mSock; ... void SomeFnc() { ba::async_write( aSocket , ba::buffer(&sHandShakeGreeting,4) , boost::bind( &Client::OnSent, this, _1, _2 ) ); } ... }; The above all occur within a .cpp file. In the latter case the dialog continues as expected, but the former results in the server(I don't have code for) not receiving a valid value. This is using VC7.1. Thanks, Jeff

2 1

Re: [boost] [vc-8_0]/EH option
by Martin Bonner 13 Mar '06

13 Mar '06

----Original Message---- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of David Abrahams Sent: 13 March 2006 08:41 To: boost(a)lists.boost.org Cc: boost-build(a)lists.boost.org Subject: Re: [boost] [vc-8_0]/EH option > "Gennadiy Rozental" <gennadiy.rozental(a)thomson.com> writes: > >> This is pretty critical and needs to be addressed before release. >> Unless we are going to be using BB2 > > We are. > >> and it does not have this problem. > > I don't know whether it does or not. > >> But this needs to be stated. > > What does? That BB2 does not have this problem. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 203894

1 0

Re: [boost] [vc-8_0]/EH option
by Gennadiy Rozental 13 Mar '06

13 Mar '06

This is pretty critical and needs to be addressed before release. Unless we are going to be using BB2 and it does not have this problem. But this needs to be stated. Gennadiy

2 1

[serialization] const-correctness
by David Abrahams 13 Mar '06

13 Mar '06

In giving a presentation about the serialization library on Tuesday the students got very hung up on the const-correctness of output streaming using the usual single serialize(MyClass&, ... ) function. Can you serialize const objects that way? Does the library cast away const? One could get the compiler to deduce constness appropriately if the object being serialized were specified as: template<class Archive, class GPSPosition> void serialize(Archive & ar, GPSPosition& g, const unsigned int version) but of course that doesn't overload very well; you'd need some other way to indicatethe type of the object to be serialized. How is this all related to http://www.boost.org/libs/serialization/doc/index.html? (and there are some weird glyphs showing up at the top of the menu at http://www.boost.org/libs/serialization/doc/index.html for me: ï»¿ that's a lowercase 'i' with diaresis, a spanish right double quote character (looks like >>) and an inverted question mark.) Thanks in advance, Dave -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3