- Boost - lists.boost.org

_REGEX_BITMASK_OPS in boost?
by Arno Schödl 23 Sep '08

23 Sep '08

_REGEX_BITMASK_OPS is used in the regex library to define binary operators for bitmask enums. I need something similar. What is the preferred way to do it? Should _REGEX_BITMASK_OPS be moved to a more public place? TIA, Arno -- Dr. Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

1 0

[property tree] boost::filesystem::path
by Johan Råde 23 Sep '08

23 Sep '08

Currently there is a problem when you put and then get a boost::filesystem::path to/from a property tree. When you get the path, then the path is first read into a string. Then a stringstream is constructed, and the path is extracted from the stringstream. The problem is that when you extract a path from a stream and the path contains spaces, then the path is truncated at the first space. The solution may be to specialize struct boost::property_tree::detail::extractor for boost::filesystem::basic_path. Instead of using a stringstream you can directly convert a string to a path. --Johan Råde

1 1

[metagraph] mpl_graph is now useable
by Gordon Woodhull 23 Sep '08

23 Sep '08

Hello - I recently posted to the sandbox a decent refactoring of the mpl_graph part of the Metagraph libraries I'm working on. mpl_graph is bgl-like graph metadata & metafunctions. Now there are two implementations - an adjacency list and an incidence list. That is, you can supply metadata in either of those formats and get full graph API access through metafunctions. Depth first search is also provided. Each capability that you access causes the library to create the corresponding indexing for the graph - that is, you pay for generating the relevant efficient metadata structure whenever you use a capability (or roughly, a concept). I think that each of the two previously reviewed libraries, FSM and Dataflow, could possibly benefit from mpl_graph. For FSM, this could be a nice input format, e.g. by supplying state data in the vertex types, and event action in the edge types. For the statically-generated Dataflow which Stjepan mentioned (not the version which was reviewed), a metadata graph could also be a nice input format, from which it would be possible to generate the call graph somewhat directly. Note that this allows templated functions to be called in combinatorial ways, generating some pretty complex code from a simple graph. But I'm getting ahead of myself (again). The big point is that there are all kinds of graphs in our code and data: generating code and data from metadata graphs is thus something we want to do. I'll work up some documentation once I get the doc toolchain working - in the meantime, please look at the examples, sandbox/metagraph/libs/metagraph/example/ I intend to do some profiling to see the complexity of the compile- time speed - it's noticeable but tolerable for small examples, on gcc. On msvc++, it's kinda slow, getting up toward a minute for a couple of examples. I don't yet know if this technique is viable for large compile-time graphs. mpl_graph is the first layer of the Metagraph stuff I've been going on about. This is just compile-time metadata graphs: mpl_graph is not the actual Metagraph compile-and-runtime data structure which started me on this quest, it's what makes that possible. Gordon

1 0

[Signals] Build problem on Linux / ARM with GCC 3.4.4
by Tobias Oberstein 22 Sep '08

22 Sep '08

I'm trying to build Boost.Signals on a Debian-based (Nokia Maemo OS2008 Diablo) system which is using GCC 3.4.4 toolchain (CodeSourcery ARM 2005q3-2). Problem is when linking, I get duplicate symbol boost::exception_detail::make_clone<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >(boost::exception_detail::error_info_injector<boost::bad_weak_ptr> in trackable.o named_slot_map.o Details see below. Any hints? Thanks alot, tgo [sbox-DIABLO_ARMEL: ~/build/boost_1_36_0] > bjam --toolset=gcc --build-dir=/home/oberstet/tmp/boost --with-signals warning: Graph library does not contain optional GraphML reader. note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note: directories containing the Expat headers and libraries, respectively. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). ...patience... ...found 576 targets... ...updating 1 target... gcc.link.dll /home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/libboost_signals-gcc34-mt-1_36.so.1.36.0 /home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/named_slot_map.o:(.bss._ZZN5boost16exception_detail10make_cloneINS0_19error_info_injectorINS_12bad_weak_ptrEEEEEPNS0_10clone_baseERKT_E9bad_alloc[*boost::exception_detail::clone_base* boost::exception_detail::make_clone<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >(boost::exception_detail::error_info_injector<boost::bad_weak_ptr> const&)::bad_alloc]+0x0): multiple definition of `boost::exception_detail::clone_base* boost::exception_detail::make_clone<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >(boost::exception_detail::error_info_injector<boost::bad_weak_ptr> const&)::bad_alloc' /home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/trackable.o:(.bss._ZZN5boost16exception_detail10make_cloneINS0_19error_info_injectorINS_12bad_weak_ptrEEEEEPNS0_10clone_baseERKT_E9bad_alloc[boost::exception_detail::clone_base* boost::exception_detail::make_clone<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >(boost::exception_detail::error_info_injector<boost::bad_weak_ptr> const&)::bad_alloc]+0x0): first defined here collect2: ld returned 1 exit status "g++" -o "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/libboost_signals-gcc34-mt-1_36.so.1.36.0" -Wl,-h -Wl,libboost_signals-gcc34-mt-1_36.so.1.36.0 -shared -Wl,--start-group "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/trackable.o" "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/connection.o" "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/named_slot_map.o" "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/signal_base.o" "/home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/slot.o" -Wl,-Bstatic -Wl,-Bdynamic -lrt -Wl,--end-group -Wl,--strip-all -pthread ...failed gcc.link.dll /home/oberstet/tmp/boost/boost/bin.v2/libs/signals/build/gcc-3.4.4/release/threading-multi/libboost_signals-gcc34-mt-1_36.so.1.36.0... ...failed updating 1 target... [sbox-DIABLO_ARMEL: ~/build/boost_1_36_0] > g++ --version sbox-arm-linux-g++ (GCC) 3.4.4 (release) (CodeSourcery ARM 2005q3-2) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [sbox-DIABLO_ARMEL: ~/build/boost_1_36_0] >

3 10

Compiling boost with visual c++
by Sean Farrow 22 Sep '08

22 Sep '08

Hi: Wha is the earliest visual c++ compuler the boost trunk will compile under? Chers Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 3458 (20080921) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

5 4

[filesystem] basic_path::operator>> issue for paths with spaces
by Johan Råde 22 Sep '08

22 Sep '08

When a path that contains spaces is extracted from a text file using basic_path::operator>>, then the path is truncated at the first space. Maybe basic_path::operator<< should put quotes around the path and basic_path::operator>> strip the quotes (if any). --Johan Råde

4 9

[process] another draft
by Ilya Sokolov 22 Sep '08

22 Sep '08

I would like to present my draft of the Boost Process library. If you are interested (Boris?), you may find a zip archive named process-is-0.3.zip here: http://www.boostpro.com/vault/index.php?direction=0&order=&directory=Proces… The library was originally written by Julio M. Merino Vidal. I continued from this point in the Boost sandbox: http://svn.boost.org/svn/boost/sandbox/SOC/2006/process/trunk/ Currently it builds with msvc-9.0-express and gcc-3.4.4/cygwin. It is in experimental stage right now, so don't be surprised if most the of interfaces will change in the future. Ilya Sokolov

3 4

Building Boost libs on Scratchbox/ARM
by Tobias Oberstein 22 Sep '08

22 Sep '08

I needed some small patches for building the Boost libs on a Debian-based system which is using GCC 3.4.4 toolchain (CodeSourcery ARM 2005q3-2). Target devices are Nokia Internet Tablets. See attached patches. Q: To optimize for the target CPU, I added the following line to tools/build/v2/user-config.jam using gcc : : : <compileflags>-mcpu=arm1136jf-s <compileflags>-mfpu=vfp <compileflags>-mhard-float <compileflags>-mfloat-abi=softfp ; However, when building I only see gcc.compile.c++ as compile command. How do I know if the options are actually used? Thx, tgo

2 2

Request for Interest in eval
by Christian Hoermann 22 Sep '08

22 Sep '08

This is a request for interest in a C++ header-only eval library. The main aim of the library is to provide means for calling compiled C++ functions/methods/constructors from within a script (which does not have to be compiled). An eval script can take arguments from the compiled code, as well as return arbitrary values. In order to make a function/method/constructor work with the library, the user only has to mention it in an eval header file, which is not unlike a normal C++ header file. (Although, in an eval header, oftentimes just the name of the function/method is necessary, rather than the full prototype.) For example syntax, documentation and a proof of concept release, see http://eval.sourceforge.net . Note that the release is still very limited in functionality; conditionals, loops and most operators are not yet supported. So, would there be any interest in such a library? Christian

6 8

[fusion] discrepancy between std::accumulate and fusion::accumulate
by Stjepan Rajko 21 Sep '08

21 Sep '08

Hello, I just started playing with an abstracted accumulate function which can be called either with a fusion sequence or a range, and calls fusion::accumulate or std::accumulate as appropriate. In using it, I ran into an interesting discrepancy: std::accumulate expects binary functions which take the accumulator as the first argument and the sequence element as the second argument. fusion::accumulate expects the arguments in reverse. This discrepancy makes the abstraction unnecessarily complicated, because the binary function has to either be able to receive the arguments in either order, or be adapted (e.g., with bind) for one of the cases. Or, I'm just missing something :-) I guess I just wanted to point this out - perhaps it might be a useful thing to mention in the docs. BTW, MPL follows the standard library convention. Kind regards, Stjepan

3 3