May 2008 - Boost - lists.preview.boost.org

Attn: BoostCon Attendees interested in C++0x
by Douglas Gregor 06 May '08

06 May '08

For those interested in attending the "Implementing a mini Boost.Fusion using C++0x" workshop, we suggest that you install a compiler capable of handling some of the C++0x features discussed today, especially decltype, variadic templates, and rvalue references. GCC 4.3 is one such option. For Windows users: MINGW is the fastest way to get GCC 4.3. Here are the steps: 1) Download the automated installer for MINGW, here: http://sourceforge.net/project/showfiles.php? group_id=2435&package_id=240780 When running the installer, you only need to install the "minimal" set of files. 2) Download the "core" and "g++" GCC 4.3.0 binaries from here: http://www.tdragon.net/recentgcc/ 3) Unzip the two files over top of your MINGW distribution, which replaces the default (ancient) compiler with GCC 4.3. 4) Try to compile a simple problem, e.g., "static_assert(false, "It works!");" with c:\mingw\bin\g++ -std=c++0x foo.cpp For Mac users: MacPorts has a version of GCC 4.3, which should be installable with: sudo port install gcc43 Fink also has a version of GCC 4.3 in the unstable distribution. Once you've configured for the unstable distribution, use: fink install gcc43 For Linux users: You can build GCC 4.3 on your own (get the source at gcc.gnu.org) or perhaps be lucky enough to find a binary for your particular distribution. - Doug

3 2

C++ Memory Management Innovation: GC Allocator
by shiwei xu 06 May '08

06 May '08

Most of the C++ programmers do not benefit from "Garbage Collection" technique (GC). They are sick of deleting objects but have to do this. There are some C/C++ memory GC implementations, but they are complex and are not widely used. I am going to introduce a new memory management technique named "GC Allocator". "GC Allocator" isn't an implementation, but a concept. Now, we have two "GC Allocator" implementations, named "AutoFreeAlloc" and "ScopeAlloc". This article consists of three parts: 1. What is GC Allocator? 2. GC Allocator implementations: ScopeAlloc and AutoFreeAlloc 3. Applications based on GC Allocator For more information, see http://www.codeproject.com/KB/cpp/gc-allocator.aspx To obtain a copy of this paper in pdf format click here<http://xushiwei.com/local--files/gc-allocator/GCAllocator.pdf>(or from google code <http://code.google.com/p/stdext/downloads/list>).

9 42

Trunk Boost Jam version users need to recompile.
by Jurko Gospodnetić 05 May '08

05 May '08

Hi all. Just a heads up that anyone using the trunk version of Boost Build newer than revision 45158 and the trunk version of Boost Jam (version 3.1.17) older than that revision needs to recompile their Boost Jam. Note that this does not affect people using the current release version (3.1.16) as the new Boost Build code preserves old behavior for older versions. This includes testers since they use the release version of Boost Jam. Without this recompile the thing that can happen is that some paths get parsed incorrectly. Best regards, Jurko Gospodnetić

1 0

Re: [boost] [Boost-build] BJam-Plugin for Eclipse
by Darren Garvey 05 May '08

05 May '08

On 05/05/2008, Frank Birbacher <bloodymir.crap(a)gmx.net> wrote: > > > > So, did you figure if you have trunk access? > > I did now: > > $ svn mv > http://svn.boost.org/svn/boost/sandbox-branches/birbacher/eclipse_contrib > > http://svn.boost.org/svn/boost/trunk/tools/build/v2/contrib/eclipse_plugins > -m "moved Eclipse plugins into trunk" Just a guess: try the same with https:// (note the 's'). -- Darren

2 1

throw_exception: gcc 3.2 errors
by Ralf W. Grosse-Kunstleve 05 May '08

05 May '08

Thanks a lot for the gcc warning workarounds! It is highly appreciated. Unfortunately, now g++ 3.2 doesn't work anymore. See below. I think gcc 3.3 and higher are fine. Ralf g++ (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-20) boost svn rev. 45087 % cat te.cpp #include <boost/throw_exception.hpp> % g++ -Wall -Iboost -c te.cpp In file included from boost/boost/exception/enable_error_info.hpp:9, from boost/boost/throw_exception.hpp:39, from te.cpp:1: boost/boost/exception/exception.hpp: In instantiation of `boost::detail::sp_convertible<boost::exception_detail::error_info_container, boost::exception_detail::error_info_container>': boost/boost/exception/exception.hpp:75: instantiated from `boost::detail::sp_enable_if_convertible<boost::exception_detail::error_info_container, boost::exception_detail::error_info_container>' boost/boost/exception/exception.hpp:75: instantiated from here boost/boost/exception/exception.hpp:75: invalid use of undefined type `struct boost::detail::sp_convertible<boost::exception_detail::error_info_container, boost::exception_detail::error_info_container>' boost/boost/detail/sp_convertible.hpp:27: declaration of `struct boost::detail::sp_convertible<boost::exception_detail::error_info_container, boost::exception_detail::error_info_container>' boost/boost/exception/exception.hpp:75: enumerator value for `value' not integer constant

2 1

[smart_ptr] enable_shared_from_this / sp_accept_owner / virtual dtor
by Daniel Frey 05 May '08

05 May '08

In case someone is interested: The attached enable_shared_from_this proves that it is possible to add sp_accept_owner without forcing a virtual dtor. It's compatible with the 1.35.0 features and overhead. Regards, Daniel

2 3

[smart_ptr] future shared_from_this
by Frank Mori Hess 05 May '08

05 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Another idea would be to make a future<shared_ptr<T> > available in the constructor, the future would become ready with a shared_ptr from this when the object gets owned. - -- Frank -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIH0d65vihyNWuA4URAoUeAKDIBtVOn2S9sdOiHvPXNNRHBIJu6gCfZN4X 69bJ4nlhOHSf6dfLaEKpQ5Q= =74HG -----END PGP SIGNATURE-----

1 0

[1.35][lexical_cast][concept check][range] Build error and warnings with MSVC8 on Warning Level 4
by Stephan Diederich 05 May '08

05 May '08

As we tried to update to 1.35 today, we found some warnings with MSVC on Warning Level 4 in: lexical_cast: There was a return statement after a call to throw_exception which causes a unreachable code warning. I can see no problem by just removing that return. see http://svn.boost.org/trac/boost/ticket/1791 concept_check: BOOST_concept(SGIAssignable,(TT)) causes two warnings: C4510: default constructor could not be generated C4610: object 'class' can never be instantiated - user-defined constructor required solved thorugh pragmas see http://svn.boost.org/trac/boost/ticket/1792 and an error in range/iterator_range: see http://svn.boost.org/trac/boost/ticket/1793 for details. The patch is attached, as I was not able to discuss with Akismet that it's no spam ;) "Submission rejected as potential spam (Akismet says content is spam)" cheers, stephan

4 7

1.35 + gcc4.3?
by Neal Becker 05 May '08

05 May '08

Will patches to build on gcc-4.3 make it into boost-1.35 release? Would be desirable. Fedora F9 is out soon and has gcc-4.3 - I think other distributions will follow soon.

2 1

Header only pro's and con's?
by Roland Schwarz 04 May '08

04 May '08

Please don't misunderstand this mail. I do not want to start a header contra lib war. I just want to learn about the pro's and the contras of header only. The issue has popped up in this list quite some times, but I was not able to find any document which tries to do a serious in-depth discussion of when to header only and when not. If anyone knows about such a document I would be pleased if he could point me at it. Thank you. -- _________________________________________ _ _ | Roland Schwarz |_)(_ | aka. speedsnail | \__) | mailto:roland.schwarz@chello.at ________| http://www.blackspace.at

4 3