- Boost - lists.boost.org

Re: Re: multi_index_container
by Wusel 03 Mar '05

03 Mar '05

Hi Joaquín M López Muñoz, thank you for your quick answer! I appreciate that multi_index_container exist and I can use it. In my opinion this library is very useful and facilitate many programs. >> 44 //version B: DOES compile >> 45 typedef index<employee_set,id >::type employee_set_by_id; >> 46 typedef index<employee_set,age>::type employee_set_by_age; > > OK, fine. > >> 48 //remove the name index (lines 31, 32) for following versions >> 49 >> 50 //version C: DOES compile >> 51 typedef index<employee_set,id >::type employee_set_by_id;; > > OK, too. > >> 52 >> 53 //version D: does NOT compile >> 54 //causes >> ...\include\boost-1_32\boost\mpl\vector\aux_\preprocessed\no_ctps\vector10.hpp(398) >> : >> 55 // error C2039: 'item3' : is not a member of >> 'boost::mpl::vector2<T0,T1>' >> 56 typedef index<employee_set,age>::type employee_set_by_age; > > !! Here I'm missing somethig... Isn't version D exactly the same > as version B, which does work? Exact this I wanted point out. Version D differs from version B in removing two lines 31, 32 only (i.e. the name index). Version C is nearly the same, too. Nevertheless there is a difference when compiling. best regards Volker Vieth

2 3

[mpl]RFE: unpack_apply
by Larry Evans 02 Mar '05

02 Mar '05

Would it be possible to add: template<typename Application> struct unpack_apply { ... }; such that: is_same < unpack_apply<f<a0,a2,...,an> >::type , vector<a0,a2,...,an> > to mpl? Maybe a better name would be get_args, but since it's so closely related to unpack_args, I thought maybe unpack_apply could be considered OK.

1 1

review of FSM nears to the end - any more reviews?
by Pavel Vozenilek 02 Mar '05

02 Mar '05

Review period of FSM library (http://boost-sandbox.sf.net/fsm.zip) nears to its end in few days. Does anyone need to extend review period? Review can be surely posted even after end of official period - I'll reserve some time for such possibility. /Pavel

8 11

Re: [boost] Re: Boost.Hash + Boost.Unordered reviews
by JOAQUIN LOPEZ MU?Z 02 Mar '05

02 Mar '05

----- Mensaje original ----- De: Daniel James <daniel(a)calamity.org.uk> Fecha: Miércoles, Marzo 2, 2005 11:49 pm Asunto: [boost] Re: Boost.Hash + Boost.Unordered reviews > Joaquín Mª López Muñoz wrote: > > This issue seems to have cooled down. Has there been > > some off-list progress, should we agree what to do here? > > No, I've been taking a small break from it. There seem to be no > real > objections to the original plan (fast-tracking Boost.Hash and > placing > Boost.Unordered in the queue), so it looks like that's the way to go. > I'm happy to know you're still on this. Looking fwd to participating in both reviews. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

RE: [boost] Iostreams Compile Issue with boost/algorithm/string.hpp was[RE: Compile problem using IoStreams from CVS inside boostv1.32 (VC71)]
by Brian Braatz 02 Mar '05

02 Mar '05

Just for giggles, I pointed my unit test code to the boost I got from CVS. Interestingly enough, it compiled with the #include <boost/algorithm/string.hpp> (but it complained about the unit test code- I am guessing there is a broken form in cvs? Or maybe I don't have something setup- when I commented out my test suite definitions- I WAS able to compile the file though) > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Brian Braatz > Sent: Wednesday, March 02, 2005 2:03 PM > To: boost(a)lists.boost.org > Subject: [boost] Iostreams Compile Issue with boost/algorithm/string.hpp > was[RE: Compile problem using IoStreams from CVS inside boostv1.32 (VC71)] > > I narrowed this down a bit more- > > In my code which uses filtered_stream if I have the following headers: > > #include <boost/iostreams/concepts.hpp> > #include <boost/iostreams/operations.hpp> > #include <boost/iostreams/filtering_stream.hpp> > #include <boost/iostreams/device/file.hpp> > // #include <boost/algorithm/string.hpp> > > It compiles- but when I uncomment the #include > <boost/algorithm/string.hpp> I get the error below > > > > -----Original Message----- > > From: Brian Braatz > > Sent: Wednesday, March 02, 2005 1:34 PM > > To: 'boost(a)lists.boost.org' > > Subject: Compile problem using IoStreams from CVS inside boost v1.32 > > (VC71) > > > > I am using VC7.1 (and will also be using VC70 for this code) > > > > What I did- > > > > Executed the following from a cmd prompt: > > cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login > > cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost > checkout > > boost > > cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout > > > > went into boost\iostreams and boost\libs\iostreams- copied both into > temp > > area- > > > > Deleted the CVS folders > > > > Copied the files into the boost 1.32 dir in my company's internal CVS > > server (we have the boost files under revision control to control > which > > version of which file we are using to build) > > > > Initially I had to change the files to from namespace io to iostreams. > Got > > through those compile errors. And Now I have this one: > > > > > > boost\algorithm\string\iterator_range.hpp(288) : error C2874: using- > > declaration causes a multiple declaration of > > 'boost::algorithm::iterator_range' > > > > \boost\algorithm\string\iterator_range.hpp(204) : see declaration of > > 'boost::algorithm::iterator_range' > > > > I am digging into this but thought I would throw this out to see if > any > > one is aware of the issue- > > > > These errors point to the end of iterator_range.hpp (pointing at the > using > > clause) > > > > Here is a snippet from that file: > > > > template< typename SeqT, typename IteratorT, typename FuncT > > > inline SeqT transform_iterator_range( const > > iterator_range<IteratorT>& Range, FuncT Func ) > > { > > SeqT Seq; > > std::transform( Range.begin(), Range.end(), > > std::back_inserter(Seq), Func ); > > return Seq; > > } > > > > } // namespace algorithm > > > > // pull names to the namespace boost > > using algorithm::iterator_range; > > using algorithm::make_iterator_range; > > using algorithm::copy_iterator_range; > > using algorithm::transform_iterator_range; > > > > } // namespace boost > > > > > > > > > > > > > > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Boost.Hash + Boost.Unordered reviews
by Joaquín Mª López Muñoz 02 Mar '05

02 Mar '05

This issue seems to have cooled down. Has there been some off-list progress, should we agree what to do here? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 2

[Boost-bugs] [ boost-Bugs-1155439 ] Correction to configuration for Sun C++
by SourceForge.net 02 Mar '05

02 Mar '05

Bugs item #1155439, was opened at 2005-03-02 14:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1155439&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Correction to configuration for Sun C++ Initial Comment: The BOOST configuration files have settings for early Sun compilers that are not correct for the current compilers. (The early compilers can't compile fair-sized chunks of BOOST in any case.) We intend full support of BOOST in Sun Studio 10 (C++ 5.7) and later. I've attached diffs for the config files. There's a possible hole in these updates, however. The BOOST configuration files currently claim nothing since C++ 5.3 was tested. I am making no claims about C++ 5.4 through 5.6, but only for 5.7 and later. Steve Clamage, stephen.clamage(a)sun.com Sun C++ Project Lead ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1155439&group_… ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Iostreams Compile Issue with boost/algorithm/string.hpp was [RE: Compile problem using IoStreams from CVS inside boost v1.32 (VC71)]
by Brian Braatz 02 Mar '05

02 Mar '05

I narrowed this down a bit more- In my code which uses filtered_stream if I have the following headers: #include <boost/iostreams/concepts.hpp> #include <boost/iostreams/operations.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/device/file.hpp> // #include <boost/algorithm/string.hpp> It compiles- but when I uncomment the #include <boost/algorithm/string.hpp> I get the error below > -----Original Message----- > From: Brian Braatz > Sent: Wednesday, March 02, 2005 1:34 PM > To: 'boost(a)lists.boost.org' > Subject: Compile problem using IoStreams from CVS inside boost v1.32 > (VC71) > > I am using VC7.1 (and will also be using VC70 for this code) > > What I did- > > Executed the following from a cmd prompt: > cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login > cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost checkout > boost > cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout > > went into boost\iostreams and boost\libs\iostreams- copied both into temp > area- > > Deleted the CVS folders > > Copied the files into the boost 1.32 dir in my company's internal CVS > server (we have the boost files under revision control to control which > version of which file we are using to build) > > Initially I had to change the files to from namespace io to iostreams. Got > through those compile errors. And Now I have this one: > > > boost\algorithm\string\iterator_range.hpp(288) : error C2874: using- > declaration causes a multiple declaration of > 'boost::algorithm::iterator_range' > > \boost\algorithm\string\iterator_range.hpp(204) : see declaration of > 'boost::algorithm::iterator_range' > > I am digging into this but thought I would throw this out to see if any > one is aware of the issue- > > These errors point to the end of iterator_range.hpp (pointing at the using > clause) > > Here is a snippet from that file: > > template< typename SeqT, typename IteratorT, typename FuncT > > inline SeqT transform_iterator_range( const > iterator_range<IteratorT>& Range, FuncT Func ) > { > SeqT Seq; > std::transform( Range.begin(), Range.end(), > std::back_inserter(Seq), Func ); > return Seq; > } > > } // namespace algorithm > > // pull names to the namespace boost > using algorithm::iterator_range; > using algorithm::make_iterator_range; > using algorithm::copy_iterator_range; > using algorithm::transform_iterator_range; > > } // namespace boost > > > > > >

1 0

Compile problem using IoStreams from CVS inside boost v1.32 (VC71)
by Brian Braatz 02 Mar '05

02 Mar '05

I am using VC7.1 (and will also be using VC70 for this code) What I did- Executed the following from a cmd prompt: cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost login cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost checkout boost cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/boost logout went into boost\iostreams and boost\libs\iostreams- copied both into temp area- Deleted the CVS folders Copied the files into the boost 1.32 dir in my company's internal CVS server (we have the boost files under revision control to control which version of which file we are using to build) Initially I had to change the files to from namespace io to iostreams. Got through those compile errors. And Now I have this one: boost\algorithm\string\iterator_range.hpp(288) : error C2874: using-declaration causes a multiple declaration of 'boost::algorithm::iterator_range' \boost\algorithm\string\iterator_range.hpp(204) : see declaration of 'boost::algorithm::iterator_range' I am digging into this but thought I would throw this out to see if any one is aware of the issue- These errors point to the end of iterator_range.hpp (pointing at the using clause) Here is a snippet from that file: template< typename SeqT, typename IteratorT, typename FuncT > inline SeqT transform_iterator_range( const iterator_range<IteratorT>& Range, FuncT Func ) { SeqT Seq; std::transform( Range.begin(), Range.end(), std::back_inserter(Seq), Func ); return Seq; } } // namespace algorithm // pull names to the namespace boost using algorithm::iterator_range; using algorithm::make_iterator_range; using algorithm::copy_iterator_range; using algorithm::transform_iterator_range; } // namespace boost

2 1

Resigning from Boost.Profiler
by christopher diggins 02 Mar '05

02 Mar '05

I am going to have to stop development of Boost.Profiler. IMO there is still a huge gap between where it is and where it would have to go to be both robust and simple enough to be appropriate for Boost. Honestly I don't see it happening without a more robust and portable high_resolution_timer, which requires far more time and energy than I am willing to commit. Where is the best place to upload my current snapshot, so that others can take over if they want? Christopher Diggins Object Oriented Template Library (OOTL) http://www.ootl.org

2 2