September 2010 - Boost - lists.preview.boost.org

Status of FSM viewer
by Michal Sojka 08 Sep '10

08 Sep '10

Dear Andreas and others, we are looking for a solution to visualize FSMs in our robotic applications. Before starting the development of our own tool I'd like to ask whether there exists something able to visualize Boost.Statecharts FSMs. I was only able to find the following GSOC project: http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Google_Summe… http://www.boost.org/community/gsoc_2006_boost_overview.html#accepted_proje… and its result: http://svn.boost.org/svn/boost/sandbox/SOC/2006/fsm-viewer/trunk/src/ but in my quick tests it produced only empty figures. I believe that after some debugging I could make it work. My question is whether the development of this tool continues or whether there are some other tools. In case of negative answers, do you have any suggestions for the development of the new tool? Currently, we consider the development of a GCC plugin which will generate dot (graphviz) source. Best regards, Michal Sojka

1 0

Adam/Eve DSEL - Re: De Bruijn Bind (alternate bind syntax) Interest?
by Gottlob Frege 08 Sep '10

08 Sep '10

On Tue, Sep 7, 2010 at 1:24 PM, Smith, Jacob N <jacob.n.smith(a)intel.com> wrote: > > For an Adam/Eve DSEL in C++ we used this syntax: > > sheet save_file = > "save_file" == sheet > { > interface == section > { > var{"file_name"} == [](arg_map args){ return any(""); }, > var{"file_type"} == "txt", > (var{"password"} <= (var{"file_type"}, var{"password1"})) == > [](arg_map args) > { > return args.get<string>("file_type") == "txt" ? any("") : args["password1"]; > } > // more constraints > }, > output == section > { > // more constraints > }, > invariant == section > { > // more constraints > } > }; > Interesting. At Adobe we had a DSEL that looked something like (from memory): dialog(name = "Clipping Path") [ column(child_horizontal = align_fill) [ popup(name = "Path:", bind = &path, items = list [ item(name = "None", value = empty), item(name = "Path 1", value = 1), item(name = "Path 2", value = 2) ]), edit_number(name = "Flatness:", digits = 9, bind = &flatness) ], button(name = "OK", dephault = true, bind = &result) ]; Or something like that. Of course we didn't have C++0x at the time. Tony

1 0

Re: [boost] [msm] Boost MPL vector limit size exceeded
by Christophe Henry 07 Sep '10

07 Sep '10

>Here is a little example I use favor_compile_time, (see attachment) > >But msm still tries to fold recursively all sub state machines states >in to 1 big mpl vector. > >As you said in your last mail : > >>Yes, it would work but I think I remember you mentioning boost::any >>not being an option. If boost::any and the performance loss are >>acceptable for you then it would probably help. > >It would be possible to overcome this problem by using >favor_compile_time but it seems apparently not :(. It seems I didn't read correctly and thus gave an unclear answer. The problem I was talking about was the compile-time. So, if you allow, 2nd try: The favor_compile_time policy will still fold all the transitions inside a big mpl::vector, at least for the moment. I already started a new version of the policy improving this too but didn't finish it yet as the problem I was trying to improve (Jeff Flinn's exploding compile-time) went away so there was not a big demand for it. So, again, yes, the policy still makes one big vector, but it's not so much of a problem any more because the compile-times are greatly reduced by the policy. So, increasing the mpl::vector size does not hurt so much any more. Sorry for the confusion. Regards, Christophe

1 0

Re: [boost] [msm] Boost MPL vector limit size exceeded
by Christophe Henry 07 Sep '10

07 Sep '10

>> I personally defined myself headers up to 100. It's pretty easy actually. > Can you provide us the files that we don't have to do it ? We did it for 60 now. Sure (provided this is not rejected). I tried with 1.42. > We have problems that the compiler runs out of heap if we include too > many transitions as well. Juraj told me not long ago (but too late to make it into the 1.44 doc) that specifying LESS heap for VC (I think it is the Zm option) actually works better than increasing it. You could try it and see if that helps. > But our state machines are complex in our interfaces we have over 100 > different events. > We have several main state machines whit 3 level deep substate > machines and around 10 substate machines altogether at the moment, > but actually as our feature list is growing with the current design > we are planning to add more and more substate machines to the system. > So we run out of 50 transitions in the main state machine pretty fast.:(. > > If we would split the implementation to several main sate machines we > would loose the nice features we gain with hierarchical approach. > > Is it not possible to use favor_compile_time feature or something > similar as described in > http://www.boost.org/doc/libs/1_44_0/libs/msm/doc/HTML/ch03s05.html#d0e3642 > to avoid using the performance improvement and have the substate > machines to dispatch all events again in them this would allow as to > continue with our implementation because none of our transaction table > contains more than 50 entries alone. Yes, it would work but I think I remember you mentioning boost::any not being an option. If boost::any and the performance loss are acceptable for you then it would probably help. Regards, Christophe

2 3

Status of Python 3 support for Boost.MPI?
by Steve M. Robbins 07 Sep '10

07 Sep '10

Hi, I just tried to build boost 1.44 using Python 3.1 and two files in mpi failed to compile. Is this easy to fix? "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -g -D_REENTRANT -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_MPI_DYN_LINK=1 -DBOOST_MPI_PYTHON_DYN_LINK=1 -DBOOST_PYTHON_DYN_LINK=1 -DNDEBUG -I"." -I"/usr/include/python3.1" -I"/usr/lib/openmpi/include" -I"/usr/lib/openmpi/include/openmpi" -c -o "bin.v2/libs/mpi/build/gcc-4.4.5/release/debug-symbols-on/python-3.1/threading-multi/python/datatypes.o" "libs/mpi/src/python/datatypes.cpp" In file included from ./boost/python/detail/wrap_python.hpp:50, from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/mpi/python/serialize.hpp:25, from libs/mpi/src/python/datatypes.cpp:13: /usr/include/python3.1/pyconfig.h:1117:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/c++/4.4/x86_64-linux-gnu/bits/os_defines.h:39, from /usr/include/c++/4.4/x86_64-linux-gnu/bits/c++config.h:243, from /usr/include/c++/4.4/bits/stl_algobase.h:60, from /usr/include/c++/4.4/bits/stl_tree.h:62, from /usr/include/c++/4.4/map:60, from /usr/lib/openmpi/include/openmpi/ompi/mpi/cxx/mpicxx.h:36, from /usr/lib/openmpi/include/mpi.h:1886, from ./boost/mpi/config.hpp:20, from ./boost/mpi/python/config.hpp:15, from ./boost/mpi/python/serialize.hpp:23, from libs/mpi/src/python/datatypes.cpp:13: /usr/include/features.h:158:1: warning: this is the location of the previous definition In file included from ./boost/python/detail/wrap_python.hpp:50, from ./boost/python/detail/prefix.hpp:13, from ./boost/python/ssize_t.hpp:9, from ./boost/python/object.hpp:8, from ./boost/mpi/python/serialize.hpp:25, from libs/mpi/src/python/datatypes.cpp:13: /usr/include/python3.1/pyconfig.h:1139:1: warning: "_XOPEN_SOURCE" redefined In file included from /usr/include/c++/4.4/x86_64-linux-gnu/bits/os_defines.h:39, from /usr/include/c++/4.4/x86_64-linux-gnu/bits/c++config.h:243, from /usr/include/c++/4.4/bits/stl_algobase.h:60, from /usr/include/c++/4.4/bits/stl_tree.h:62, from /usr/include/c++/4.4/map:60, from /usr/lib/openmpi/include/openmpi/ompi/mpi/cxx/mpicxx.h:36, from /usr/lib/openmpi/include/mpi.h:1886, from ./boost/mpi/config.hpp:20, from ./boost/mpi/python/config.hpp:15, from ./boost/mpi/python/serialize.hpp:23, from libs/mpi/src/python/datatypes.cpp:13: /usr/include/features.h:160:1: warning: this is the location of the previous definition libs/mpi/src/python/datatypes.cpp: In function ‘void boost::mpi::python::export_datatypes()’: libs/mpi/src/python/datatypes.cpp:20: error: ‘PyInt_Type’ was not declared in this scope In file included from ./boost/function/detail/prologue.hpp:17, from ./boost/function/function_template.hpp:13, from ./boost/function/detail/maybe_include.hpp:13, from ./boost/function/function0.hpp:11, from ./boost/python/errors.hpp:13, from ./boost/python/handle.hpp:11, from ./boost/python/converter/arg_to_python_base.hpp:7, from ./boost/python/converter/arg_to_python.hpp:14, from ./boost/python/call.hpp:15, from ./boost/python/object_core.hpp:14, from ./boost/python/object.hpp:9, from ./boost/mpi/python/serialize.hpp:25, from libs/mpi/src/python/datatypes.cpp:13: ./boost/function/function_base.hpp: In static member function ‘static void boost::detail::function::functor_manager_common<Functor>::manage_small(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>]’: ./boost/function/function_base.hpp:360: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, mpl_::true_) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>]’ ./boost/function/function_base.hpp:406: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, boost::detail::function::function_obj_tag) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>]’ ./boost/function/function_base.hpp:434: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manage(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>]’ ./boost/function/function_template.hpp:913: instantiated from ‘void boost::function3<R, T1, T2, T3>::assign_to(Functor) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>, R = void, T0 = boost::mpi::packed_oarchive&, T1 = const boost::python::api::object&, T2 = const unsigned int]’ ./boost/function/function_template.hpp:722: instantiated from ‘boost::function3<R, T1, T2, T3>::function3(Functor, typename boost::enable_if_c<boost::type_traits::ice_not::value, int>::type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<bool>, R = void, T0 = boost::mpi::packed_oarchive&, T1 = const boost::python::api::object&, T2 = const unsigned int]’ ./boost/mpi/python/serialize.hpp:276: instantiated from ‘void boost::python::detail::direct_serialization_table<IArchiver, OArchiver>::register_type(const T&, PyTypeObject*) [with T = bool, IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive]’ ./boost/mpi/python/serialize.hpp:389: instantiated from ‘void boost::python::register_serialized(const T&, PyTypeObject*) [with IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive, T = bool]’ ./boost/mpi/python/serialize.hpp:534: instantiated from ‘void boost::mpi::python::register_serialized(const T&, PyTypeObject*) [with T = bool]’ libs/mpi/src/python/datatypes.cpp:21: instantiated from here ./boost/function/function_base.hpp:321: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp:325: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp: In static member function ‘static void boost::detail::function::functor_manager_common<Functor>::manage_small(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>]’: ./boost/function/function_base.hpp:360: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, mpl_::true_) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>]’ ./boost/function/function_base.hpp:406: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, boost::detail::function::function_obj_tag) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>]’ ./boost/function/function_base.hpp:434: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manage(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>]’ ./boost/function/function_template.hpp:913: instantiated from ‘void boost::function3<R, T1, T2, T3>::assign_to(Functor) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>, R = void, T0 = boost::mpi::packed_iarchive&, T1 = boost::python::api::object&, T2 = const unsigned int]’ ./boost/function/function_template.hpp:722: instantiated from ‘boost::function3<R, T1, T2, T3>::function3(Functor, typename boost::enable_if_c<boost::type_traits::ice_not::value, int>::type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<bool>, R = void, T0 = boost::mpi::packed_iarchive&, T1 = boost::python::api::object&, T2 = const unsigned int]’ ./boost/mpi/python/serialize.hpp:276: instantiated from ‘void boost::python::detail::direct_serialization_table<IArchiver, OArchiver>::register_type(const T&, PyTypeObject*) [with T = bool, IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive]’ ./boost/mpi/python/serialize.hpp:389: instantiated from ‘void boost::python::register_serialized(const T&, PyTypeObject*) [with IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive, T = bool]’ ./boost/mpi/python/serialize.hpp:534: instantiated from ‘void boost::mpi::python::register_serialized(const T&, PyTypeObject*) [with T = bool]’ libs/mpi/src/python/datatypes.cpp:21: instantiated from here ./boost/function/function_base.hpp:321: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp:325: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp: In static member function ‘static void boost::detail::function::functor_manager_common<Functor>::manage_small(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>]’: ./boost/function/function_base.hpp:360: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, mpl_::true_) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>]’ ./boost/function/function_base.hpp:406: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, boost::detail::function::function_obj_tag) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>]’ ./boost/function/function_base.hpp:434: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manage(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>]’ ./boost/function/function_template.hpp:913: instantiated from ‘void boost::function3<R, T1, T2, T3>::assign_to(Functor) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>, R = void, T0 = boost::mpi::packed_oarchive&, T1 = const boost::python::api::object&, T2 = const unsigned int]’ ./boost/function/function_template.hpp:722: instantiated from ‘boost::function3<R, T1, T2, T3>::function3(Functor, typename boost::enable_if_c<boost::type_traits::ice_not::value, int>::type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_saver<double>, R = void, T0 = boost::mpi::packed_oarchive&, T1 = const boost::python::api::object&, T2 = const unsigned int]’ ./boost/mpi/python/serialize.hpp:276: instantiated from ‘void boost::python::detail::direct_serialization_table<IArchiver, OArchiver>::register_type(const T&, PyTypeObject*) [with T = double, IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive]’ ./boost/mpi/python/serialize.hpp:389: instantiated from ‘void boost::python::register_serialized(const T&, PyTypeObject*) [with IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive, T = double]’ ./boost/mpi/python/serialize.hpp:534: instantiated from ‘void boost::mpi::python::register_serialized(const T&, PyTypeObject*) [with T = double]’ libs/mpi/src/python/datatypes.cpp:22: instantiated from here ./boost/function/function_base.hpp:321: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp:325: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp: In static member function ‘static void boost::detail::function::functor_manager_common<Functor>::manage_small(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>]’: ./boost/function/function_base.hpp:360: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, mpl_::true_) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>]’ ./boost/function/function_base.hpp:406: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, boost::detail::function::function_obj_tag) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>]’ ./boost/function/function_base.hpp:434: instantiated from ‘static void boost::detail::function::functor_manager<Functor>::manage(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>]’ ./boost/function/function_template.hpp:913: instantiated from ‘void boost::function3<R, T1, T2, T3>::assign_to(Functor) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>, R = void, T0 = boost::mpi::packed_iarchive&, T1 = boost::python::api::object&, T2 = const unsigned int]’ ./boost/function/function_template.hpp:722: instantiated from ‘boost::function3<R, T1, T2, T3>::function3(Functor, typename boost::enable_if_c<boost::type_traits::ice_not::value, int>::type) [with Functor = boost::python::detail::direct_serialization_table<boost::mpi::packed_iarchive, boost::mpi::packed_oarchive>::default_loader<double>, R = void, T0 = boost::mpi::packed_iarchive&, T1 = boost::python::api::object&, T2 = const unsigned int]’ ./boost/mpi/python/serialize.hpp:276: instantiated from ‘void boost::python::detail::direct_serialization_table<IArchiver, OArchiver>::register_type(const T&, PyTypeObject*) [with T = double, IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive]’ ./boost/mpi/python/serialize.hpp:389: instantiated from ‘void boost::python::register_serialized(const T&, PyTypeObject*) [with IArchiver = boost::mpi::packed_iarchive, OArchiver = boost::mpi::packed_oarchive, T = double]’ ./boost/mpi/python/serialize.hpp:534: instantiated from ‘void boost::mpi::python::register_serialized(const T&, PyTypeObject*) [with T = double]’ libs/mpi/src/python/datatypes.cpp:22: instantiated from here ./boost/function/function_base.hpp:321: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp:325: warning: dereferencing type-punned pointer will break strict-aliasing rules ...failed gcc.compile.c++ bin.v2/libs/mpi/build/gcc-4.4.5/release/debug-symbols-on/python-3.1/threading-multi/python/datatypes.o... and "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -g -D_REENTRANT -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_MPI_DYN_LINK=1 -DBOOST_MPI_PYTHON_DYN_LINK=1 -DBOOST_PYTHON_DYN_LINK=1 -DNDEBUG -I"." -I"/usr/include/python3.1" -I"/usr/lib/openmpi/include" -I"/usr/lib/openmpi/include/openmpi" -c -o "bin.v2/libs/mpi/build/gcc-4.4.5/release/debug-symbols-on/python-3.1/threading-multi/python/py_environment.o" "libs/mpi/src/python/py_environment.cpp" libs/mpi/src/python/py_environment.cpp: In function ‘bool boost::mpi::python::mpi_init(boost::python::list, bool)’: libs/mpi/src/python/py_environment.cpp:53: error: cannot convert ‘char**’ to ‘wchar_t**’ for argument ‘2’ to ‘void PySys_SetArgv(int, wchar_t**)’ ...failed gcc.compile.c++ bin.v2/libs/mpi/build/gcc-4.4.5/release/debug-symbols-on/python-3.1/threading-multi/python/py_environment.o... Thanks, -Steve

1 0

Re: [boost] Domagoj Saric: "Re: [function] invoking without requiring boost::throw_exception"
by Peter Myerscough-Jackopson 07 Sep '10

07 Sep '10

From: "Peter Myerscough-Jackopson" <peter.myerscough-jackopson_at_[hidden]> Sent: Thursday, September 02, 2010 5:36 PM > I am using boost::function on an embedded platform, which requires me to > not use exceptions, and as commented in the thread associated with > > http://article.gmane.org/gmane.comp.lib.boost.devel/195351 > > I am checking that the function object contains a function before > calling it. There is therefore no need for the invocation of the > function to check if it is valid, but also there is no method circumvent > this checking, and therefore my program requires the definition of > boost::throw_exception, when really it is not needed. This is a concern > because I intend on compiling my code into a library and do not wish to > require the user to define boost::throw_exception, especially when I am > guaranteeing it isn't going to be called from this site. I liked the > idea of a templated NOP for the function library, but at the very least > an unchecked invocation method would be great, or a nop-if-empty > invocation method would be useful. If you are certain that neither you nor your users use or will use boost::throw_exception (to actually handle some other cases 'exceptional' cases in other parts of boost) then you can provide the definition yourself. I cannot know whether my users will invoke other parts of boost that may make use of boost::throw_exception because my code is being compiled up and provided as a (application support) library. Also, since I know that I will never call the function object when it is null, I don’t want to burden my users by requiring them to define a function that will never be called from my code. As it is currently I am resorting to mimicking the code that occurs after the check and I have put a check in to ensure the library is compiled with an exact version of boost, a poor/bad/nightmare work around, but it means my users don’t have to define throw_exception. As others have noted, a common idiom for using a boost function object is to check if it is non-empty prior to calling it, is it an unreasonable extension to add this call? I am aware TR1 has subsumed “function” and so it is probably not possible remove the if-clause, but adding an unchecked invoke has significant benefits, [unchecked_invoke(), might be a better name than purely invoke()]. Peter Dr Peter Myerscough-Jackopson - Principal Engineer Tel: +44 (0)23 8076 7808 Fax: +44 (0)23 8076 0602 Web: http://www.macltd.com/ <BLOCKED::http://www.macltd.com/> Email: peter.myerscough-jackopson(a)macltd.com <mailto:peter.myerscough-jackopson@macltd.com> MULTIPLE ACCESS COMMUNICATIONS LIMITED is a company registered in England at Delta House, The University of Southampton Science Park, Southampton, SO16 7NS, United Kingdom with Company Number 1979185 and VAT Number GB 411942866

4 3

[testing] strange failure
by Emil Dotchevski 06 Sep '10

06 Sep '10

Anyone has any idea how to interpret this log? http://www.boost.org/development/tests/trunk/developer/output/Sandia-darwin… Should I also file a ticket for the testing framework? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

3 2

[array] Invalid data: accessing 'elems'
by Mateusz Loskot 06 Sep '10

06 Sep '10

Hi, I compile a small test program using Visual C++ 10.0 (Visual Studio 2010 Premium) with static code analysis turned on (option /analyze): #include <boost/array.hpp> int main() { typedef int T; // short, char, etc. boost::array<T, 2> x; T a = x[0]; } and whichever integer type I use for T, the analyser throws similar reports every time: 1>------ Build started: Project: boost_array_test, Configuration: Debug Win32 ------ 1> boost_array_test.cpp 1>g:\workshop\boost\boost_test\array\boost_array_test.cpp(5): warning C4189: 'a' : local variable is initialized but not referenced 1>g:\dev\boost\_svn\trunk\boost\array.hpp(111): warning C6385: Invalid data: accessing 'elems', the readable size is '8' bytes, but '12' bytes might be read: Lines: 110, 111 1> G:\dev\boost\_svn\trunk\boost/array.hpp(109) : while compiling class template member function 'int &boost::array<T,N>::operator [](boost::array<T,N>::size_type)' 1> with 1> [ 1> T=int, 1> N=0x2 1> ] 1> boost_array_test.cpp(4) : see reference to class template instantiation 'boost::array<T,N>' being compiled 1> with 1> [ 1> T=int, 1> N=0x2 1> ] 1> boost_array_test.vcxproj -> G:\workshop\boost\boost_test\array\Debug\boost_array_test.exe ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== Shall I report a ticket? No warnings are reported for the std::array provided with Visaul C++ 10.0. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 3

[program options] msvc warning suppression
by Jürgen Hunold 06 Sep '10

06 Sep '10

Hi Volodya, I've finally started using Boost.ProgramOptions and found some annoying msvc warnings. Okay to apply the attached patch ? Those warnings are totally useless, as templates can not have a "dll- interface". Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

3 3

[multi_index] Multi-Index as fast running median solver
by Ryan Fogarty 05 Sep '10

05 Sep '10

I'm hoping to use multi-index' ordered_index (non-unique) to do a fast running median. Given a set of M numbers and a window size of N compute the medians (for each of M - N + 1 solutions). Here is my solution: template<typename T> class FastMedianSolver { private: // boost::multi_index does most of the heavy lifting for this FastMedianSolver. // This index is given both "sequence" and "tree" semantics. typedef typename boost::multi_index_container< T,indexed_by<sequenced<>,ordered_non_unique<identity<T> > > > SortedList; typedef typename SortedList::template nth_index<0> SeqIndex; typedef typename SeqIndex::type SIndex; typedef typename SortedList::template nth_index<1> TreeIndex; typedef typename TreeIndex::type TIndex; SortedList mQueue; const size_t mSize; const size_t mHalfSize; public: typedef typename SIndex::iterator iterator; /** * Create a FastMedianSolver with queue size as argument * * @param size - size of the queue. */ // Note: fast divide by 2 is: X >> 1 FastMedianSolver(size_t size) : mSize(size), mHalfSize(size >> 1) {} /** * insert a value into the median queue */ void insert(const T& value) { mQueue.push_front(value); if(mQueue.size() > mSize) mQueue.pop_back(); } /** * Get the median for the elements within the queue. Note: * the algorithm requires a full queue, o.w. may throw an exception. */ const T& getMedian() { // Ensure queue is filled up before we ask for median! assert((mQueue.size() >> 1) == mHalfSize); typename TIndex::iterator tNdx(mQueue.get<1>().begin()); // Now grab the median element // Note that unfortunately the root() node is not exposed so the only way to get the central node // is to iterate to it :( (this will incur a O(N) operation on this function which is a little unfortunate for(int i = 0; i < mHalfSize; ++i,++tNdx); // This would be better if it were available and accurate! // typename TIndex::iterator tNdx(mQueue.get<1>().beginAtRoot()); // TODO: Check if we need to average the output of 2 positions if mSize is even return *tNdx; } }; Note, that to get to the central node I just iterate the ordered list half way through set: for(int i = 0; i < mHalfSize; ++i,++tNdx); However, what I was hoping was that I could get the root node directly. ordered_index doesn't expose an iterator to root() so I put it in ordered_index.hpp as: iterator beginAtRoot(){return make_iterator(root());} However, this isn't working out because the tree isn't always balanced. My question is 2-fold is there any way to force the internal red-black tree to stay balanced; and secondly, would that have an appreciable performance penalty. Thank you, Ryan

2 1