February 2008 - Boost - lists.preview.boost.org

[config] compiler/sunpro_cc.hpp seems to need increment on latest tested version
by Tobias Schwinger 07 Feb '08

07 Feb '08

Hi, just keeping some form to please anti-spam tools (the subject says it all). Regards, Tobias

2 1

Serialization of Range library's sub_range
by brass goowy 06 Feb '08

06 Feb '08

Shalom A possibly easier to read version of this note is here - http://home.seventy7.com/misc/range_postfeb608. Previously I suggested there should be serialization support wrt the Range library - http://lists.boost.org/Archives/boost/2008/01/132294.php. I'm writing to inform you of my plans in this regard. This input: Msgs (sub_range<list<short> >) @OUT } to the C++ Middleware Writer, http://home.seventy7.com/cgi-bin/samb.cgi, results in this output: #include <boost/range/sub_range.hpp> #include <list> #include <Buffer.hh> using boost::sub_range; struct Msgs { inline Msgs() {} inline ~Msgs() {} inline int Send(Buffer* buf, const sub_range<list<short> >& about1) { unsigned int headCount = 0; headCount = about1.size(); if (!buf->Receive(&headCount, sizeof(int))) { buf->ews_.SetErrorWords(1, __FILE__, __LINE__); return 0; } list<short>::const_iterator rit1 = boost::begin(about1); list<short>::const_iterator rit2 = boost::end(about1); for (; rit1 != rit2; ++rit1) { if (!buf->Receive(&(*rit1), sizeof(short))) { buf->ews_.SetErrorWords(1, __FILE__, __LINE__); return 0; } } if (!buf->SendStoredData()) { buf->ews_.SetErrorWords(2, __FILE__, __LINE__); return 0; } return 1; } }; This functionality isn't available online yet. G-d willing, it will be available by the middle of next month. The file Buffer.hh is here - http://home.seventy7.com/misc/Buffer.hh. There's also a version that calculates and sends the total message length here - http://home.seventy7.com/misc/rangeMsg.hh. (An option on the front end is checked to obtain this functionality.) This thread on clc++m, http://preview.tinyurl.com/218cnh, convinced me of the need to support total message lengths. The @OUT used above as input to the C++ Middleware Writer indicates you only want a Send function--by default both a Send and Receive function are generated. I believe sub_range supports operator << but not operator >>. So the @OUT option is necessary when using sub_range. A container could be used to receive data sent via the above Send function; as Middle code it would look something like this: Msgs (sub_range<list<short> >) @OUT (vector<short>) @IN } Brian Wood Ebenezer Enterprises www.webebenezer.net Keep your heart with all diligence; for out of it are the issues of life. Proverbs 4:23

1 0

Aspen Meadows Sold Out
by Jared McIntyre 06 Feb '08

06 Feb '08

I just got off the phone with Dolce, and they said there are no rooms available in the reserved block for the conference. Too bad, it was really nice there last year (apparently I had Madeline Albright's favorite room). But, you snooze, you loose. Has anyone started to look at other locations? Jared

4 7

Supressing MSVC 'unsafe' warnings (was : [xpressive] Lots of warnings on VS9)
by Darren Garvey 06 Feb '08

06 Feb '08

On 05/02/2008, Eric Niebler <eric(a)boost-consulting.com> wrote: > > Robert Dailey wrote: > > On Feb 5, 2008 3:11 PM, Eric Niebler <eric(a)boost-consulting.com> wrote: > >> I'm against Boost globally disabling any warnings. IMO, it's really the > >> user's call. > > > > I believe boost should keep itself clean, whether that means fixing > warnings > > properly or hiding them via #pragma directives. It's my responsibility > to > > hide my own warnings in my own source files, not in boosts. That's just > my > > opinion on the subject of warnings. > > An organization may have a policy to disallow use of "unsafe" constructs > that could lead to unchecked buffer overflows. They would want actually > want to know if Boost headers were using raw pointers as output > iterators, for instance. If Boost disables these warnings for its own > code, it presents a barrier to adoption for these organizations. > > If Boost adopts a policy whereby noisy warnings are disabled for Boost > code, there should at least be a well-documented method for re-enabling > these warnings for the people who care about them. The concern is that, > since nobody reads the docs, and since the lack of warnings actually > hides the issue, it could lead to a false sense of security. It seems > like the wrong default to me. The attached patch attempts to globally silence these warnings unless --show-all-warnings is passed on the command line. It should only work for the main boost build process and for user builds that explicitly use a library's build/Jamfile.v2 and bjam. Also, there's a warning emitted that explains what's happening. I'm sure there are better ways of doing this, but the patch is really simple and seems to work as expected. It's there if anyone finds it useful. Cheers, Darren P.S. I've not got access to MSVC8.0 and I seem to remember there being three defines you needed to supply but I can't remember what they all were.

1 0

[xpressive] semantic actions: is ref() necessary
by Thorsten Ottosen 06 Feb '08

06 Feb '08

Hi Eric, My semantic actions might look like +(name[push_back(ref(causeNames),as<std::string>(_) )]); My first question here is whether ref() is really necessary? In your example from the documentation, I can better understand it: [ ref(result)[s1] = as<int>(s2) ]; because you apply the [] operator to the result. But otherwise, is there any time you not want a reference stored? In my case above, couldn't the destructor of push_back() take a T& argumentment and construct a lazy reference from that? I also have another question: is it really necessary to write the as<std::string>(_) part of the semantic action? Can this type not be deduced from the template argument to push_back()? In my case it would simply be Container::value_type. If so, we would end up with the really slick looking +(name[push_back(causeNames)]); best regards -Thorsten

3 4

[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