- Boost - lists.boost.org

[phoenix] Phoenix & 1.37
by Robert Jones 08 Oct '08

08 Oct '08

I see the 1.37 release is gathering momentum. We will see any development of Phoenix in 1.37, following on from all the input of the recent review? - Rob.

2 1

config.hpp
by Joel Falcou 08 Oct '08

08 Oct '08

I'm digging up a previous topic of mine : http://article.gmane.org/gmane.comp.lib.boost.user/39236/match=config Basically, is it possible to consolidate the boost/config headers so they provide a macro usable in #ifdef and such so we can use Boost comprehensive platform/compiler tests in library ? I know some are already usable (like testing for BOOST_MSVC and such) but it lacks in some area like platform. My proposal is the following : For platform, stdlib and compiler config flag, add a macro called respectively : BOOST_ACTIVE_PLATFORM_CONFIG BOOST_ACTIVE_STDLIB_CONFIG BOOST_ACTIVE_COMPILER_CONFIG That contains a numeric value that identify the current chosen configuration. For each type of configuration, files called boost/config/platform_list.hpp,boost/config/stdlib_list.hpp and boost/config/compiler_list.hpp are provided. Those files contains the global list of possible active configuration and give them proper usable symbol. eg : platform_list.hpp #ifndef __BOOST_CONFIG_PLATFORM_LIST_HPP__INCLUDED__ #define __BOOST_CONFIG_PLATFORM_LIST_HPP__INCLUDED__ #define BOOST_AIX_PLATFORM_CONFIG 100 #define BOOST_AMIGAOS_PLATFORM_CONFIG 101 /// and so on ... #define BOOST_WIN32_PLATFORM_CONFIG 111 #define BOOST_UNKNOWN_PLATFORM_CONFIG 999 #endif Then in win32.hpp, the following definition is provided : #define BOOST_ACTIVE_PLATFORM_CONFIG BOOST_WIN32_PLATFORM_CONFIG In user code, it can be checked like this : #if (BOOST_ACTIVE_PLATFORM_CONFIG == BOOST_WIN32_PLATFORM_CONFIG) // Some Win32 code #else // some other code for non-win32 #endif Does this sound useful or am I overlooking some already existing boost system that may already do this ?

1 0

[serialization] disabling msvc warnings
by Jürgen Hunold 08 Oct '08

08 Oct '08

Hi ! Please find a patch attached which disables MS "secure" STL and C-Runtime warnings when build Boost.Serialization with msvc-8.0 and above. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

1 0

[serialization] extended_type_info_typeid doesn't work with objects with non public destructors
by Rodolfo Lima 07 Oct '08

07 Oct '08

Hi, it seems that in boost::serialization-1.36 the extended_type_info_typeid and extended_type_info_no_rtti doesn't use boost::serialization::access to delete the object, hence there are compile failures when it's used with an object whose destructor isn't public. Is there any chances that this will be fixed in boost-1.37? Regards, Rodolfo Lima

2 2

[property_tree] Conversion constructor missing?
by Boris 07 Oct '08

07 Oct '08

Imagine you have this XML structure (copied from the documentation and shortened): <debug> <modules> <module>Finance</module> <module>Admin</module> <module>HR</module> </modules> </debug> Now imagine you have this function which you want to call three times to pass the <module>...</module> nodes to: void foo(boost::property_tree::ptree pt); You can use get_child("debug.modules") to retrieve a property tree containing all module nodes. However if you iterate over the property tree the iterator refers to std::pair<const key_type, basic_ptree<Tr>> - and there is no simple way to convert this pair to a new property tree. You must create an empty property tree followed by a call to push_back() to insert the pair. Either there is a conversion constructor missing or I miss something and there is a simpler way of what I'm trying to do? Boris

1 0

type_with_alignment.hpp / alignment_of.hpp too heavy
by Emil Dotchevski 07 Oct '08

07 Oct '08

I need to allocate an object of type T, but I also need to bundle it in a single memory allocation with an object of class U. Something like "new std::pair<T,U>" would work, except that U is a rather heavy type and I want to pimpl it away into a cpp. This means that the cpp needs to deal with the alignment of T and U when allocating the memory. For that purpose, I could use type_traits/type_with_alignment.hpp in my header, but when I looked at it, I was blown away by how much crap it includes (remember, I want my header to be very very light.) Then I thought that I could probably build my system by just using type_traits/alignment_of.hpp. It sure would be very light, right? Wrong, it also includes mpl and whatnot. I hope someone shares my frustration. Shouldn't at least alignment_of.hpp be much, much lighter? I'd think that all it should contain is whatever compiler-specific hacks are needed and that's it. What is the justification for including stuff like <boost/mpl/aux_/lambda_support.hpp> in alignment_of.hpp? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

8 9

status on Coroutine library?
by Tim Michals 07 Oct '08

07 Oct '08

What is the status of the coroutine library? _________________________________________________________________ Get more out of the Web. Learn 10 hidden secrets of Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!5…

1 0

[config] Any reason not to enable long long support in for Sun's compiler?
by John Maddock 07 Oct '08

07 Oct '08

Title says it all really, any reason why I should define BOOST_HAS_LONG_LONG for sun's compiler? Seems to all work OK... John.

2 2

[lambda] Serialising Lmanda functions
by Robert Jones 07 Oct '08

07 Oct '08

Is there a 'standard' solution to this problem? #include <list> #include <iostream> #include "boost/lambda/lambda.hpp" typedef std::list<unsigned> List; std::ostream & operator<<( std::ostream & s, const List & ); int main( ) { using namespace boost::lambda; List my_list; ( std::cout << _1 << "\n" )( my_list ); } The compiler cannot find a match for operator<<() because the operator and the type are defined in different namespaces, but it's really a nuisance! - Rob.

2 1

Difficulties checking into release ready branch
by Robert Ramey 07 Oct '08

07 Oct '08

In following instructions to commit to the releae ready branch I get the following message: Modified: BoostRelease\boost\archive\impl\basic_binary_iprimitive.ipp Error: Commit failed (details follow): Error: Your file or directory 'impl\basic_binary_iprimitive.ipp' is probably out-of-date Error: The version resource does not correspond to the resource within the transaction. Either the requested version resource is out of date (needs to be updated), or the requested version resource is newer than the transaction root (restart the commit). This was after a bunch of files got commit successfully. In the past when problems like this occured (as they often seem to), repeating the operation (with maybe an intervening clean up) seemed to plow through the situation. But this time it seems something is permantly stuck. Any help would be appreciated. Robert Ramey

2 2