- Boost-users - lists.boost.org

[ublas] bounded_vector redundant storage of size. (is this a bug?)
by johanngoetz 24 Oct '08

24 Oct '08

for small vectors (geometry vectors is what I have in mind) the bounded_vector and bounded_matrix look promising. Indeed, if I was only dealing with a handful of vectors at a time, this would be ideal. However, I am creating a fieldmap (of a magnetic field, say) which maps 3D vectors (position) to 3D vectors (the field). The likely size of this map is around a million points. This should correspond to 6 million numbers stored. However, if I have something like: std::map< ublas::bounded_vector<int, 3>, ublas::bounded_vector<float, 3> > Then the size is actually 8 million numbers stored since I am storing the size of each of the bounded_vectors. While access time to the map is still very fast, I find that reading in or creating such maps takes much more time than should be required. It seems to me that the advantage of having the size as a template parameter is: not needing to store it as a member variable. Therefore I would like to say this is a bug (do I have agreement?). Unfortunately, the only solution for ublas::bounded_vector I can think of would be a complete reimplementation of ublas::vector just with the size as a template parameter instead of a member variable. but maybe I don't know enough to suggest the proper way to handle such situations. Of course the same applies to ublas::bounded_matrix but the effect there is not as big and it is hard to imagine off-hand a huge array of matrices. --- Johann -- View this message in context: http://www.nabble.com/-ublas--bounded_vector-redundant-storage-of-size.-%28… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

XML optional field
by Emanuele Rocci 23 Oct '08

23 Oct '08

Hi AllI would like to build a configuration file for my application in XML.The Configuration files includes also optional sectionsi.e. there might be properties that are not required to be defined by the user. If I use BOOST serialization to load this file, the XML format seems to me that forces every field of the XML field to be REQUIRED. Do you know if with Boost serialization for XML there is some mechanismallowing or handling optional Xml field? Kind RegardsManu _________________________________________________________________ Tutto il mondo MSN a portata di clic! http://toolbar.msn.com/overview.aspx?loc=it-it

7 13

Boost 1.36 portability issues on FreeBSD 6.x?
by Alexander Sack 23 Oct '08

23 Oct '08

Hello: I have a FreeBSD 6.1 amd64 box and I'm running into various issues building boost on my platform. In no particular order: - libboost_prg_exec_monitor checks for a lot of optional signal codes (execution_monitor.ipp file) that FreeBSD 6.1 does not support AND FreeBSD 7 supports somewhat. I'm talking about the XSI codes for SIGCHLD, SIGILL, etc. in my /usr/include/sys/signal.h (amd64 tree but is also a problem on my x86 branch): e.g. #define ILL_ILLOPC 1 /* [XSI] illegal opcode */ #define ILL_ILLTRP 2 /* [XSI] illegal trap */ #define ILL_PRVOPC 3 /* [XSI] privileged opcode */ #define ILL_ILLOPN 4 /* [XSI] illegal operand -NOTIMP */ #define ILL_ILLADR 5 /* [XSI] illegal addressing mode -NOTIMP */ #define ILL_PRVREG 6 /* [XSI] privileged register -NOTIMP */ #define ILL_COPROC 7 /* [XSI] coprocessor error -NOTIMP */ #define ILL_BADSTK 8 /* [XSI] internal stack error -NOTIMP */ #define CLD_EXITED What's the best thing to do here? I've actually compiled against FreeBSD 7's signal.h just to get me through this but the fact is the kernel (trap.c) does not set these codes. Will this cause Boost to crap out on me during runtime? If so, is there a workaround since this seems like a real bug in portability? - SIGPOLL is not defined, its SIGIO (I can work around this) - The Boost build when doing its standard tests sets up the LD_LIBRARY_PATH on my box as: LD_LIBRARY_PATH=/usr/bin:/usr/lib:/usr/lib32:/usr/lib64 - ICU for FreeBSD is in /usr/include/local which causes the build.jam stuff to miss autodetecting it On a 64-bit machine, adding /usr/lib32 BREAKS not only the test but most natively compiled binaries - I had to move /usr/lib32 and rename it for some of the tests to work (like boost_std_no_locale) etc. I started a thread on Boost-Build but got no replies. I'm just wondering how portable the latest release of Boost is on FreeBSD? Btw, there are several files I had to patch within boost to even get it to build relatively far (and I haven't tried python support just yet). The current BSD port is 1.34 and has been that for a long time (there was a 1.35 release at some point in beta testing) but I would like to update it to 1.36 but need some guidance on the above. Any guidance would be much appreciated... Thanks! -aps

3 8

[phoenix] or [lamdba] Operating on containers of smart pointers.
by Raindog 23 Oct '08

23 Oct '08

I ran into a problem while cleaning up some old code. What I wanted to do was replace explicit for loops with some stl algorithms or BOOST_FOREACH. Below is the original function: |//in header file: ..snip typedef std::vector<Loki::SmartPtr<ADTChunk> > chunk_vec_t chunk_vec_t chunks; ..snip //in source file: uint32_t ADT::get_connectivity_data( std::vector< std::vector<uint8_t> > &output ) { output.resize(chunks.size()); for(chunk_vec_t::iterator it = chunks.begin(); it < chunks.end(); ++it) { uint32_t success = (*it)->get_connectivity_data(output[it-chunks.begin()]); } return TRUE; } I asked on a separate website for some possibilities of replacing this code with boost::lambda, and the following almost correct suggestion was given to replace the loop: ||std::for_each( chunks.begin(), chunks.end(), bind( &chunk_vec_t::value::type::get_connectivity_data, _1, output[ std::distance( _1, chunks.begn() ] ) ); The problem is that the above obviously does not compile, so I made some changes and came up with this: ||std::for_each( chunks.begin(), chunks.end(), bind( &chunk_vec_t::value_type::StoredType::get_connectivity_data, _1, output[ std::distance( &_1, &chunks[0] ) ] ) ); The problem with the above is that "||&chunk_vec_t::value_type::StoredType::get_connectivity_data|" causes the VC9 compiler to crash =( So I made this change: |std::for_each( chunks.begin(), chunks.end(), bind( &ADTChunk::get_connectivity_data, _1, output[ std::distance( _1, chunks.begin() ) ] ) ); But now I get an error with the call to std::distance not being able to discern the arguments due to ambiguity. Next I thought that I might be able to use zip_iterator to assist in dealing with both of the containers, and then I realized it used tuples, which then made me thing that extracting the iterators from the tuples is going to take a lot of boiler plate code itself. Which led me to settle with the following code that is concise and easily readable but will only work if chunks is a vector essentially: BOOST_FOREACH(chunk_vec_t::value_type it, chunks) { output[std::distance(&it, &chunks[0])] = it->get_connectivity_data(); } So, my final question is, given my above attempts, is there a way to do what the 1st and 5th(the one immediately above this line) code snippets do in a straight-forward manner using either boost::lambda, or, since it will be replaced eventually by phoenix v3, with phoenix v2? Thanks! | | |

4 5

compile problem of boost::accumulators
by Ivy Ye 23 Oct '08

23 Oct '08

hi, I am a newbie in this forum. I just installed boost and want to solve some statistic problems. My system is Windows Vista and compiler is MSVC 6.0 At first I try to compile the "hello world" program in the boost::accumulators user guide page, but I got some compiler errors: The program is #include <iostream> #include <boost/accumulators/accumulators.hpp> #include <boost/accumulators/statistics/stats.hpp> #include <boost/accumulators/statistics/mean.hpp> #include <boost/accumulators/statistics/moment.hpp> using namespace boost::accumulators; int main() { // Define an accumulator set for calculating the mean and the // 2nd moment ... accumulator_set<double, stats<tag::mean, tag::moment<2> > > acc; // push in some data ... acc(1.2); acc(2.3); acc(3.4); acc(4.5); // Display the results ... std::cout << "Mean: " << mean(acc) << std::endl; std::cout << "Moment: " << moment<2>(acc) << std::endl; return 0; } The error I get from compiler is s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(43) : error C2989: 'tag<T>' : template class has already been defined as a non-template class s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(43) : error C2908: explicit specialization; 'tag<T>' has already been instantiated from the primary template s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(43) : error C2988: unrecognizable template declaration/definition s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(48) : error C2989: 'tag<T>' : template class has already been defined as a non-template class s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(43) : see declaration of 'tag<T>' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(48) : error C2908: explicit specialization; 'tag<T>' has already been instantiated from the primary template s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(48) : error C2988: unrecognizable template declaration/definition s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(53) : error C2989: 'tag<T>' : template class has already been defined as a non-template class s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(48) : see declaration of 'tag<T>' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(53) : error C2908: explicit specialization; 'tag<T>' has already been instantiated from the primary template s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(53) : error C2988: unrecognizable template declaration/definition s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(107) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(107) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(108) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(108) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(109) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(109) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(110) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(110) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(111) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(111) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(112) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(112) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(113) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(113) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(114) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(114) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(115) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(115) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(116) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(116) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(117) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(117) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(119) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(119) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(120) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(120) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(121) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(121) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(122) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(122) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(123) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(123) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(124) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(124) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(126) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(127) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(128) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(129) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(137) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(139) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(141) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(143) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(145) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(147) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(149) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(151) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\numeric\functional_fwd.hpp(198) : error C2039: 'type' : is not a member of 'lazy_disable_if<struct boost::is_const<T>,struct ?? :: ?? >' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(82) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(82) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(98) : error C2182: '__formal' : illegal use of type 'void' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2143: syntax error : missing ';' before '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2501: 'apply' : missing storage-class or type specifiers s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2059: syntax error : ';' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2059: syntax error : '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(120) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(124) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(124) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(127) : error C2954: template definitions cannot nest s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2143: syntax error : missing ';' before '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2501: 'apply' : missing storage-class or type specifiers s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2086: 'apply' : redefinition s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2059: syntax error : ';' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2059: syntax error : '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(128) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2954: template definitions cannot nest s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2143: syntax error : missing ';' before '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2501: 'apply' : missing storage-class or type specifiers s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2086: 'apply' : redefinition s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2059: syntax error : ';' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2059: syntax error : '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2954: template definitions cannot nest s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2143: syntax error : missing ';' before '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2501: 'apply' : missing storage-class or type specifiers s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2086: 'apply' : redefinition s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2059: syntax error : ';' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2059: syntax error : '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'type' : is not a member of '`global namespace'' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2954: template definitions cannot nest s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2039: 'apply' : is not a member of 'mpl' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2143: syntax error : missing ';' before '<' s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : error C2501: 'apply' : missing storage-class or type specifiers s:\program files\boost\boost_1_36_0\boost\accumulators\accumulators_fwd.hpp(154) : fatal error C1003: error count exceeds 100; stopping compilation Error executing cl.exe. accExam.obj - 102 error(s), 0 warning(s) --------------------------- can someone tell me what is wrong? Many thanks, Ivy

4 3

[Spirit] Closure arg2 compiler error
by Anders Dalvander 23 Oct '08

23 Oct '08

Hi, I get a compiler error (cannot convert from 'const phoenix::nil_t' to 'int') when using arg2 of a two value closure. arg1 works fine, but not arg2. I don't understand what I have done wrong. Visual Studio 2005 SP1 boost 1.36.0 Anyone got any ideas? Best regards, Anders Dalvander Output: Compiling... SpiritClosureTest.cpp d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\operators.hpp(446) : error C2440: '=' : cannot convert from 'const phoenix::nil_t' to 'int' No user-defined-conversion operator available that can perform this conversion, or the operator cannot be called d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\operators.hpp(446) : while compiling class template member function 'int &phoenix::binary_operator<TagT,T0,T1>::eval(T0 &,const T1 &)' with [ TagT=phoenix::assign_op, T0=int, T1=phoenix::nil_t ] d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\operators.hpp(1017) : see reference to class template instantiation 'phoenix::binary_operator<TagT,T0,T1>' being compiled with [ TagT=phoenix::assign_op, T0=int, T1=phoenix::nil_t ] d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\composite.hpp(237) : see reference to class template instantiation 'phoenix::assign_op::result<T0,T1>' being compiled with [ T0=int, T1=phoenix::nil_t ] d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\composite.hpp(267) : see reference to class template instantiation 'phoenix::composite2_result<OperationT,TupleT,A,B>' being compiled with [ OperationT=phoenix::assign_op, TupleT=phoenix::tuple<>, A=phoenix::actor<phoenix::closure_member<0,phoenix::closure<int,int,phoenix::nil_t>>>, B=phoenix::actor<phoenix::argument<0>> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\actor.hpp(122) : see reference to class template instantiation 'phoenix::composite<OperationT,A,B,C>::result<TupleT>' being compiled with [ OperationT=phoenix::assign_op, A=phoenix::actor<phoenix::closure_member<0,phoenix::closure<int,int,phoenix::nil_t>>>, B=phoenix::actor<phoenix::argument<0>>, C=phoenix::as_actor<phoenix::nil_t>::type, TupleT=phoenix::tuple<> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\phoenix\actor.hpp(133) : see reference to class template instantiation 'phoenix::actor_result<ActorT,TupleT>' being compiled with [ ActorT=phoenix::composite<phoenix::assign_op,phoenix::actor<phoenix::closure_member<0,phoenix::closure<int,int,phoenix::nil_t>>>,phoenix::actor<phoenix::argument<0>>,phoenix::as_actor<phoenix::nil_t>::type>, TupleT=phoenix::tuple<> ] c:\documents and settings\anders\my documents\visual studio 2005\projects\spiritclosuretest\spiritclosuretest\spiritclosuretest.cpp(25) : see reference to class template instantiation 'phoenix::actor<BaseT>' being compiled with [ BaseT=phoenix::composite<phoenix::assign_op,phoenix::actor<phoenix::closure_member<0,phoenix::closure<int,int,phoenix::nil_t>>>,phoenix::actor<phoenix::argument<0>>,phoenix::as_actor<phoenix::nil_t>::type> ] c:\documents and settings\anders\my documents\visual studio 2005\projects\spiritclosuretest\spiritclosuretest\spiritclosuretest.cpp(16) : while compiling class template member function 'my_grammar::definition<ScannerT>::definition(const my_grammar &)' with [ ScannerT=boost::spirit::scanner<> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\non_terminal\impl\grammar.ipp(279) : see reference to class template instantiation 'my_grammar::definition<ScannerT>' being compiled with [ ScannerT=boost::spirit::scanner<> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\non_terminal\impl\grammar.ipp(298) : see reference to function template instantiation 'void boost::spirit::impl::call_helper<0>::do_<result_t,definition_t,ScannerT>(RT &,DefinitionT &,const ScannerT &)' being compiled with [ ScannerT=boost::spirit::scanner<>, RT=result_t, DefinitionT=definition_t ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\non_terminal\grammar.hpp(55) : see reference to function template instantiation 'boost::spirit::match<boost::spirit::nil_t> boost::spirit::impl::grammar_parser_parse<0,my_grammar,boost::spirit::parser_context<>,ScannerT>(const boost::spirit::grammar<DerivedT> *,const ScannerT &)' being compiled with [ ScannerT=boost::spirit::scanner<>, DerivedT=my_grammar ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\non_terminal\grammar.hpp(65) : see reference to function template instantiation 'boost::spirit::match<boost::spirit::nil_t> boost::spirit::grammar<DerivedT>::parse_main<ScannerT>(const ScannerT &) const' being compiled with [ DerivedT=my_grammar, ScannerT=boost::spirit::scanner<> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\impl\parser.ipp(30) : see reference to function template instantiation 'boost::spirit::match<boost::spirit::nil_t> boost::spirit::grammar<DerivedT>::parse<boost::spirit::scanner<>>(const ScannerT &) const' being compiled with [ DerivedT=my_grammar, ScannerT=boost::spirit::scanner<> ] d:\prog\boost_1_36_0\boost\spirit\home\classic\core\impl\parser.ipp(47) : see reference to function template instantiation 'boost::spirit::parse_info<IteratorT> boost::spirit::parse<const CharT*,DerivedT>(const IteratorT &,const IteratorT &,const boost::spirit::parser<DerivedT> &)' being compiled with [ IteratorT=const char *, CharT=char, DerivedT=my_grammar ] c:\documents and settings\anders\my documents\visual studio 2005\projects\spiritclosuretest\spiritclosuretest\spiritclosuretest.cpp(54) : see reference to function template instantiation 'boost::spirit::parse_info<IteratorT> boost::spirit::parse<char,DerivedT>(const CharT *,const boost::spirit::parser<DerivedT> &)' being compiled with [ IteratorT=const char *, DerivedT=my_grammar, CharT=char ] Source: #include <boost/spirit.hpp> #include <boost/spirit/phoenix/primitives.hpp> #include <iostream> struct result_closure : boost::spirit::closure<result_closure, int, int> { member1 res1; member2 res2; }; struct my_grammar : boost::spirit::grammar<my_grammar> { template <typename ScannerT> struct definition { explicit definition(const my_grammar& self) { using boost::spirit::ch_p; using boost::spirit::uint_p; using phoenix::var; using phoenix::arg1; using phoenix::arg2; exp = uint_p[exp.res1 = arg1] >> ch_p('-') >> uint_p[exp.res2 = arg1] ; root = exp[var(self.i) = arg2] // compiler error here if using arg2. ; // arg1 works fine though. } boost::spirit::rule<ScannerT, result_closure::context_t> exp; boost::spirit::rule<ScannerT> root; const boost::spirit::rule<ScannerT>& start() const { return root; } }; my_grammar(int& i_) : i(i_) { } int& i; }; int main() { int i; my_grammar g(i); if (parse("1-2", g).full) { std::cout << i << "\n"; } }

2 1

Asio timer - how to restart it?
by Peleg 23 Oct '08

23 Oct '08

Hello, I'm writing an Asio based serial port communication application. I've tried to use Asio timer as receive time out timer. The implementation consist of restarting the timer each time the receive event is called, , so it'll trigger only after time out duration with no receive event. The problem is that when I try to restart the timer, using expires_from_now(), the timer immediately triggers. I've written a simplified code that demonstrate this problem: #include <iostream> #include <boost/asio.hpp> #include <boost/thread.hpp> #include <boost/date_time/posix_time/posix_time.hpp> using namespace std; using namespace boost::posix_time; void delay(int sec) { boost::posix_time::ptime expire_time = second_clock::local_time() + boost::posix_time::seconds(sec); while(second_clock::local_time() < expire_time) ; } void on_time_out(const boost::system::error_code& ) { cout << second_clock::local_time() <<" Time out!" << endl; } int main() { boost::asio::io_service io; cout << second_clock::local_time() << " Starting timer" << endl; boost::asio::deadline_timer timer(io, boost::posix_time::seconds(5)); boost::thread thread(boost::bind(&boost::asio::io_service::run, &io)); timer.async_wait(on_time_out); delay(3); cout << second_clock::local_time() << " Restarting timer" << endl; timer.expires_from_now(boost::posix_time::seconds(5)); delay(12); return 0; } This code results the following output: 2008-Oct-23 13:22:59 Starting timer 2008-Oct-23 13:23:02 Restarting timer 2008-Oct-23 13:23:02 Time out! As you can see to on_time_out() is called immediately after expires_from_now() call, with no actual time out. How do I restart to timer in the right way? Thanks, Peleg -- View this message in context: http://www.nabble.com/Asio-timer---how-to-restart-it--tp20128401p20128401.h… Sent from the Boost - Users mailing list archive at Nabble.com.

4 6

question on boost::interprocess
by Markos.Perrakis＠tsx.com 23 Oct '08

23 Oct '08

I have created a shared memory segment with the boost::interprocess library and have created and populated a boost::interprocess::map in that segment. The key for the map is the boost::interprocess::string class. If I want to search for an element in the map I obviously have to supply the key for the element. Here is what I do: { std::string key; // assign here a value to key string object const Char_Alloc char_alloc( (shared_memory_segment_obj.get_segment_manager() ) ); boost::interprocess::string some_string( char_alloc ); some_string.assign( key.c_str() ); } where Char_Alloc is a suitable shared memory allocator for plain characters. As you can see from the code the key (the some_string object) for the map is created in local memory (in-process memory) but the contents of the string are allocated in shared memory. If two threads access this shared memory segment and execute the above code at the same time, is this thread safe? Will the two concurrent assign() statements use the same location in shared memory and cause overlaps? Or is the shared memory allocator smart enough to synchronize the two assign() calls and execute them sequencially? In case the shared memory allocator is not smart enough to guarantee synchronization can I use a boost::interprocess mutex for thread synchronization? Regards, Markos Perrakis -------------------------------------- NOTICE OF CONFIDENTIALITY This e-mail, including all materials contained in or attached to this e-mail, contains proprietary and confidential information solely for the internal use of the intended recipient. If you have received this email in error, please notify us immediately by return e-mail or otherwise and ensure that it is permanently deleted from your systems, and do not print, copy, distribute or read its contents. AVIS DE CONFIDENTIALIT� Le pr�sent courriel, y compris tous les documents qu'il contient ou qui y sont joints, renferme des renseignements exclusifs et confidentiels destin�s uniquement � l'usage interne du destinataire pr�vu. Si vous avez re�u le pr�sent courriel par erreur, veuillez nous aviser imm�diatement, notamment par retour de courriel, et vous assurer qu'il est supprim� de fa�on permanente de vos syst�mes; veuillez �galement vous abstenir d'imprimer, de copier, de distribuer ou de lire son contenu.

2 1

Boost.Asio uses not specified WSAGetLastError
by Yakov Olkhovskiy 23 Oct '08

23 Oct '08

I just have found that Boost.Asio returns wrapped WSAGetLastError code even on successfully executed ::connect (didn't check it for other functions). There is a problem with Norton Personal Firewall - looks like it performs some operation after successful connection and doesn't restore error variable in the DLL. As result on a second (and further) program's run WSAGetLastError returns code 2 (The system cannot find the file specified). After removing record of the program from "Norton Internet Security->Norton Internet Security->Personal Firewall->Program control" list, the program works once and then again returns error on further runs. Actually it looks like as an Asio fault, because WSAGetLastError is not specified on successful function execution.

1 1

[Graph] Dijkstra algorithms checks edge weight is positive: loss of generality ?
by Tristram Gräbener 23 Oct '08

23 Oct '08

Hello, I'm not very familiar yet with all boost::graph internals, but there is something that bothers me: I use a special weight_map (cost functions of my own), providing my own distance_combine. So WeightMap::value_type is CostFunction and DistanceMap::value_type is float The dijkstra algorithm checks if an edge has a positive weight ( boost/graph/dijkstra_shortest_paths.hpp lines 121 & 122 with version 1.36.0). However, it uses the distance_compare parameters where "argument types that match the value type of the DistanceMap property map" So it tries to compare my cost function against a float (which of course is not possible). Of course this test garanties the optimality of the algorithm, but it restricts the use to have the weight_map and the distance_map of the same type. Did I miss how to use custom weight_maps, or is it some special case that wasn't thought of ? For now I just commented out the check Thank you ! PS: a more general optimality condition is (sufficient, but I'm not sure if it's necessary) : the combine function has to be non decreasing : for a node u, and edge e = (u,v), the distance_map d and the weight map w distance_compare(d[u], distance_combine(d[u], w[e]) ) has to be true

2 5