- Boost - lists.boost.org

Boost regression notification (2005-08-03)
by Douglas Gregor 03 Aug '05

03 Aug '05

<html> <head> <meta http-equiv="refresh" content="1; url=issues-email.txt"> </head> <body> <p>Update in progress (building archive index, done in approximately 4 seconds), please wait...</p> </body> </html>

2 1

[mpl] as_sequence< X< Y > > instantiates typedefs in X< Y >
by Andreas Huber 03 Aug '05

03 Aug '05

Hi there I'm trying to address a point raised by Jonathan Turkanis during the formal review of the statechart library. Basically, the problem boils down to the following: #include <boost/mpl/list.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/as_sequence.hpp> namespace mpl = boost::mpl; // InnerInitial is either an mpl sequence of types or a single type template< class InnerInitial > struct state { // stateArray_ must have a length equal to the number of types // in InnerInitial int stateArray_[ mpl::size< typename mpl::as_sequence< InnerInitial >::type >::type::value ]; }; // A is defined later, possibly in a different translation unit struct A; template< class X > struct B { typedef typename X::reactions reactions; }; int main() { // fine: instantiation with an incomplete type state< A > a; // fine: instantiation with an mpl sequence containing B< A > state< mpl::list< B< A > > > b; // error: mpl::as_sequence triggers the instantiation of B's member // typedef, which tries to access the member typedef of A. A compile- // time error results because A is still incomplete at this point. state< B< A > > c; // *** here *** return 0; } MSVC7.1 and GCC3.4 agree that the last state template instantiation is illegal (use of undefined type A). I'm wondering whether there is any way to make this legal (different as_sequence implementation, implement the state template differently, etc.)? Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

2 14

[iostreams-1.33.0-RC1] documentation error?
by Russell Hind 03 Aug '05

03 Aug '05

2.1.1 states "Here io::stream<my_device> is a derived class of std::basic_streambuf, and io::stream<my_device> is a derived class of std::basic_istream, std::basic_ostream or std::basic_iostream depending on the mode of my_device, i.e., depending on which of the fundamental i/o operations read, write and seek it supports." Shouldn't the first part be "Here io::stream_buffer<my_device>"? Cheers Russell

2 1

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