February 2006 - Boost - lists.preview.boost.org

Patch for smart pointers assignation of plain pointers
by Pierre THIERRY 15 Jun '06

15 Jun '06

It seems to me that smart pointers could have the same semantics that plain pointers have (it's also the orientation taken by other smart pointers, like those in Glibmm). Here is my proposed patch against CVS HEAD: Index: boost/scoped_ptr.hpp =================================================================== --- boost/scoped_ptr.hpp.orig +++ boost/scoped_ptr.hpp @@ -101,6 +101,12 @@ return *this; } + scoped_ptr & operator=(T * rhs) + { + this_type(rhs).swap(*this); + return *this; + } + T * get() const // never throws { return ptr; Index: boost/shared_ptr.hpp =================================================================== --- boost/shared_ptr.hpp.orig +++ boost/shared_ptr.hpp @@ -246,6 +246,12 @@ #endif // BOOST_NO_SFINAE, BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION + shared_ptr & operator=(T * r) + { + this_type(r).swap(*this); + return *this; + } + #endif // BOOST_NO_AUTO_PTR #if !defined(BOOST_MSVC) || (BOOST_MSVC >= 1300) Regards, Nowhere man -- nowhere.man(a)levallois.eu.org OpenPGP 0xD9D50D8A

2 5

bug in filesystem::wpath
by Mark Bartosik 31 Mar '06

31 Mar '06

bug in filesystem::wpath. In mirgrating to support wchar_t, a couple of lines were missed. m_path which has type of std::wstring is assigned a narrow character string resulting in a compilation error. inline below is a patch: +++ C:\Boost_CVS\CVSROOT\boost\boost\filesystem\path.hpp Wed Feb 22 22:52:11 2006 @@ -249,8 +249,8 @@ ~basic_path() {} // assignments - basic_path & operator=( const string_type & s ) { m_path=""; operator/=( s ); return *this; } - basic_path & operator=( const value_type * s ) { m_path=""; operator/=( s ); return *this; } + basic_path & operator=( const string_type & s ) { m_path.clear(); operator/=( s ); return *this; } + basic_path & operator=( const value_type * s ) { m_path.clear(); operator/=( s ); return *this; } # ifndef BOOST_NO_MEMBER_TEMPLATES template <class InputIterator> basic_path & assign( InputIterator first, InputIterator last ) I've taken a look for similar bugs and couldn't find any. Thanks

4 14

New implementation of remove_xxx for vintage compilers
by Peder Holt 28 Mar '06

28 Mar '06

Hi. I have started implementing some of the missing type_traits functionality for vintage compilers using typeof. The following are complete, and seem to work flawlessly on VC 6.5 and 7.0: remove_pointer remove_reference remove_bounds The source is available at: http://groups.yahoo.com/group/boost/files/typeof_vintage.zip The use of typeof in this respect, makes remove_xxx much more flexible. Would it be possible to start using this scheme for compilers without partial template specialization support? #define BOOST_MAX_TYPEOF_SIZE 20 #include <boost/test/minimal.hpp> //Include typeof_define.hpp in all header files where new types are added to typeof. #include <boost/typeof/typeof_define.hpp> #include <complex> #include <boost/type_traits/remove_reference.hpp> #include <boost/type_traits/remove_pointer.hpp> #include <boost/type_traits/remove_bounds.hpp> #include <boost/type_traits/is_same.hpp> template<typename A0> struct X {}; template<typename A0,unsigned int A1> struct Y {}; template<typename A0,typename A1,long A2> struct Z {}; BOOST_TYPEOF_DEFINE_TEMPLATE(X,1,(typename)) BOOST_TYPEOF_DEFINE_TEMPLATE(Y,2,(typename,unsigned int)) BOOST_TYPEOF_DEFINE_TEMPLATE(Z,3,(typename,typename,long)) BOOST_TYPEOF_DEFINE_TEMPLATE(std::complex,1,(typename)) int test_main(int, char*[]) { BOOST_TEST((boost::is_same<X<int>* const[8][9],boost::remove_bounds<X<int>* const[5][8][9]>::type>::value)); BOOST_TEST((boost::is_same<Z<X<double&>,Y<bool[4][7],12324>,0>* const*,boost::remove_pointer<Z<X<double&>,Y<bool[4][7],12324>,0>* const**volatile>::type>::value)); //VC7.1 fails to compile remove_reference. BOOST_TEST((boost::is_same<Y<int,345>** const,boost::remove_reference<Y<int,345>** const&>::type>::value)); typedef BOOST_TYPEOF(5.+std::complex<double>(6,7)) result_type; BOOST_TEST((boost::is_same<result_type,std::complex<double> >::value)); return 0; } -- Peder Holt

8 29

MPC support for Boost
by Kevin Heifner 22 Mar '06

22 Mar '06

After seeing some posts about people having difficulties building Boost with bjam and Dave Abrahams comment about wishing to add Microsoft solution files as an alternative build option. OCI decided to add MPC (http://www.ociweb.com/products/mpc) support to Boost. Chad Elliott the creator of MPC put together the zip file in Boost Vault under Miscellaneous which contains the necessary files to add MPC support to Boost. Here is a little description of the addition. It would be great if this could be added to Boost and something similar to this description added to the getting started web page. Building Boost using bjam is straightforward and easy to use for those used to building applications with make. However, for those who have little or no exposure to make may find building Boost with bjam somewhat confusing or difficult. The MPC application can be used to provide an alternate build mechanism for the Boost libraries. MPC (http://www.ociweb.com/products/mpc) can generate makefiles and projects for various build tools (make, Visual C++ 6.0, Visual Studio 7.1, etc.) Allowing users to choose their favorite build tool increases the appeal of Boost. We have put together boost.mwc (a workspace), a set of mpc files (projects) and a simple perl based configure script that allows MPC to generate a usable workspace (with projects) to build various libraries located in Boost. This perl based configure script is used to set up various required environment variables and then runs MPC. It takes a few options (most (coicide with the existing configure shell script), one of which is the --with-toolset option that converts the Boost toolset into the corresponding MPC options. The result of building Boost with MPC will leave the user with a set of libraries located in a "lib" directory at the top of the boost directory tree. The libraries are named as they would be when built with bjam. The current state of the .mwc file and perl based configure script only allows building multi-threaded versions of the Boost libraries. This is not meant to replace bjam, just provide an alternate way of building Boost. Thanks, KevinH -- Kevin Heifner heifner @ ociweb.com http://heifner.blogspot.com Object Computing, Inc. (OCI) www.ociweb.com

4 9

Re: [boost] [Release 1.34] Supported Compilers
by brangdon＠cix.compulink.co.uk 15 Mar '06

15 Mar '06

In-Reply-To: <drn6le$4d0$1(a)sea.gmane.org> rh_gmane(a)mac.com (Russell Hind) wrote (abridged): > Can't people still working with this just use 1.33.x version of boost? I completely agree. People who won't upgrade VC++ 6 shouldn't expect to upgrade boost. I see no need for "depreciated" here. (I'm speaking as a user who had to stick with VC++ 6 for a long time.) -- Dave Harris, Nottingham, UK.

2 1

[app submission] Paragent Manage
by Timothy Ritchey 14 Mar '06

14 Mar '06

Application: Paragent Manage 2.1 Company: Paragent URL: <http://www.paragent.com> Description: Paragent Manage is a Desktop Management Application that uses a lightweight agent written in C++. Unlike traditional desktop management solutions, Paragent Manage avoids the complexity and cost of servers by using peer-to-peer communication between agents and the administrative console. This allows real-time inventory searching, alerting and software auditing in an easy-to-deploy and maintain package. Boost Usage: We have used boost extensively throughout our agent, including: threads shared_ptr bind spirit date_time algorithm multi_index filesystem Apart from some read_write_mutex issues we had, boost has been a seamless part of our development, and has allowed us to develop and deploy a very complex, highly threaded networking agent with a built-in lisp-like xml-based scripting language all done in C++. Our entire development team would like to thank everyone for their hard work on behalf of C++ coders everywhere.

2 1

Re: [boost] [pkg-boost-devel] Bug#349209: boost: Boost Graph Library is non-free and undistributable in compiled form
by Steve M. Robbins 12 Mar '06

12 Mar '06

Dear Boost Graph Library Developers, The following is a reply to a bug report from a Debian user [http://bugs.debian.org/349209] pointing out deficiencies in the library licensing, from Debian's point of view. We'd like to know whether the few remaining files NOT available under the Boost Software License may be relicensed. Thanks. On Sat, Jan 21, 2006 at 04:21:38PM +0100, Francesco Poli wrote: > According to boost debian/copyright file, the > Boost Graph library does not seem to comply with the DFSG. That file is out of date. Most of the current boost source files are licensed under the Boost Software License [http://www.boost.org/LICENSE_1_0.txt] which I believe is OK by DFSG. I found the exceptions in the HEADER files using cd boost/graph find * -type f | xargs grep -L 'http://www.boost.org/LICENSE_1_0.txt' Of the exceptions these 8 are under the original GRAPH license: adjacency_list_io.hpp cuthill_mckee_ordering.hpp detail/sparse_ordering.hpp BLANKET king_ordering.hpp profile.hpp relax.hpp BLANKET sloan_ordering.hpp wavefront.hpp The two marked BLANKET, however, are actually available under the Boost Software License as all listed authors have granted permission to replace all existing licenses on their contributions to Boost with the Boost Software License, Version 1.0. [http://www.boost.org/more/blanket-permission.txt] For the record here are the set of authors and whether they appear on blanket-permission.txt: François Faure NO Andrew Lumsdaine YES Lie-Quan Lee YES Jeremy G. Siek YES Doug Gregor YES D. Kevin McGrath NO Marc Wintermantel NO Three more of the headers have MIT/BSD-like licenses which sound okay to me. They are as follows. File detail/bitset.hpp is from SGI with the following license: /* * Copyright (c) 1998 * Silicon Graphics Computer Systems, Inc. * * Permission to use, copy, modify, distribute and sell this software * and its documentation for any purpose is hereby granted without fee, * provided that the above copyright notice appear in all copies and * that both that copyright notice and this permission notice appear * in supporting documentation. Silicon Graphics makes no * representations about the suitability of this software for any * purpose. It is provided "as is" without express or implied warranty. */ File isomorphism.hpp is under the following license: // Copyright (C) 2001 Jeremy Siek, Douglas Gregor, Brian Osman // // Permission to copy, use, sell and distribute this software is granted // provided this copyright notice appears in all copies. // Permission to modify the code and to distribute modified code is granted // provided this copyright notice appears in all copies, and a notice // that the code was modified is included with the copyright notice. // // This software is provided "as is" without express or implied warranty, // and with no claim as to its suitability for any purpose. File property_iter_range.hpp is under the following license: // (C) Copyright François Faure, iMAGIS-GRAVIR / UJF, 2001. Permission // to copy, use, modify, sell and distribute this software is granted // provided this copyright notice appears in all copies. This software // is provided "as is" without express or implied warranty, and with // no claim as to its suitability for any purpose. File simple_point.hpp has no copyright at all. I presume this is an oversight and invite the Boost Graph authors to comment. > What is worse, it seems there's no permission to distribute > the Boost Graph Library in compiled form. The headers are only distributed as sources, so that should be OK, even if annoying and possibly non-free (see below). There is a small library that is compiled to libbgl-viz. This library has four source files, three of which are under Boost Software License. The exception is libs/graph/src/graphviz_lex.ll, which is under the origian graph license. On the other hand, the listed author, Lie-Quan Lee has given blanket permission, so we may apply the Boost Software License to it as well. > | Any disputes arising out of this Agreement or LICENSEE'S use of the > | software at any time shall be resolved by the courts of the state of > | Indiana. LICENSEE hereby consents to the jurisdiction of the Indiana > | courts and waives the right to challenge the jurisdiction thereof in > | any dispute arising out of this Agreement or Licensee's use of the > | software. > > This is a choice of venue, which is considered non-free by many > debian-legal regulars (including myself...). > People who accept this license may be forced to travel to the state > of Indiana, whenever the copyright holder decides to sue them (even > for frivolous claims, even if they live on the other side of the > ocean). This is a significant restriction on the exercise of the > rights granted by the license. This sounds like a serious problem. I'd hate to have to remove part of Boost from Debian. To the graph authors: is it possible that the remaining few files can be relicensed under BSL? Thanks, -Steve Robbins (co-maintainer of Boost for Debian)

4 3

Re: [boost] bug in filesystem::wpath
by Jan Hermelink 08 Mar '06

08 Mar '06

> PS: I'd like to hear from programmers using wide character file names. Are > they working OK? Are they meeting your needs? I use the wide character names for about three months with VC8 and after applying a similar patch like Mark I'm very satisfied with the library! Thank you. Three items doesn't meet my needs: As already reported in http://article.gmane.org/gmane.comp.lib.boost.devel/128277, narrow_path() doesn't work if short filename generation is disabled. As a workaround I have fstream.hpp patched for using the non-standard wide char fstream constructors in VC8 (Dinkumware library). Indeed this works for VC8 only... I would like to see a what() method in basic_filesystem_error. Ok, I have seen the free function what() but what it's the rationale not including it in the exception object? The documentation is yet incomplete (for instance the convenience functions are not documented I think). Jan -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes Posted At: Thursday, February 23, 2006 10:35 PM Posted To: Boost Developer Conversation: [boost] bug in filesystem::wpath Subject: Re: [boost] bug in filesystem::wpath "Mark Bartosik" <mbartosik(a)yahoo.com> wrote in message news:dtjclm$7dr$1@sea.gmane.org... > bug in filesystem::wpath. > In mirgrating to support wchar_t, a couple of lines were missed. > m_path which has type of std::wstring is assigned a narrow character > string resulting in a compilation error. Fixed in CVS. Test cases were also added to wide_test.cpp. Thanks, --Beman PS: I'd like to hear from programmers using wide character file names. Are they working OK? Are they meeting your needs? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

OT Query: Robert G. Burger and R. Kent Dybvig, "Printing Floating-Point Numbers Quickly and Accurately"
by Paul A Bristow 08 Mar '06

08 Mar '06

Sorry for an Off-topic question, but does anyone know of a C/C++ Implementation of a C++ algorithm based on the paper by Robert G. Burger and R. Kent Dybvig, entitled: "Printing Floating-Point Numbers Quickly and Accurately" http://portal.acm.org/citation.cfm?doid=989393.989430 ACM subscribers only http://citeseer.ist.psu.edu/cache/papers/cs/2654/http:zSzzSzwww.cs.indiana.e duzSz~burgerzSzFP-Printing-PLDI96.pdf/printing-floating-point-numbers.pdf Many thanks. Paul -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow(a)hetp.u-net.com http://www.hetp.u-net.com/index.html http://www.hetp.u-net.com/Paul%20A%20Bristow%20info.html

2 2

[date_time] [MSVC8] Memory leak in operator<<(ptime)
by Alo Sarv 08 Mar '06

08 Mar '06

The following test app illustrates a memory leak that I'v been able to produce so far with MSVC 8.0 (earlier versions not tested). GCC 4.0 seems to be unaffected. The leakage in case of this test app is around 12kb/s. #include <iostream> #include <boost/date_time/posix_time/posix_time.hpp> using namespace boost::posix_time; int main(int argc, char *argv[]) { ptime t(second_clock::local_time()); while (true) { std::cout << t << "\r"; } return 0; } Tested against Boost 1.33.1 release. Compiled with cl test.cpp /I c:\boost_1_33_1 /D _CRT_SECURE_NO_DEPRECATE /EHsc /D BOOST_ALL_NO_LIB -- Alo Sarv

6 15