- Boost - lists.preview.boost.org

Review Request: future library (Gaskill version)
by Braddock Gaskill 30 May '08

30 May '08

I wanted to formally request a review of my Futures library. Latest Version: http://braddock.com/~braddock/future/ The library has matured greatly over the past year. It has been heavily used as a key component in a mid-sized commercial application on both Linux and Windows. Extensive unit tests and (just now) documentation have been written - in fact there are more than twice as many lines of test code and documentation than are in the library proper. The library incorporates many ideas from this list, from other prospective submissions, other languages, and from academic papers. The library does not currently use jamfiles or boostdoc (I tried I really did). It is a header-only library. The documentation is currently straight HTML, and should be very easy to translate to boostdoc if the submission looks good. NOTE - to avoid confusion, note that there is an older 2005 boost.future candidate in the vault by Thorsten Schuett that is not related to mine (although it was studied early on). Thanks, Braddock Gaskill braddock(a)braddock.com

10 100

[thread] suspend/resume functions
by vicente.botet 30 May '08

30 May '08

Hello, Currently we can interrupt a thread. Have the functions suspend/resume a sens for a thread? Best regards Vicente

2 1

[config] C++0x macros
by Beman Dawes 30 May '08

30 May '08

There was some past discussion of changing the C++0x BOOST_HAS_* macros to BOOST_NO_*. Several participants thought that was better for the long run. Who needs to do what to make this happen? The motivation for asking is that I'm starting to update some Boost code that could benefit from C++0x features and so would like to start using these macros. Also, a C++03 workaround for the lack of the C++0x keyword "constexpr" is to simply omit it. Should we have a BOOST_CONSTEXPR macro defined as "constexpr" for platforms that support constexpr, otherwise as null? --Beman

14 31

[spirit] 'nother patch, (building example5.cpp on gcc4.2), attribute_transform.hpp
by troy d. straszheim 30 May '08

30 May '08

Hi again guys, This one is easier. Having applied the assign_to/construct patch, examples 4 and 6 compile fine, but example5.cpp died on this: example5.cpp:283: instantiated from here ../boost/trunk/boost/spirit/home/support/attribute_transform.hpp:144: error: ambiguous class template instantiation for 'boost::spirit::traits ::strip_single_element_sequence< boost::fusion::vector< boost::variant< unsigned int, string, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_ >, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_ >, mpl_::bool_<false> >' ../boost/trunk/boost/spirit/home/support/attribute_transform.hpp:144: error: invalid use of incomplete type 'boost::spirit::traits ::strip_single_element_sequence< boost::fusion::vector< boost::variant< unsigned int, string, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_ >, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_ >, mpl_::bool_<false> >' ../boost/trunk/boost/spirit/home/support/attribute_transform.hpp:32: error: declaration of 'boost::spirit::traits::strip_single_element_sequence< boost::fusion::vector< boost::variant< unsigned int, string, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_, boost::detail::variant::void_ , boost::detail::variant::void_ >, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_, boost::fusion::void_, boost::fusion::void_ , boost::fusion::void_ >, mpl_::bool_<false> >' You just disambiguate via enable_if to get things building. Works on gcc4.2: --- attribute_transform.hpp (revision 45915) +++ attribute_transform.hpp (working copy) @@ -11,6 +11,7 @@ #include <boost/spirit/home/support/unused.hpp> #include <boost/spirit/home/support/component.hpp> #include <boost/spirit/home/support/attribute_of.hpp> +#include <boost/spirit/home/support/detail/values.hpp> #include <boost/fusion/include/vector.hpp> #include <boost/fusion/include/is_sequence.hpp> #include <boost/variant/variant_fwd.hpp> @@ -25,16 +26,19 @@ namespace traits { + using boost::spirit::detail::not_is_variant; + // Here, we provide policies for stripping single element fusion // sequences. Add more specializations as needed. - template <typename T, typename IsSequence> + template <typename T, typename IsSequence, typename Enable = void> struct strip_single_element_sequence { typedef T type; }; template <typename T> - struct strip_single_element_sequence<fusion::vector<T>, mpl::false_> + struct strip_single_element_sequence<fusion::vector<T>, mpl::false_, + typename boost::enable_if<not_is_variant<T> >::type> { // Strips single element fusion vectors into its 'naked' // form: vector<T> --> T @@ -42,7 +46,8 @@ }; template <typename T> - struct strip_single_element_sequence<fusion::vector<T>, mpl::true_> + struct strip_single_element_sequence<fusion::vector<T>, mpl::true_, + typename boost::enable_if<not_is_variant<T> >::type> { // Strips single element fusion vectors into its 'naked' // form: vector<T> --> T, but does so only if T is not a fusion Let me know if you just want a commit, (also for the other stuff). There are a few more things like this around, I'll get after them. Thanks for a great library (these little gotchas notwithstanding). I'm getting a real kick out of all this, learning a lot... this code is *crazy*. You guys have definitely raised the bar. -t

2 1

[date_time] boost time is lacking a big bang
by Joachim Faulhaber 29 May '08

29 May '08

Hi! My first goal in boostifying my proposed interval template library (ITL http://sourceforge.net/projects/itl) was to provide good examples for interval_sets and interval_maps using boost::date_time objects. This was much harder than I had expected, because incidentally the most important syntactical and semantical requirements that I do rely on for a parameter T of itl::interval<T> are not provided by boost::date_time. The one property of boost::date_time that knocked my socks off was the default constructor that 'is-not-a-date-time'. I paraphrase this as: boost::time is lacking a big bang ;-) Default constructors in nearly all the types that I've seen in my lifetime (I know the realm of my unknown unknowns is vast ;-) are intended to be elements of the type they do construct. Moreover in so many cases including built in types, default ctors serve as *initial elements*. Other elements can be *reached* from T() applying operations of T on them. This applies to all built in types and many std::types, like e.g. string, set, list etc. The most simple instance is unsigned int() with increment operation ++ that resembles the Peano axiomatic operations 0 and successor for natural numbers. This semantics of default ctors, at least in common built in and standard types and also in so many user defined types is so fundamental that I took it as a *semantical invariant* for the construction of my library. In the ITL an empty interval<T> [1,0] for instance, has to be defined generically: [ type<T>::unon(), type<T>::neutron() ] where type<T>::neutron() is implemented via T() : the default ctor and type<T>::unon() is implemented via ++T() : the default ctor incremented exactly once. So, striving to be as generic as possible I tried to set those minimal requirements that I assumed to be common sense: For discrete types T, the existence of an initial value T() and In(De)crementation. Instead of being a big bang of time, boost::date_times default constructors are cannibals. They give birth to a date_time() object that they immediately swallow. Then saying schizophrenic things about themselves like: cout << to_simple_string(ptime()); "not-a-date-time" They are singularities having an infinite gravitational pull on any operators. You can apply as many of them on the constructed black whole and they are never seen again having no effect. In addition to making the expected source of all elements of boost::date_time an awesome creature to be avoided, the universal c++ way of saying the next object within minimal distance '++' has also been taken away from me. May be with the good intension to prevent me from doing silly things like iterating over whole centuries in nanoseconds ;-) Yet all my applications of ++ and -- in my generic code use them only once like in comparing intervals of discrete types (a, b] == [c, d] is true, if(++a==c && b == d) that have different borders. I only have to make sure here that the minimal distance is proceeded only once. To summarize: What I have been relying on in my design, an initial default ctor T() and an increment operator ++ on the least availabel distance unit is exactly not provided by boost::date_time. Now the good news: Both libraries are so well designed that these seemingly contrarian designs can still be coupled with relatively small changes. Specifically, which is crucial for me, I can adapt my libraries code so that I can use all of boost::date_time in it's current form without patching anything (which would also work as I wrote in my last posting). The seemingly most decoupled remedy was, to implement the the missing functions type<T>::neutron() as well as increment ++ and decrement -- operators using the public interface of boost::date_time. This had to be done for every boost::date_time type like e.g. ptime: itl/ptime_adapter.hpp: ------------------------------------------------------------- boost::posix_time::ptime operator ++(boost::posix_time::ptime& x) { return x += boost::posix_time::ptime::time_duration_type::unit(); } boost::posix_time::ptime operator --(boost::posix_time::ptime& x) { return x -= boost::posix_time::ptime::time_duration_type::unit(); } template<> inline boost::posix_time::ptime type<boost::posix_time::ptime>::neutron() { return boost::posix_time::ptime(boost::posix_time::min_date_time); } ------------------------------------------------------------- Drawbacks of this are: (1) Designs are not completely decoupled, for every boost::a_date_time the matching adapterfunctions must be included. This is a complication for the usage. (2) *Every* generic library that relies on the existence of an initial default ctor and incrementation has to provide an adapter. (3) Every adapter has to be maintained, when boost::date_time is changed. (Kind of a distributed responsibility that is error prone) I would suggest, that a type that in it's basic characteristics resembles an intergral numeric type like boosts date_time types, that type should follow the concept Integral. cheers Joachim Interval Template Library download from http://sourceforge.net/projects/itl documentation http://www.herold-faulhaber.de/

5 9

[smart_ptr] trunk version of enable_shared_from_this incompatible with TR1
by Daniel Frey 29 May '08

29 May '08

TR1 states that the dtor of enable_shared_from_this is non-virtual, the trunk version violates this. Regards, Daniel

6 25

[shifted_ptr] Neural networks
by Phil Bouchard 29 May '08

29 May '08

Greetings: I have made some changes into my sandbox and I am happy to say some tests send by Steven a while ago are now working correctly. The interface was previously supporting only allocations made by "new_sh". I was aware of this but now I am adding a solution to make shifted_ptr generic enough. The solution is still a non-portable one but will be corrected shortly; it consists of detecting the stack frame and I am using gcc's __builtin_frame_address(). I also replaced Nedmalloc for Boost.Pool because I temporarily wish to reduce problems I might face. The problem with Boost.Pool is that it doesn't handle arbitrary sized chunks and the complexity goes down to O(n) for array allocations. All in all shifted_ptr behaves differently when a pointer resides either on the: 1. stack & data segment 2. local heap 3. system heap Moreover the test file shifted_ptr_test3.cpp which uses BOOST_TEST macros is crashing on gcc for Windows. The same tests appears in shifted_ptr_test2.cpp and work correctly. Finally yes I definitely need to write documentation about this but I will basically need to write something similar to a book. For now I just want to present a working example and here it is. The ultimate objective of shifted_ptr is to handle neural networks for artificial intelligence testings so feel free using the pointer in your tests to help me finding flaws that might still exist. Regards, -Phil

1 1

[spirit][xpressive][memory] A new regex library: TPL
by shiwei xu 29 May '08

29 May '08

TPL is short for "Text Processing Library". It is a spirit/xpressive like library. I used spirit/xpressive. But the codes based on spirit or xpressive was compiled slowly. Here are some hints of TPL: * It is simple. * It will always be compiled fast. * It is based on Boost-Memory (still is a sandbox library). Here is an example of TPL: #include <stack> #include <tpl/RegExp.h> #include <tpl/ext/Calculator.h> #include <cmath> using namespace tpl; void calculate2() { typedef SimpleImplementation impl; // ---- define rules ---- impl::Allocator alloc; std::stack<double> stk; impl::Grammar::Var rFactor; impl::Grammar rMul( alloc, '*' + rFactor/calc<std::multiplies>(stk) ); impl::Grammar rDiv( alloc, '/' + rFactor/calc<std::divides>(stk) ); impl::Grammar rTerm( alloc, rFactor + *(rMul | rDiv) ); impl::Grammar rAdd( alloc, '+' + rTerm/calc<std::plus>(stk) ); impl::Grammar rSub( alloc, '-' + rTerm/calc<std::minus>(stk) ); impl::Grammar rExpr( alloc, rTerm + *(rAdd | rSub) ); impl::Rule rFun( alloc, "sin"/calc(stk, sin) | "cos"/calc(stk, cos) | "pow"/calc(stk, pow) ); rFactor.assign( alloc, real()/assign(stk) | '-' + rFactor/calc<std::negate>(stk) | '(' + rExpr + ')' | (gr(c_symbol()) + '(' + rExpr % ',' + ')')/(gr(rFun) + '(') | '+' + rFactor ); // ---- do match ---- for (;;) { std::string strExp; std::cout << "input an expression (q to quit): "; if (!std::getline(std::cin, strExp) || strExp == "q") { std::cout << '\n'; break; } try { while ( !stk.empty() ) stk.pop(); if ( !impl::match(strExp.c_str(), rExpr + eos(), skipws(), alloc) ) std::cout << ">>> ERROR: invalid expression!\n"; else std::cout << stk.top() << '\n'; } catch (const std::logic_error& e) { std::cout << ">>> ERROR: " << e.what() << '\n'; } } } // ------------------------------------------------------------------------- If you are interested in TPL, you can check out its source code from SVN: svn checkout http://libtpl.googlecode.com/svn/trunk/

1 0

[vault] polymorphic_function call wrapper
by Daniel Walker 29 May '08

29 May '08

Hello, Following up on several discussion over the last few weeks, I've placed an implementation of a polymorphic call wrapper (and associated utilities) similar to Boost.Function in the file polymorphic_function.zip in the Function Objects directory on vault at http://tinyurl.com/56zvo4. Here's a brief demonstration to give an idea of what's included: // Work with arbitrary callable objects without loss of polymorphism. template<class Signature> void do_division(polymorphic_function<Signature> f) { // Do floating point division. float one = 1, two = 2; assert(f(one, two) == 0.5); if(is_polymorphic_function<Signature>::value) { // Now, drop the remainder using integer division. int one = 1, two = 2; assert(f(one, two) == 0); // And now, use high precision floating point division to // compute the inverse product of a series of integers. int series[3] = { 1, 2, 3 }; double x = std::accumulate(&series[0], &series[3], 1.0, functional_cast<double(double,double)>(f)); assert(0.16666666 < x && x < 0.166666667); } } // A second class builtin function. float builtin_divide(float x, float y) { return x / y; } // A TR1 result_of compatible function object. struct divide { template<class Signature> struct result : argument_of<Signature, 0> { }; template<class T> T operator()(T x, T y) const { return x / y; } }; int main() { // Promote builtin functions to first class. do_division< float(float,float) >( builtin_divide ); // Perform type-erasure. do_division< float(float,float) >( std::divides<float>() ); // Use polymorphic function objects polymorphically. do_division< divide(_1,_1) >( divide() ); } The file polymorphic_function.hpp provides the following components: * signature/call_signature/erase are metafunctions used to describe polymorphic functions. They allow you to do things like erase the callable object type of a boost::result_of compatible signature so it can be used with boost::function. typedef signature<my_function(int)>::type signature_type; typedef result_of<signature_type>::type result_type; typedef function<erase<signature_type>::type> function_object_type; * is_polymorphic_function is a metafunction used to designate function prototypes that may have variable return types according to boost::result_of. These are a subset of the prototypes detected by boost::is_function. More pertinently, is_polymorphic_function distinguishes the boost::function protocol for specifying function signatures - a.k.a. call signatures - from the boost::result_of protocol - a.k.a. polymorphic signatures. * is_incomplete_function is a metafunction used to designate polymorphic functions with variable argument types. These are a subset of the prototypes detected by is_polymorphic_function. They are described using Boost.MPL placeholders as arguments in the signature. * argument_of is a metafunction used to deduce the types of arguments to functions. It's a more general, nary alternative to the C++98 argument_type member. For example, argument_of can be used to detect call-by-reference functions: template<class F> void g(F f) { int x = 0; int& y = f(x); if(is_reference<typename result_of<F(int)>::type>::value && is_reference<typename argument_of<F(int), 0>::type>::value) assert(&x == &y); } int& my_function(int& t) { return t; } int main() { g(my_function); } * polymorphic_function is a call wrapper, which can be used in place of boost::function to allow both builtin functions and function objects to be used interchangeably without the degradation of polymorphism incurred by wrapping polymorphic function objects in boost::function. Essentially, this is achieved by giving the user the option of either erasing the function object's type as one would with boost::function or retaining the function object's type as one would with boost::result_of. * functional_cast is used to change the signature of a call wrapper. It can be used with both std/boost::function and polymorphic_function. For example, by specifying a new signature one may change the arity or argument types of a call wrapper, so long as the underlying callable object can be described by the new signature. Also included is a test set. I tested on gcc 3.4, 4.3 and msvc 9. The code includes some documentation in the form of inline comments. As far as future work and known defects, this is the first time I have seriously played with C++0x forwarding conventions using std::forward and rvalue references. I'm not confident that I got it perfectly right, so any corrections/guidance would be greatly appreciated. In C++98, I use an argument forwarding technique similar to Boost.Bind and Boost.Lambda - arguments are taken as non-const references and forwarded as rvalue conversions of the types requested in the signature. Secondly, type deduction using argument_of could have better support for function objects in C++98 and currently only supports member template operator() in C++0x. Finally, I'm sure more boost::function-like features could be added to polymorphic_function including members for queryng capacity, comparison operators, an allocator template parameter, etc. Thanks for your time and consideration! Cordially, Daniel Walker

2 4

[thread] Are thread ids unique during an applications life time?
by Johan Torp 28 May '08

28 May '08

IIRC, windows thread ids can be re-used. That is, if you stop a thread X and later start a thread Y they might get the same thread id. Is this the case with boost.thread? What about the standard? It states: "An object of type thread::id provides a unique identifier for each thread of execution and a single distinct value for all thread objects that do not represent a thread of execution ([thread.threads.class]). Each thread of execution has a thread::id that is not equal to the thread::id of other threads of execution and that is not equal to the thread::id of std::thread objects that do not represent threads of execution." http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2497.html#thread.t… Which sounds like thread ids are free to be re-used. Johan -- View this message in context: http://www.nabble.com/-thread--Are-thread-ids-unique-during-an-applications… Sent from the Boost - Dev mailing list archive at Nabble.com.

5 8

property tree and default translator_type
by Christian Holmquist 28 May '08

28 May '08

Hi, I've been using property_tree for quite a while now, and I think it's a very useful library, many thanks to the authors for their work! I'm wondering if it's possible to refactor it a bit, so that users can configure it to be more lightweight? In it's current form it pulls in quite a lot dependencies, where many are used only by the default template translator parameter (which is std::stringstream based); If I supply a translator of my own I won't get rid of the includes in ptree.hpp. Wouldn't it be better that users include property_tree/translator.hpp when they need to parse data from the tree? In my experience I often need to manipulate the property_tree, but without doing and type conversion. Such code would compile faster with the translator left out. Pushing it a bit further, I don't think the translator should be a class member template at all, since it has nothing to do with the contents of the tree. Parsing of data is done on a 'use-case' basis, meaning that different code has different requirements on the parser, even if it reads the data from the same tree. With the current design I cannot choose to parse an int (say) using boost.spirit at one location, and the default stringstream parser at another, unless instantiating a new basic_ptree<...> type. I am of course free to not use the translator and instead access data() directly and pass it to the parser of my choice, but then I need to reimplement some parts of the get_value and get_optional which are very useful as they are now (and probably more carefully written than I would come up with). I would prefer the translator to be a template parameter to the get()/get_xxx() functions instead. This would probably give faster code for the end-user too,since they are encouraged to instantiate a translator before parsing values from the tree. The default translator would in this case reuse its internal stringstream object, instead of recreating one for every read. Something like this: property_tree::ptree pt; property_tree::translator t; pt.get_value<int>(t); pt.get_value<float>(t); pt.get_value<int>(my_custom_number_parser()); The above would create only one stringstream, compared to: property_tree::ptree pt; pt.get_value<int>(); // stringstream() pt.get_value<float>(); // stringstream() // I cannot use my_custom_number_parser here at all, unless creating some kind of composite translator type, which isn't easy when dealing with polymorphic function objects. Thoughts on this, anyone? / Christian

2 2

the beginning of a pattern/gesture recognition library
by Stjepan Rajko 28 May '08

28 May '08

Hello, I have started moving some code into a Boost-based open source generic pattern/gesture recognition library (I briefly mentioned it at my Dataflow+Arts talk at BoostCon) . The examples right now show how to do gesture recognition on some pre-segmented video captures of full-body human gestures, as well as pattern recognition in sequences of floating-point numbers. Soon I'll be adding something for recognition of mouse gestures. The library docs and download info is at: http://ame4.hc.asu.edu/amelia/patterns/ The library is currently GPLed but that's open to debate (this is my research program's first venture into open source and GPL was the safest initial choice). As the library matures I'd like to move it to the Boost license and eventually submit it for Boost review. If anyone is interested in using this library or joining the development, please let me know. The few tests/examples have so far been verified to work on GCC4.0.1/darwin and MSVC8. Kind regards, Stjepan

2 2

BoostCon library in a week (sequence)
by Marshall Clow 28 May '08

28 May '08

The first part of the BoostCon "library in a week" code has been uploaded to the sandbox in "sandbox/boost/algorithm/copy.hpp", and it is a set of variations on std::copy. Doxygen generated documentation is available here: <http://www.idio.com/copy/copy_8hpp.html> and more formal documentation will be available soon. The algorithms in this file are: copy_if (iterator and range based versions) copy_backwards_if (iterator and range based versions) copy_while (iterator and range based versions) copy_backwards_while (iterator and range based versions) copy_n copy (range-based version only) copy_backwards (range-based version only) [ The iterator-based versions of copy and copy_backwards are in the standard library ] When the documentation is ready, we will request a mini-review. -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Re: [boost] tokenizer
by Lars Schouw 28 May '08

28 May '08

Got it now ;)#include<iostream>#include<boost/tokenizer.hpp>#include<string>void { string s = {main()usingnamespacestd;usingnamespaceboost;"LDNTOK";if(s.size() > 3)// insert comma by every 3 charssize_t len = s.size(); { s.insert( i, 1, } tokenizer<escaped_list_separator< { cout << *beg << std::endl;for( size_t i = ((len-1)%3) + 1; i < len; i+=4, ++len )',');char> > tok(s);for(tokenizer<escaped_list_separator<char> >::iterator beg=tok.begin(); beg!=tok.end();++beg)// load holiday calendar *beg} }// else just load holiday calendar} ----- Original Message ---- From: Lars Schouw <schouwla(a)yahoo.com> To: boost(a)lists.boost.org Sent: Wednesday, May 28, 2008 10:20:24 PM Subject: tokenizer Can I use the tokenizer to seperate my command and every 3 chars? I have a string A) XXXYYY B) XXX,YYY Can I use the tokenizer to seperate these? I want to to check for strings of type A and then B. Here is some code that does B but what about A before? #include<iostream>#include<boost/tokenizer.hpp>#include <string>void { string s1 = string s = tokenizer<escaped_list_separator< cout << *beg << } }main()usingnamespacestd;usingnamespaceboost;"LDNTOK";"XXX,YYY";char> > tok(s);for(tokenizer<escaped_list_separator<char> >::iterator beg=tok.begin(); beg!=tok.end();++beg){"\n"; Cheers. Lars

1 0

Trac open bugs - by assignee
by Marshall Clow 28 May '08

28 May '08

[ 312 open bugs today, 309 yesterday ] If you are maintaining a library, and have not logged into the trac system at <http://svn.boost.org/trac/boost/>, please do so ASAP. Until you do that, no tickets can be assigned to you, and will remain under "None". Instructions on working with tickets can be found at: <http://svn.boost.org/trac/boost/wiki/TicketWorkflow> and a mapping of user names to "real names" can be found at: <http://svn.boost.org/trac/boost/report/16> Bug summary 34 djowel 28 az_sw_dude 26 dgregor 24 grafik 21 dave 17 bemandawes 14 ramey 14 agurtovoy 12 vladimir_prus 12 no-maintainer 11 jsiek 9 rogeeff 9 nesotto 8 anthonyw 6 turkanis 6 johnmaddock 5 kaalus 5 igaztanaga 5 danieljames 4 witt 4 pavol_droba 4 ebf 4 None 3 samuel_krempp 3 nasonov 2 troyer 2 shammah 2 marshall 2 jmaurer 2 hkaiser 2 gmelquio 2 garcia 2 danielw 1 urzuga 1 t_schwinger 1 speedsnail 1 matias 1 fcacciola 1 dlwalker 1 aaron_windsor 1 <Blank> <Blank> 1750 Autolink library name not in sync with actually build lib None 1736 Headers containing non ASCII characters cause MS VC to issue warning 4819 in some locales None 1907 name of library files on mingw None 1927 MacOS (Darwin) should use the -headerpad_max_install_name option None 1928 complete + icu build fails on darwin (MacOS 10.4.11) aaron_windsor 1622 Adjacency list needs to handle self-edges correctly agurtovoy 1001 gcc 4.1.2 segfaults on mpl/test/apply.cpp agurtovoy 1051 MPL header ordering triggers bug agurtovoy 1099 unable to iterate through a "non-explicitly-declared" mpl::set agurtovoy 1215 Boost 1.34.1_ mpl: Wrong workaround detection using MinGW32 (or.hpp_ line #33) agurtovoy 1317 has_xxx randomly broken in msvc agurtovoy 1469 [mpl] nested typedef of set has two different meanings agurtovoy 1476 always<> is not nullary. agurtovoy 1528 g++ 4.3.0 reports error because of redeclaration of next agurtovoy 1549 Boost.MPL: 'index_of' algorithm is not documented agurtovoy 1568 duplicate include guards agurtovoy 1900 Missing documentation for mpl::print in the MPL library agurtovoy 1901 Missing documentation for mpl::for_each in the MPL library agurtovoy 1916 [mpl] MPL_HAS_XXX_TRAIT_DEF bug in MSVC71 agurtovoy 588 mpl::remove compile error with gcc 4.1.0 anthonyw 1154 tss destruction segfaults in conjunction with dlopen/dlclose anthonyw 1470 Boost.Thread: Compilation errors with non-__cdecl calling convention anthonyw 1825 thread.hpp injects windows.h and breaks user application. anthonyw 1826 Auto detection of threadapi and target-os broken under cygwin gcc anthonyw 1867 Missing member functions in shared_mutex (win32) anthonyw 1929 Borland/Codegear C++ 2007 creating boost::thread fails at initialisation of membervar boost::thread::thread_info anthonyw 1958 thread_specific_ptr lacks support for NULL cleanup function anthonyw 1965 There is no documented swap(thread&_thread&) az_sw_dude 1028 typo in boost header: date_time/time_defs.hpp az_sw_dude 1078 from_iso_string cannot read the output from to_iso_string az_sw_dude 1098 Urgent libboost-date-time1.33.1 : bugs on ia64 ? az_sw_dude 1147 date_time library contains global #define ERROR az_sw_dude 1160 warning: month_format shadows a member of this az_sw_dude 1162 warning: ticks shadows a member of this az_sw_dude 1289 posix_time::time_facet forgets to pass a_ref argument to base class az_sw_dude 1299 change in typedef stringstream_type in format_date_parser.hpp causing compilation error az_sw_dude 1306 invalid docbook in date_period.xml az_sw_dude 1384 Linking problem with date_time library on Visual C++ 2008 Express az_sw_dude 1524 format_date_parser.hpp(221) : cannot convert parameter 1 az_sw_dude 1574 operator<< for boost::posix_time::ptime ignores ostream flags az_sw_dude 1674 date_time::date_formatting.hpp: incorrectly formats year using global locale az_sw_dude 1695 add correct namespace to class to fix compilation bug az_sw_dude 1726 boost/date_time/posix_time/time_formatters.hpp incorrectly formats fractional seconds using global locale az_sw_dude 1740 date_time includes <windows.h> az_sw_dude 1788 local_time::local_time_period streaming operators not implemented az_sw_dude 1859 boost::gregorian::to_tm() doesn't fill in tm_zone on Mac OS X az_sw_dude 1878 Documention Corrections - Various date_time Pages az_sw_dude 1903 [date_time] - 1.34+ c_local_adjustor derefs null pointer for dates >2038 az_sw_dude 1933 special_values not found when compiling date_time/time.hpp az_sw_dude 1934 iterator reference zero when reading time zone [with patch] az_sw_dude 287 wrong usage of ios_base::narrow az_sw_dude 316 date_time type conversion warning az_sw_dude 604 from_ftime incorrectly processes FILETIME filled with zeros az_sw_dude 642 operator<< for gregorian::date_duration not found az_sw_dude 889 Insane Dependencies az_sw_dude 890 date_time library supports only the current dst rule bemandawes 1378 filesystem path invalid name for hidden files (LINUX) bemandawes 1389 filesystem::ostream << boost::format generates operator ambigious error (in MSVC++) bemandawes 1458 Darwin Tiger throws std::runtime_error: locale::facet::_S_create_c_locale name not valid bemandawes 1578 bug in readdir_r_simulator() in a multi-threaded environment bemandawes 1583 Serious flaw in boost::filesystem filename handling (opensuse) bemandawes 1589 [filesystem] 'mbstate_t' : is not a member of 'std' bemandawes 1606 filesystem/src/exception.cpp doesn't build with gcc bemandawes 1613 Link Errors against file_system on OS X with Intel Version 10.1 C++ compilers bemandawes 1682 path_traits needs imbue() bemandawes 1701 boost::filesystem::remove_all - segmentation fault with wpath on Linux bemandawes 1711 Boost Serialization export facility broken on gcc 4.1_ 4.2 bemandawes 1767 missing file: boost/filesystem/cerrno.hpp bemandawes 1768 system: error_code.cpp #defines macros without checking whether already defined bemandawes 1840 name check functions have different behavior wrt empty string bemandawes 1876 portable_file_name() returns true for '.' and '..' bemandawes 1962 Doesn't measure wall clock time bemandawes 752 directory_iterator doesn't work with catch danieljames 1554 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support new string types. danieljames 1555 When BOOST_HASH_NO_EXTENSIONS is defined hash doesn't support boost::system::error_code danieljames 1742 Some bugs in http://www.boost.org/doc/libs/1_35_0 danieljames 1743 Documentation has incorrect Build & Link settings for some libraries danieljames 1923 Unordered move implementation doesn't work in Borland. danielw 1054 Parameter takes an "infinite" amount of time to compile with the Intel compiler. danielw 1097 keyword.hpp generates many warnings C4180: qualifier applied to function type has no meaning; ignored dave 1010 linking boost.python on freebsd dave 1019 iterator_facade::pointer should be the return type of operator-> (DR 445) dave 1085 Python rules for compiling in Mac OS X dave 1179 [boost.python] can not export a union in VC2005sp1 dave 1181 [boost.python] can modify enum value dave 1387 Review / update docs to reflect changes dave 1460 Python classes with multiple bases are convertible only to the first class in the lists dave 1482 boost::python::throw_error_already_set should be marked noreturn dave 1516 [python] Failing VC9 regression tests dave 1599 [python] '_set_se_translator': identifier not found dave 1697 [utility][noncopyable] ADL barrier broken by msvc-9.0 dave 1730 No debug libs on Windows by default dave 1744 [getting started] No information on building static libraries with bjam under Windows dave 1851 Issue with proxies and rvalues dave 1860 zip_iterator::value_type should not be reference dave 1887 [doc] input_iterator_archetype is not a valid InputIterator dave 1890 Missing parameters in example code dave 1931 Boost.Python headers won't compile with GCC 4.3 dave 1952 The operation static_cast<std::string>(boost::python::extract<std::string>(...)) crashes Python. Seems to create reference counting problem. dave 865 Use of C++0x keyword as identifier dave 910 gcc strict-aliasing problems with python dgregor 1009 Improper overflow handling in shortest paths algorithms dgregor 1021 [Graph][reverse_graph] Problem using reverse_graph adapter with an adapted user defined graph dgregor 1076 compile error: disconnecting struct with operator()() doesn't work in VS2005 SP1 dgregor 1164 Floyd Warshall broken with unsigned edge weights dgregor 1192 [boostbook] problem when two files have the same name dgregor 1199 configure doesn't work with path containing whitespaces (MacOS X) dgregor 1310 [result_of] const-qualified function pointer doesn't work dgregor 1326 Unable to check graph isomorphism using LEDA adapter dgregor 1391 dominator_tree_test on Borland/CodeGear outputs overly long line dgregor 1630 gcc-4.3: adjacency_list.hpp includes deprecated header dgregor 1910 function::swap should avoid doing memory allocations dgregor 1943 (minor) configuring with header-only libraries. dgregor 1945 Update CMake configuration introduction for CMake 2.6.0 dgregor 375 LEDA graph adaptors do not handle hidden nodes properly dgregor 402 random_vertex/random_edge are unnecessarily inefficient dgregor 403 Document copy_component dgregor 447 reverse_graph and constness of property maps dgregor 556 Bundled graph properties dgregor 708 Dijkstra no_init version should not require VertexListGraph dgregor 732 Johnson All-Pairs needs better "no path" information dgregor 733 Numbered headers don't work with "preferred" syntax dgregor 735 Fruchterman-Reingold grid performance can be improved dgregor 736 Const correctness violation dgregor 738 Memory leaks with signal::connect? dgregor 829 Implicit graph not implement dgregor 852 Problem with Boost and GCC 4.1 djowel 1170 Emit Warnings instead of # symbols in the syntax highlighter djowel 1171 Quickbook title output djowel 1172 non-utf djowel 1176 Space after inline code djowel 1206 Escaping from within code? djowel 1273 CR+LF newlines in position_iterator djowel 1276 spirit problem with _GLIBCXX_DEBUG djowel 1277 Closing section like [pre with } causes Quickbok to crash djowel 1280 sections in imported source files get put inside <para> elements in docbook output djowel 1281 Quickbook produces invalid BoostBook/DocBook XML djowel 1324 tuple should have a swap() that operates element-by-element djowel 1396 wrong result_of invocation around transform_view djowel 1436 [quickbook] inline code inside headings djowel 1484 Quickbook produces illegal docbook for some docinfo fields. djowel 1500 [Spirit/Phoenix] C4512 Compiler warnings from VC8 djowel 1570 Some boost headers aren't ready for gcc 4.3 djowel 1600 duplicate include guard djowel 1601 distane of boost::tuple djowel 1607 Tuple Library Documentation Changes djowel 1610 [MSVC/STLport] [tree/common.hpp] Standard library requirements violation(incomplete type as vector parameter) djowel 1614 vector workaround needed for MSVC9 djowel 1617 spirit gcc-4.3 fix djowel 1619 [Fusion] C4512 warnings from VC9 (Visual Studio 2008) djowel 1651 incorrect typedefs in examples djowel 1763 wrong AST when parser_tag==0 djowel 1764 wrong AST when parser_tag==0 djowel 1844 Quickbook matches forward slashes (for italics) with slashes in links djowel 1864 [Documentation]There is no documentation for repetivive_view djowel 1872 [Spirit2] 'assignment operator could not be generated' warnings from VC9 djowel 1892 boost::spirit::static_ causes link error (using wave) djowel 1893 Documentation Corrections to map.html djowel 1894 fusion\support\tag_of.hpp_ boost::fusion::traits djowel 1920 lexical_cast with tuple target fails_ because of cleared skipws flag djowel 1953 spirit doesn't use quickbook proper dlwalker 613 boost/crc.hpp uses non-standard conforming syntax ebf 1507 [variant] C4512 warnings from VC8.0 ebf 1548 [variant][docs]typo: formal arg_ operand_ should be v in times_two arglist ebf 1654 recursive variants do not handle nested variants correctly. ebf 993 Variant should use least common multiple of alignments_ rather than maximum fcacciola 1666 Visualizer for boost::optional garcia 1581 Boost.MultiArray: Resizing bug if the index is not 0-based garcia 1741 Review schedule out of date gmelquio 1886 Typo in Interval documentation gmelquio 1944 Interval library pow function doesn't work with mpq_class and similar grafik 1041 Cygwin requires PATH setting. grafik 1322 trac rejects patch attachment as spam grafik 1406 Understanding the Tables outdated grafik 1417 Regresson tests hang in Darwin (Tiger) grafik 1430 Regression fails under Cygwin grafik 1433 Trac's spam detection rejects too many valid messages grafik 1512 Broken link to vacpp in bjam docs. grafik 1513 Broken link to bcpp in bjam docs. grafik 1576 cannot read non-ASCII output messages grafik 1577 Some commands don't work because hStdInput == 0 grafik 1663 build.bat cannot set/reset ERRORLEVEL grafik 1733 Website layout overlays on IE7 grafik 1735 [website] Wrong HTML on main documentation page. grafik 1738 Boost Jam details and download link grafik 1739 Search box and Google link grafik 1753 Python docs: bad link to the Jamroot grafik 1771 Statechart TOC mangled. grafik 1776 Documentation page renders incorrectly in Safari 3.1 on OS X grafik 1906 Trac site too hard to find grafik 1930 The userman.pdf boost-build documentation is outdated grafik 1940 broken links grafik 616 Boost Jam_ and non english directorys grafik 959 linking fails when Boost is compiled with STLport 5.1.* on Linux (names mismatch) grafik 986 Problem building Python modules on boost 1.34.0 hkaiser 1079 boost-1.34.0 fails to compile. concept checks not satisfied. hkaiser 1670 wave almost unusably slow on real-world input igaztanaga 1080 boost::interprocess win32 global file mapping issue igaztanaga 1210 interprocess::barrier hangs during second use under linux (boost 1.33.1) igaztanaga 1390 Interpocess: managed shared memory failing completely under OS X igaztanaga 1634 boost::interprocess::vector cannot contain volatile int igaztanaga 1960 [gcc-4.3] detail/math_functions.hpp misses #include <climits> jmaurer 351 Diff in state of mersenne_twister gen between GCC3.41 & CW9 jmaurer 599 uniform_01 copies engine instead of using a reference johnmaddock 1081 Empty string rejected as perl-style regex johnmaddock 1446 POSIX API doesn't use C locale johnmaddock 1451 error: use of C99 long long integer constant johnmaddock 1863 Boost.Regex unstable with Borland Turbo C++ 2006 johnmaddock 1946 [type_traits] type_with_alignment fails on non-power-of-2 alignment johnmaddock 1959 [regex] C4910 warnings from VC9 jsiek 1531 segfault in dynamic_bitset::reference assign operator jsiek 1540 Poisson distribution very slow for large mean (and may also overflow). jsiek 1755 Boost.tokenizer is broken for wide characters - patch attached jsiek 1798 met an error using boost::tokenizer in multi-times in vs2005_ unicode jsiek 1888 Why doesn't InputIterator require that reference is convertible to value_type? jsiek 1909 Documentation is out of sync jsiek 575 Calling subgraph::global_to_local on a root graph jsiek 636 strange compiling problem for transitive_closure jsiek 815 remove_edge core dumps on self-circle jsiek 875 No iterator based constructor for adjacency_matrix jsiek 900 graphml reader namespace handling is broken kaalus 1184 property_tree assignment (operator) bug kaalus 1604 property_tree xml parser doesn't compile with gcc kaalus 1678 Boost.property_tree::read_xml does not parse UNICODE file with BOMs kaalus 1914 Boost.PropertyTree JSON parser in SVN trunk does not compile with Spirit2 changes kaalus 1955 gcc-4.x and gcc-4.3 fixes marshall 1252 [pool] severe overhead with unaligned sizes. marshall 1854 Interval is not available as a component in the SVN system matias 1822 header dependency in boost/serialization/map.hpp nasonov 1220 lexical_cast requires RTTI nasonov 1847 Can't compile without <locale> header_ boost::lexical_cast problem nasonov 754 boost::any - typeid comparison across shared boundaries nesotto 1629 range/iterator_range.hpp bug nesotto 1675 [range] VC8 - compiler warnings when including range/array headers nesotto 1694 NDEBUG vs. BOOST_ASSERT in iterator_range.hpp nesotto 1748 [ptr_container] compiler warnings from VC9 nesotto 1754 Illegal HTML in range docs. nesotto 1785 assign::list_of works poorly with class constructors nesotto 1795 [ptr_container] minor documentation typo nesotto 1842 boost::sub_rage::front error nesotto 1908 boost::size(std::set<T> const& s) causes compile errors with msvc no-maintainer 1068 Mersenne twister disables streaming for Visual C++ no-maintainer 1222 lambda::ret<T> should declare result_type. no-maintainer 1270 uniform_smallint doesn't compile with lagged_fibonacci random number generators no-maintainer 1515 [lambda] C4512 warnings from VC8.0 no-maintainer 1544 uniform_01 w/ref template param causes ref to ref error no-maintainer 1546 Method boost::random::uniform_int::operator()(engine_ value) is missing no-maintainer 1572 [lambda] smart pointer const-ness affects its contents no-maintainer 1632 Default Interval rounding policies incomplete no-maintainer 1691 [Random] Brokem MSVC workaround no-maintainer 1856 minstd_rand returning different values in 1.35.0 than in 1.34.1 no-maintainer 781 Lambda: (_1 + "y")(string("x")) Doesn't Compile no-maintainer 819 uniform_int<> with type's maximum availaible range error pavol_droba 1152 rle_example fails pavol_droba 1385 begin must be boost-qualified pavol_droba 1761 StringAlgo: Error in an example pavol_droba 1827 String algorithm composite header doesn't include join ramey 1708 Can't serialize class with private destructor ramey 1734 BOOST_STATIC_WARNING can't be passed a dependent expression ramey 1747 [serialization] unreferenced formal parameter warnings from VC9 ramey 1807 boost::archive::xml_archive_exception does not store error code and reports wrong message text ramey 1812 Boost.Serialization fails to build on Cygwin ramey 1823 Archive concept: Incomplete description? ramey 1836 bug in serializing wide character strings ramey 1837 Base class missed in binary_wiarchive ramey 1849 Deserialization of std::string overwrites non-copied contents. ramey 1857 IA64_ GCC 4.3_ redefinition of 'struct boost::serialization::implementation_level<std::vector<long int_ std::allocator<long int> > >' ramey 1877 Documentation Corrections - Archive Concepts ramey 1941 polymorphic archive interface doesn't match other archive interfaces ramey 1942 Pointers to elements in a std::map are not serilaized correctly ramey 1954 gcc-4.3 doesn't compile collection_traits.hpp rogeeff 1383 signal.h features not found on Mac OS rogeeff 1542 [test] compiler errors when building with stdcxx library rogeeff 1644 Boost.Test missing documentation file BOOST_CHECK_CLOSE_FRACTION.html rogeeff 1676 Dead links on Boost.Test example documentation. rogeeff 1723 No subprocess can be started in init_unit_test_suite rogeeff 1746 Online documentation for 1.35.0 is out of date for current lib version rogeeff 1839 Test fails if child process exits with non-zero code rogeeff 1866 Typos in Boost Test documentation rogeeff 1869 Typo in Unit Test Framework documentation samuel_krempp 1699 Compile warning about initialization order. samuel_krempp 1801 Typo in documentation. samuel_krempp 859 boost::format ignores a user defined locale shammah 290 perfomance: memory cleanup for pool takes too long shammah 386 boost::pool_allocator breaks with vector of vectors speedsnail 1138 Problems with TSS and static thread library t_schwinger 1653 wave executable erroneously required for build of function_types lib troyer 1774 serialization: file written with 1.34.1 can't be read in with 1.35 troyer 1778 Possible regression in 1.35 serialization of 2D arrays turkanis 1579 gzip compressor should model DualUseFilter turkanis 1649 Fix definition of JavaScript menu to avoid long chains of functions turkanis 1656 Consider implementing flush() for symmetric filters turkanis 1671 type mismatch of buffer size parameter causes overload resolution to fail turkanis 1875 Boost.Iostreams warnings with GCC -Wall -W -std=c++98 -pedantic turkanis 1896 boost::iostreams::gzip_decompressor silently ignores multiple members urzuga 574 [boost::lambda] Compile error with libstdc++ debug mode vladimir_prus 1132 zero_tokens clarification vladimir_prus 1165 more quoting problems vladimir_prus 1274 Useless error message vladimir_prus 1527 [program_options] Second (and subsequent) lines in tabbed text not aligned correctly vladimir_prus 1537 no value given in 'mysql_password =' vladimir_prus 1584 cryptic bbv2 error building quickbook vladimir_prus 1587 [program_options] crashes if value part missing in external configuration file vladimir_prus 1645 Invalid unicode support for default_value vladimir_prus 1679 added 4-way universal binary support from mac osx (ppc_ ppc64_ i386_ x86_64) vladimir_prus 469 multitoken broken vladimir_prus 689 [program_options] Endless loop with long default arguments vladimir_prus 850 program_options strips off escaped quotes in some situations witt 583 Fixes for build on IBM pSeries for AIX and Linux witt 834 Homepage regression links witt 957 The "Getting Started" page does not mention the stdlib option witt 973 zip_iterator has value_type == reference -- -- Marshall Marshall Clow Qualcomm, Inc. <mailto:mclow@qualcomm.com> The famous British scientist, Lord Kelvin, said: "When you measure what you are speaking about and express it in numbers, you know something about it, but when you cannot (or do not) measure it, when you cannot (or do not) express it in numbers, then your knowledge is of a meagre and unsatisfactory kind."

1 0

tokenizer
by Lars Schouw 28 May '08

28 May '08

Can I use the tokenizer to seperate my command and every 3 chars? I have a string A) XXXYYY B) XXX,YYY Can I use the tokenizer to seperate these? I want to to check for strings of type A and then B. Here is some code that does B but what about A before? #include<iostream>#include<boost/tokenizer.hpp>#include <string>void { string s1 = string s = tokenizer<escaped_list_separator< cout << *beg << } }main()usingnamespacestd;usingnamespaceboost;"LDNTOK";"XXX,YYY";char> > tok(s);for(tokenizer<escaped_list_separator<char> >::iterator beg=tok.begin(); beg!=tok.end();++beg){"\n"; Cheers. Lars

1 0

[futures] reference-counted futures
by Frank Mori Hess 28 May '08

28 May '08

It's occurred to me that support for reference counting futures (which Peter Dimov has suggested a couple times) could be added simply by adding a method to the promise class bool promise::has_future() const; The has_future query would not alter the state of the promise (it wouldn't put it into some unusable "expired" state). It would simply allow the promise-setting thread to query if there are any futures and take whatever action it chooses. So it wouldn't put any burden on someone who wants to code a fire-and-forget function that returns a future that may be safely discarded. In a typical implementation, has_future might boil down to a call of shared_ptr::unique(). This works because threads don't block waiting on promises, only on futures. When a future's promise is destroyed without ever being fulfilled, action has to be taken to give the waiting futures an exception to prevent a thread from blocking forever in vain. But if a promise's last future disappears, it doesn't need to take any action. All it needs to do is provide a query that can be used by interested code to detect that fact. Also, for debugging a unsigned promise::future_count() const; method could be provided, which might be implemented by returning the value of shared_ptr::use_count minus one. Any thoughts? These functions could be added independently of whether or not an explicit future::cancel() is supported.

3 2

Spirit 2 and backwards compatibity?
by John Maddock 28 May '08

28 May '08

I'm having trouble building an app that uses spirit from SVN Head with gcc-4.2 (Mingw32), I see: In file included from c:\data\boost\boost\trunk/boost/spirit/home/classic/core/p arser.hpp:14, from c:\data\boost\boost\trunk/boost/spirit/home/classic/core.h pp:29, from c:\data\boost\boost\trunk/boost/spirit/include/classic_cor e.hpp:11, from c:\data\boost\boost\trunk/boost/spirit/core.hpp:21, from main.cpp:17: c:\data\boost\boost\trunk/boost/spirit/home/classic/core/scanner/scanner.hpp: In member function 'typename boost::detail::iterator_traits<IteratorT>::value_type boost::spirit::scanner<IteratorT, PoliciesT>::operator*() const': c:\data\boost\boost\trunk/boost/spirit/home/classic/core/scanner/scanner.hpp:259 : error: 'iteration_policy_t' has not been declared Any ideas? Note that simply including spirit/core.hpp is enough to trigger this error. Thanks, John.

2 3

Platform Champions needed
by Beman Dawes 28 May '08

28 May '08

Awhile back, there was discussion of setting up a list of platform champions. Platform champions are experts that Boost developers can turn to when they have a problem with a particular compiler or operating system. Whether it is a question about configurations, features, or submitting a bug report to the compiler supplier, these folks know the ropes for the platform. If you are knowledgeable about at platform, and would like to be a platform champion, please add yourself to the list! The list is found at http://svn.boost.org/trac/boost/wiki/PlatformChampions --Beman

4 6

thread_group
by David Abrahams 28 May '08

28 May '08

I don't know if thread_group is supposed to stay around now that we have movable threads, but if we're going to keep it I would like to propose a few changes. 1. add_thread should take an auto_ptr<thread> (and eventually unique_ptr<thread>) so the signature indicates the ownership transfer. 2. remove_thread should be called release_thread. "Release" is at least not ambiguous about whether the thing is being destroyed. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

iterator_facade, decoupling of access and traversal?
by Roland Schwarz 28 May '08

28 May '08

After having read http://www.boost.org/doc/libs/1_35_0/libs/iterator/doc/index.html I have been left, believing that the new iterator concepts will allow me to create an iterator that may return a proxy instead of a reference. I tried to do this by using the iterator_facade template, and for the "Reference" parameter I specified a proxy class that has a conversion operator to the "Value" type. This almost works, but fails for expressions of Val v = it[n]; expressions, because iterator facade does not return "Reference" objects in that case, but operator_brackets_proxy objects that are convertible to "Reference". So I am wondering if I understand something wrong? Isn't the decoupling of access and traversal meant to allow "Reference" be a proxy object? Any hints appreciated! -- _________________________________________ _ _ | Roland Schwarz |_)(_ | aka. speedsnail | \__) | mailto:roland.schwarz@chello.at ________| http://www.blackspace.at

5 10

movable threads, locks, and boost::array
by David Abrahams 27 May '08

27 May '08

I just discovered that while none of my standard containers are "move-aware" in the way needed by boost::thread, I can use boost::array to store threads by simply move-assigning new threads into the elements it contains: boost::array<boost::thread, 100> thread_q; for (int i = 0; i < 100; ++i) thread_q[i] = boost::thread( some_function ); it ain't perfect, but given that the number of cores on any real machine is limited these days, you can do a lot with a fixed-size array of thread. Pretty cool; it sure beats using shared_ptr. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

3 3

[exception] enable_error_info.hpp compile errors
by Beman Dawes 27 May '08

27 May '08

Boost.Filesystem's wide_test is failing on trunk due to enable_error_info.hpp compile errors. It's happening with many (or maybe all) compilers. See below for typical error messages. --Beman ..\boost/exception/enable_error_info.hpp(23): error: not a class or struct name public T, ^ detected during: instantiation of class "boost::exception_detail::error_info_injector<T> [with T=char [29]]" at line 90 instantiation of "boost::exception_detail::enable_error_info_return_type<T>::type boost::enable_error_info(const T &) [with T=char [29]]" at line 58 of "..\boost/throw_exception.hpp" instantiation of "void boost::throw_exception(const E &) [with E=char [29]]" at line 114 of "..\libs\filesystem\test\wide_test.cpp" ..\boost/exception/enable_error_info.hpp(28): error: "T" is not a nonstatic data member or base class of class "boost::exception_detail::error_info_injector<char [29]>" T(x) ^ detected during: instantiation of "boost::exception_detail::error_info_injector<T>::error_info_injector(const T &) [with T=char [29]]" at line 95 instantiation of "boost::exception_detail::enable_error_info_return_type<T>::type boost::enable_error_info(const T &) [with T=char [29]]" at line 58 of "..\boost/throw_exception.hpp" instantiation of "void boost::throw_exception(const E &) [with E=char [29]]" at line 114 of "..\libs\filesystem\test\wide_test.cpp"

2 2

Re: [boost] Question regarding logging, persistence, threadcommunication, network messaging and async frameworks
by brass goowy 27 May '08

27 May '08

Scott Woods writes: >Hi, >Is there a place in Boost for a library that tackles all of the above? I >believe the realistic >answer is no but I would be happy to be proven wrong. >Work in the different areas mentioned in the subject line recently collapsed >into a single >underlying technique. Given the example UDT below; >struct person >{ >std::string name; >std::vector<unsigned> score; >std::set<string> team; >}; >persistence is achieved using; >person new_member; >codec_object<person> configuration( "profile" ) >configuration << new_member; // Save in a disk file name >"profile" >configuration >> new_member; // Load from the same disk file >transmitting the same object between threads looks like; >send( new_member, other_thread ); >while receiving that transmission occurs in code that looks like; >my_thread::received( person &new_member ) >{ >.. >} >Transmission of messages across networks looks like; >send( new_member, socket_proxy ); >Yes, its the same as for inter-thread communications. The "socket_proxy" >just >happens to be a variation on "my_thread" that forwards materials it receives >onto a socket connection. >Logging looks like; >WINSOCK( socket, AF_INET << SOCK_STREAM << 0 ); >COMMENTARY( "connection to " << address_entered << " failed (" << >failure << ")" ); >Logging messages can be routed anywhere based on the type and unique >identity of >the originating party. >The fragments of code provided above hide a lot. While that's technically >desirable >I can appreciate that it might not flesh out my question at all (i.e. >...room in Boost). But >actually this is precisely the most compelling thing about the library - it >reduces code >that traditionally can be quite difficult into fragments such as those >shown. Shalom From what you've shown it looks like the duplication of data members in serialization methods is not needed. Some have been struggling to eliminate the need for that duplication -- http://preview.tinyurl.com/6kpx8t . Maybe more details about codec_object<> would be helpful. Brian Wood Ebenezer Enterprises www.webEbenezer.net

3 4

promote "unwrap" to ref.hpp
by Ronald Garcia 27 May '08

27 May '08

Hi all, boost::reference_wrapper exists at the top-level of boost (in boost/ ref.hpp), but that header provides no way to unwrap a reference_wrapper. There are two implementations floating around of "unwrap", one in boost.bind's implementation details, and one in boost.mpl's implementation details. Is there any problem with providing a version of unwrap in ref.hpp? ron

4 8