- Boost - lists.boost.org

[flyweight][review] Flyweight accepted
by Ion Gaztañaga 06 Feb '08

06 Feb '08

Hi to all, The Flyweight library submitted by Joaquín M. López Muñoz has been *accepted* into Boost. Thanks to all reviewers and all who contributed to the library before the review. We've received 10 reviews (Alberto Ganesh Barbati, David Sankel, John Reid, John Torjo, Kevin Scopp, Marcus Lindblom, Markus Werle, Matias Capeletto, Neil Hunt, Tim Blechmann), and all except Alberto's one were positive. Please, if I've missed a review, let me know. Joaquín agreed to address Alberto's comments (either with keyed_flyweight or by another method) and I like to encourage Joaquín and Alberto and the rest of the Boost community to improve the flyweight library to optimize and adapt it for situations like Alberto has described. I'm pretty sure that we'll reach an agreement. I'll have some time during the weekend to read all the reviews and write an small summary of requested changes, ideas, complaints, etc... to summarize the review process. Congratulations to Joaquín and thanks to all those who have participated in the review. Ion Gaztañaga - Review Manager -

6 5

SVN, forgotten password
by Tobias Schwinger 06 Feb '08

06 Feb '08

Hi, it seems I've forgotten my SVN/Trac password. Can someone help me, please? Regards, Tobias

2 2

[xpressive] are there any default ways to match built-in types?
by Thorsten Ottosen 06 Feb '08

06 Feb '08

Hi Eric, Spirit has a lot of default parsers like real_p, int_p, str_p etc. Are there any plans to add something similar to xpressive? best regards -Thorsten

2 1

Re: [boost] [fusion]bug: as_list on cons list is identity
by dan marsden 06 Feb '08

06 Feb '08

Larry Evans <cppljevans(a)suddenlink.net> wrote: <snip exampling showing make list returns a cons cell list, rather than fusion::list> >IOW, instead of: > > boost::fusion::vector<...> > >there should be: > > boost::fusion::list<...> > >as the 1st line of the above result type for as_list<source_type>::type. Does this lead to a problem in your code? The sequence of cons cells is a list (fusion::list can be seen as just a convenient way of building a long cons cell sequence). The cons sequence will behave exactly as a list. Maybe these functions should be called as_random_access_sequence, as_bidirectional_sequence etc? Possibly that would be less misleading? Cheers Dan ___________________________________________________________ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/

2 2

Does Boost format() has a wstring equivalent?
by Jim W 06 Feb '08

06 Feb '08

I hope I'm not asking something obvious, but I was wondering if Boost format() has a wstring equivalent? Thanks, Jim

2 1

Re: [boost] Review of Logging library begins today February 4th
by Scott Woods 06 Feb '08

06 Feb '08

Sorry, bad keystroke near the end of my previous post. Will take me a while to reply fully. ----- Original Message ----- From: "Scott Woods" <scott.suzuki(a)gmail.com> To: <boost(a)lists.boost.org> Sent: Wednesday, February 06, 2008 1:03 PM Subject: Re: [boost] Review of Logging library begins today February 4th >>> >>> To raise the bar you might include requirements such as gleaning maximum >>> information from the point of logging, with minimum developer fuss and >>> delivering that information to a storage+viewing mechanism for >>> convenient >>> post-processing and analysis, e.g.; >>> >>> >> I would say I provided that. > > I suppose you can. > <snip>

1 0

[fusion]bug: as_list on cons list is identity
by Larry Evans 05 Feb '08

05 Feb '08

With source_type: boost::fusion::cons < type_id < 0u > , boost::fusion::cons < type_id < 1u > , boost::fusion::cons < type_id < 2u > , boost::fusion::nil > > > the result type of fusion::result_of::as_list<source_type>::type is: boost::fusion::cons < type_id < 0u > , boost::fusion::cons < type_id < 1u > , boost::fusion::cons < type_id < 2u > , boost::fusion::nil > > > However, I expected something more like was happens with: fusion::result_of::as_vector<source_type>::type which gives the result type: boost::fusion::vector < type_id < 0u > , type_id < 1u > , type_id < 2u > , boost::fusion::void_ , boost::fusion::void_ , boost::fusion::void_ , boost::fusion::void_ , boost::fusion::void_ , boost::fusion::void_ , boost::fusion::void_ > IOW, instead of: boost::fusion::vector<...> there should be: boost::fusion::list<...> as the 1st line of the above result type for as_list<source_type>::type.

1 0

[signals] warning C4512 (VS9)
by Robert Dailey 05 Feb '08

05 Feb '08

In Visual Studio 9 at warning level 4, I get the following warning when I compile the Boost.Signals library via the header <boost/signals.hpp>: 1>c:\it\personal\rocket_test\sdk\boost\boost\signals\trackable.hpp(163) : warning C4512: 'boost::signals::detail::bound_objects_visitor' : assignment operator could not be generated 1> c:\it\personal\rocket_test\sdk\boost\boost\signals\trackable.hpp(66) : see declaration of 'boost::signals::detail::bound_objects_visitor'

1 0

Re: [boost] Review of Logging library begins today February 4th: dlls
by Dirk Griffioen 05 Feb '08

05 Feb '08

Hi John, Just a small question - in 2005 we used logging v1, but we couldnt get it to play along with dlls: logging was defined in one dll (called 'log.dll' - if I remember correctly) , and various parts of the system in other dlls, but we could use log.dll reliably from the other dlls and had to revert to have a log inside each dll ... has this been addressed? (it might just be that this has to do with windows' way of memory in dll's) Regards, - Dirk -- CodeShop

2 2

[xpressive] how to see how much of one's input that matched
by Thorsten Ottosen 05 Feb '08

05 Feb '08

Hi Eric, I'm trying to build a parser, this time with boost.xpressive instead of using boost.spirit. In spirit I have this function that displays when parsing failed: template< class ParseInfo > void printParsingError( boost::sub_range<std::string> range, const ParseInfo& info ) { std::cerr << "\n\n" << "Parsing of file failed. The parser matched:\n\n" << "-------------------------------------------\n[start]"; std::cerr << std::string( range.begin(), info.stop ); std::cerr << "[stop]\n"; std::cerr << "\nThe input was:\n\n" << "-------------------------------------------\n[start]"; std::cerr << std::string( range.begin(), range.end() ); std::cerr << "[stop]\n"; std::cerr << std::endl; } Can I get the same info with xpressive somehow? Thanks -Thorsten

2 1