- Boost - lists.boost.org

Re: [boost] [1.33.0] Checklist for RC2
by JOAQUIN LOPEZ MU?Z 03 Aug '05

03 Aug '05

----- Mensaje original ----- De: Douglas Gregor <doug.gregor(a)gmail.com> Fecha: Miércoles, Agosto 3, 2005 4:05 pm Asunto: [boost] [1.33.0] Checklist for RC2 > These are the issues we need to resolve before I can roll RC2, > which is > likely to become the final release: > > - Jonathan Turkanis needs a picture > - Fix remaining broken links > - iostreams: Document how to get bzip2/gzip iostreams to work > in > more/getting_started.html > - regex: Decide what to do about std::equal bug in VC++ 8.0 > beta (it > *is* a beta, and it *is* a compiler bug) > Hi, I posted about the following several times, but the message went unnoticed. Maybe it is a misunderstanding from my part, but the "getting started" page lists Boost.Serialization as not autolinkable and not dyanmically linkable. I think this is no longer true in Boost 1.33 (but I might be wrong.) I would have taken care of the problem myself, but currently I can't access the CVS, as I'm on vacation. I'd be greateful if someone can correct this bit. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

Re: [boost] [1.33.0] User reports go live / feedback request
by Matt Doyle 03 Aug '05

03 Aug '05

> The draft version of user-centric regression reports is now > available at > http://engineering.meta-comm.com/boost-regression/CVS-RC_1_33_ > 0/user/summary_release.html > (http://tinyurl.com/bamym) If you'd like to comment on > usability/presentation of these before they go public with the > release, now it's time :). I liked the idea of having hyper-links to the details but I think the older 1.32 version was more readable. The first thing I did when I looked at it was print it out for reference. Without color the table is of no use. If you put text in each cell as before (OK, FAIL, ect...), in addition to the color, then it can be used in B/W or color. Scanned by Fortigate {X3BTB534}

3 3

mailing list delays
by David Abrahams 03 Aug '05

03 Aug '05

The problem should be fixed now. Let's hear it for the OSL guys! From: Rob Henderson <robh(a)cs.indiana.edu> Date: July 26, 2005 8:50:35 AM MDT To: Jeff Squyres <jsquyres(a)osl.iu.edu> Cc: OSL Sysadmin <osl-sysadmin(a)osl.iu.edu>, Bruce Shei <shei(a)cs.indiana.edu> Subject: Re: boost mailing lists I wanted to let you know that I think I've figured out what is going on with the recent slowness with email to the mailman lists that was reported. The email address xxx@xxxx that is on the boost list appears to have some kind of anti-spam tarpit set up that is catching milliways. Email to this address is handled by mail.tapeinternational.no and it you telnet to port 25 on this host from milliways you will see that it is (I assume) deliberately slow. During the initial '220' response, it is sending characters at a rate of about one character per 30 seconds. This keeps the connection from milliways moving along at a rate sufficient to keep it from timing out but slow enough that delivery is taking hours. If you telnet to port 25 from any other CS/OSL host the response is very fast so it is clearly set up to catch milliways. I don't know why they have done this, but I'd say the options are to either remove that user from the list or contact them and try to get them to stop this. Please let me know if there is anything else I can do related to this issue. We have disabled delivery to the offending email address and notified its owner. -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 3

[1.33.0][iostreams][serialization]
by Jeff Flinn 03 Aug '05

03 Aug '05

I've spent the last several hours trying to update my project with 1.33.0.RC. The only changes were naming issues with iostreams, and the getting rid of the lovely :) asserts on serialization inclusions previous to archive inclusions. Also an issue with operator << and const_cast-ing appears below, and switching to the standard BOOST_SHARED_POINTER_EXPORT_GUID macro which now appears to handle pointers in namespaces properly. All compiles and links succesfully under VC7.1. Rudimentary xml serialization seems to save/load succesfully. I am having an problems when using iostreams/serialization together to support copy/paste/drag/drop under Windows MFC. Which all worked flawlessly using 1.32.0 along with pre-release iostreams. I'd appreciate it if anyone sees anything blatantly wrong with the code below. CSharedFileSink::write is not being called at all. This leads and assert in MFC's CSharedFile::Detach because the file has never been written to. The member CSafeDataSource::GlobalArchiveHdl instantiates a CSharedFileOStream and attempts to serialize it's mVal data member to a binary archive. Thanks in advance, Jeff namespace adi { namespace mfc { namespace clipboard { struct CSharedFileSink : public boost::iostreams::sink { CSharedFile& mSharedFile; CSharedFileSink( CSharedFile& aSharedFile ) : boost::iostreams::sink() , mSharedFile(aSharedFile) {} std::streamsize write( const char* s, std::streamsize n ) { mSharedFile.Write( s, n ); return n; } }; class CSharedFileOStream : private boost::base_from_member<CSharedFile> , public boost::iostreams::stream<CSharedFileSink> { typedef boost:: base_from_member<CSharedFile > tSharedFile; typedef boost::iostreams::stream<CSharedFileSink> tBase; public: CSharedFileOStream() : tSharedFile( GMEM_MOVEABLE|GMEM_DDESHARE|GMEM_ZEROINIT ) , tBase( CSharedFileSink( tSharedFile::member ) ) {} HGLOBAL Detach(){ return tSharedFile::member.Detach(); } }; template< class T > class CSafeDataSource : public COleDataSource { typedef T value_type; value_type mVal; HGLOBAL GlobalArchiveHdl() { CSharedFileOStream lOut; boost::archive::binary_oarchive oa( lOut ); // oa & mVal; // same result as below oa << const_cast<const value_type&>(mVal); //BOOST_1_33_0 return lOut.Detach(); } CSafeDataSource( const T& aVal ) : COleDataSource(),mVal(aVal){ DelayRenderData( NativeFormat() ); } friend void ToClipBoard<T>( const T& aVal ); friend void Drag<T>( const T& aVal , tDragImagePtr aDragImagePtr , DWORD aDropEffect ); public: static CLIPFORMAT NativeFormat(){ return RegisteredClipboardFormat<value_type>(); } virtual BOOL OnRenderGlobalData( LPFORMATETC lpFormatEtc, HGLOBAL* phGlobal ) { if( lpFormatEtc->cfFormat == NativeFormat() ) { return (*phGlobal = GlobalArchiveHdl())? TRUE : FALSE; } return FALSE; } }; } } }

2 6

Boost Build V2 docs removed from cvs?
by John Maddock 03 Aug '05

03 Aug '05

All the links to the docs bbv2 docs from tools/build/v2/index.html seem to go nowhere. Has someone removed the docs from cvs? Thanks, John.

1 0

[1.33.0] Final release schedule
by Douglas Gregor 03 Aug '05

03 Aug '05

The release is starting to shape up, and here is our final release schedule. We'll stick to it unless something goes horribly wrong. Code freeze - 11pm EST on Sunday, July 24 Total freeze (including documentation) - 11pm EST on Wednesday, July 27 Final release - Monday, August 1st Doug Gregor 1.33.0 Release Manager

12 30

[date_time] and BCB
by Richard Jennings 03 Aug '05

03 Aug '05

The CVS head revision of date_time fails to compile with Borland C++ 5.6.4. This is because the run time libraries lack the re-entrant functions such as localtime_r. I added Borland to the list of compilers that do not support this in date_time/compiler_config.hpp and then the library compiles fine. Richard

3 5

iterators::function_output_iterator is missing in boost_1_32_0
by Oleg Abrosimov 03 Aug '05

03 Aug '05

Hello boosters! I've just found that function_output_iterator, mentioned in boost_1_32_0/libs/iterator/doc/function_output_iterator.html is missing in the boost or boost/iterator directories both in my own copy and in sf.net CVS. Neither me nor my compiler could found it. Was it deprecated? or removed accidentally? Best, Oleg Abrosimov

2 2

singleton design plan
by Jason Hise 03 Aug '05

03 Aug '05

This message is an in depth description of my current design plan for a new singleton library, which I hope to complete and schedule for review by boost in the coming year. I would appreciate any comments, questions, or suggestions regarding this plan before I begin work on the code. Specifically, I would like to know if there are any important issues that this design fails to address, or difficulties with the interface that would turn away potential users. (My old singleton library, which was not accepted by boost, is available at http://tinyurl.com/6qvrd. It was rejected primarily because it failed to adequately address concerns related to multi threading and dlls.) Thus far, my high level design plan looks like this: The creator_policy defines fundamental pointer, const_pointer, and reference types. These hold references to a creator policy instance which maintains the singleton internally, so that the pointer types can always see and access the state of the single instance. This way, pointers to the singleton instance are not invalidated when the state of the singleton changes. The creator_policy defines create, replace, and destroy methods, as well as methods to generate instances of the various pointer types. Create only creates the instance if it does not already exist, destroy only destroys the instance if it does exist, and replace makes sure any existing instance is destroyed before attempting creation. Thus far, I hope to support the following creators: -------------------------------------------------------------------------------- in_place_creator creates/destroys inside an aligned_storage POD interface: create ( [ctor params] ); replace ( [ctor params] ); destroy ( ); pros: no memory allocation/deallocation ever required constructor params can be easily specified cons: automatic creation, when it occurs, always uses the default constructor singleton cannot be created as a derived type useful for simple, user defined singleton classes -------------------------------------------------------------------------------- source_sink_creator owns fixed source and sink functors, specified with template parameters interface: create ( ); replace ( ); destroy ( ); pros: source can return a derived type automatic creation uses source rather than default construction cons: source and sink cannot be set or changed at runtime constructor arguments cannot be specified by calling code useful for singleton types provided by untouchable code, which may require calling special functions to get pointers to instances -------------------------------------------------------------------------------- dynamic_source_sink_creator owns dynamic source and sink functors interface: create ( [source[, sink]] ); replace ( [source[, sink]] ); destroy ( [source[, sink]] ); pros: source can return a derived type automatic creation uses source rather than default construction source and sink can optionally be changed at run time source and sink can change functor types when they are set (example: from function pointer to lambda expression) cons: specifying constructor parameters to pass is non-trivial dynamic memory allocation and virtual functions must be used to store the functors in order to allow for different functor types at runtime, thus creation is more expensive and can potentially fail useful for a singleton which needs to take the forms of unspecified derived types and is frequently destroyed and created via some type of factory -------------------------------------------------------------------------------- The lifetime_policy owns and wraps the creator policy, and provides pointer and reference types which wrap those belonging to the creator. It also provides functions to generate instances of the various pointer types, and provides a function to access the creator_policy instance. The unmanaged lifetime simply typedefs the underlying pointer and reference types, and thus results in no overhead. The longevity_lifetime and lifo_lifetime behave similarly, but handle scheduling of automated destruction when any of the pointer generation methods are called. The dependency_lifetime will wrap the internal pointer types to perform reference counting (the reference count itself will be stored in the lifetime_policy instance). The timeout_lifetime will manage a separate thread that releases the instance when it finishes counting down. It will also wrap the internal pointer types to reset the timer when a pointer is dereferenced, and reset and lock the timer while any references exist. The threading_policy owns and serializes access to the lifetime_policy. It also has a function to get access to the lifetime_policy instance, and provides pointer, const_pointer, and reference types which wrap and forward to the lifetime's corresponding types. For the single_threaded policy, these pointer types are simply typedefs of the lifetime's pointer types, resulting in no overhead, and the function through which the lifetime_policy instance is accessed just returns a raw pointer to it. For the multi_threaded policy, pointer types perform locking before forwarding to lifetime pointer types, and the reference type acts as a lock throughout it's existence. The mutex is stored inside the threading_policy instance. The function which returns a pointer to the lifetime_policy instance returns a smart pointer which serializes access. A storage_policy determines how instances of the threading_policy are stored (and because these instances contain instances of the other policies, this indirectly controls how all of the policy instances are stored). static_storage stores policy instances directly as global variables, which is fine for singletons that are not required to have a specific lifetime with regard to other singletons. These global variables will be set up in such a way that it will be guaranteed that any automatic destruction takes place before the policy bundle is destroyed. group_storage allows multiple singletons to have their policies stored in a master group. No policies in this group are destroyed until all automated destruction that will be performed by any members of the group has completed. This way, if destructors of some of the singletons in this group trigger re-creation of other singletons in the same group, the policies needed to recreate the singletons are guaranteed to still exist. dll_storage requires linking with singleton.dll, and stores instances in a special exported manager singleton to ensure unique singleton instances across dll boundaries. All policy instances of this type are guaranteed to be destroyed only after all automated destruction has taken place. A singleton class exists, which takes a singleton type and a name tag as template parameters. The name will have a default type called 'unnamed'. This name parameter enables using multiple singleton instances of the same type. Policies are traits of the name specified, so using the default name 'unnamed' results in using the default policies. Policies can be specified by declaring a name as an undefined struct, and then specializing the desired policy traits for that name. The singleton class contains three pointer types, which wrap those of the threading policy. These are strong_pointer, lazy_pointer, and weak_pointer. strong_pointer attempts automatic creation of the singleton instance if it does not exist when the pointer is first created, and also attempts automatic creation if needed any time it is dereferenced. lazy_pointer only attempts automatic creation when dereferenced, and weak_pointer will never create the instance automatically. For the lifo_lifetime, a strong_pointer can be used to specify a dependency of some singleton B on some singleton A by having B own a strong_pointer to A. This will ensure that A is created before B and destroyed after B. Const versions of these three pointer types will also exist. Creation, destruction, and non-const member functions will not be allowed to be called through these const pointer types. A single reference type will exist which will be the result of dereferencing any pointer type via the unary * operator. const_pointers return const qualified references. Pointers only perform temporary locking (if the threading policy supports locking) when a member function is called via the -> operator or when a create or destroy operation is invoked. References lock the singleton throughout their entire lifetime, and thus can be used to make a series of operations on the singleton instance atomic. A reference provides an implicit conversion to a raw reference of the singleton's type (which comes back const if the reference is const). Create and destroy can only be called on non-const references. Typical code will access a singleton instance by creating one of the above pointer types and calling member functions through it via the -> operator. Ex: singleton < MyType, SomeName >::lazy_pointer ptr; ptr->DoSomething ( ); -------------------------------------------------------------------------------- I plan to sneak an improved version of the null developed by Scott Meyers in with this code in a header called boost/null.hpp, and use it in the singleton's implementation. It will be defined as follows: namespace boost { const class { private: void operator & ( ) const; public: #ifndef BOOST_NO_MEMBER_TEMPLATES // provide conversion to any pointer type template < typename Class, typename Type > operator Type Class::* ( ) const { return 0; } template < typename Type > operator Type * ( ) const { return 0; } #else //provide conversion to int if member templates are not supported operator int ( ) const { return 0; } #endif//BOOST_NO_MEMBER_TEMPLATES } null; } #undef NULL #define NULL (::boost::null) -------------------------------------------------------------------------------- Any and all comments or suggestions on this plan are welcomed. Potential problems are much easier to address at design time than after the code is written. -Jason

8 20

[signals] Signals 1.33 dylib crashes when used with Xcode
by Chiedo Acholonu 02 Aug '05

02 Aug '05

I'm using boost 1.33 and recently tried to build the signals dll using the darwin toolset. I then created a simple Xcode project called TestSignals to test it was working correctly. The project only contains the maximum.cpp example file (/boost-root/libs/signals/examples/maximum.cpp) linked against the signals dynamic library. The project builds just fine, but when I run the app, Xcode crashes with: "TestSignals has exited due to signal 10 (SIGBUS)." Here is a piece of the crash log (I can send the full log on request): --- Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 maximum.ob 0x0040c844 std::less<int>::operator()(int const&, int const&) const + 48 (stl_function.h:227) --- I tried using different example files, and they all crash. The library is built multithreaded and I do define BOOST_SIGNALS_DYN_LINK in my project. I'm running on Tiger 10.4.2 using Xcode 2.1. Has anyone tried this or run into a similar problem? Thanks, Chiedo

1 0