- Boost - lists.boost.org

[xpressive] regex_replace() issue.
by Robert Dailey 17 Mar '08

17 Mar '08

Hi, Currently I'm using Boost.Xpressive to search a string for variables that will be replaced by localized utf-8 encoded strings, in the format of $(variable_name). Because of this, I don't think I can simply use regex_replace(), since it takes a common regex that will be used to replace all matches, when in my case each match requires a special, unique replacement. Is there a way of doing this using Boost.Xpressive, or do I need to use a different component in the boost library? Is there a Xpressive 'replace' function that takes a functor, perhaps, and for each match it calls the function object and replaces the match with the return value of the functor? An example of a string that I'll be searching is below: "This string $(variable1) has localized $(var2) text interleaved for no $(reason)" In the string above, we have 3 variables. Each variable will reference a string in a localization table, which will then be used to replace the variable itself. Any help is greatly appreciated. Thanks.

5 15

[filesystem] not_found_error unresolved external symbol on windows platform
by Alexander Arhipenko 17 Mar '08

17 Mar '08

Hi, guys! I had following problem when using boost::filesystem dynamically linked on windows platform: unresolved external symbol boost::filesystem::not_found_error. (By the way, this issue was raised up on users list some time ago, but had no resolution). According to dumpbin utility, mentioned symbol resides in boost_filesystem binary, so, I guess, there is some problem with macro magics (__declspec(dllimport/dllexport) ) in header file (operations.hpp). I'm building test application using Boost.Build: Boost.Build V2 (Milestone 11) Boost.Jam 03.1.16 and boost 1.34.1. Compiler is MSVC 9, but problem is reproducible on MSVC 8. The attached patch fixes the problem by defining BOOST_FILESYSTEM_DYN_LINK in usage requirements (in boost.filesystem's Jamfile.v2), but I'm wondering 1. why all the other symbols are successfully imported when mentioned macro is not defined 2. and why this macro wasn't defined in usage requirements by the author of the library. Could you please shed a light on this issue or correct me if I'm doing something wrong. Thanks. Sasha P.S. In attach there are minimal project that reproduces the problem and patch that fixes the problem.

2 2

[quickbook][1.35]
by Daniel James 16 Mar '08

16 Mar '08

Hi, There are two copies of the quickbook documentation in the release candidate - one in 'boost/tools/quickbook/doc/html' and one in the main generated documentation. The one in the generated documentation has a few broken links because they're releative to the 'tools' location. So can I remove it from the generated documentation from this release, and then if it needs to be added to the generated documentation, we can get that working for the next release? Daniel

3 2

Features list for v1.34
by Balasubramanyam, Shivakumar 16 Mar '08

16 Mar '08

Hi, Could someone point me to a link that provides features added or major bugs fixed for a major boost release. Currently we are using 1.32 and I would like to know if we need to upgrade to 1.34 releases. I tried in the boost.org but could not find a link. Thanks, Shiva

3 2

Attention: all authors of new libraries for 1.35.
by John Maddock 16 Mar '08

16 Mar '08

Could you please check that the descriptions here: http://beta.boost.org/users/news/version_1_35_0 are correct. If you would like to expand on the descriptions given then now is the time to do so! Thanks, John.

4 5

Review Request: Dataflow.Signals
by Stjepan Rajko 16 Mar '08

16 Mar '08

Hello, I would like to request a formal review of the Dataflow.Signals layer of the Dataflow library. The Dataflow.Signals layer provides dataflow functionality based on function calls (using Boost.Signals), and is a result of the Signal Networks GSoC project from 2007. (The other layers of the Dataflow library are not quite ready, so for now I'd like to keep them as implementation details and/or examples of the Dataflow.Signals layer, and submit them for review at a later point.) The documentation for the Dataflow library is located at: http://dancinghacker.com/code/dataflow/ Version 0.9.0 has been uploaded to the vault, in the Dataflow directory. There are a few more things I plan to add before the library comes up for review, especially regarding the documentation and motivating examples. Description: The Dataflow library is a generic library for dataflow programming. Dataflow programs can typically be expressed as a graph in which vertices represent components that process data, and edges represent the flow of data between the components. As such, dataflow programs can be easily reconfigured by changing the components and/or the connections. The Dataflow.Signals layer provides dataflow functionality based on function calls - which is one of the fundamental ways of dataflow in C++. For its data transport mechanism, Dataflow.Signals uses Boost.Signals which can be used to make lasting dataflow connections based on function calls. Dataflow.Signals provides the following to facilitate signals-based dataflow networks: * A number of useful general-purpose components, and building blocks for implementing new components. * Various free functions and operators for connecting and using components. Kind regards, Stjepan

5 20

[fusion] Instantiating elements of nested sequences
by Carlos Rafael Giani 16 Mar '08

16 Mar '08

Hi, I want to store boost signals in fusion sequences. This does not work directly, since signals are noncopyable. I figured I could use shared_ptr's of the signals, and all that needs to be done is to iterate through the sequences, instantiate objects, and assign them to the shared_ptr's. These are the structures for the signals: template < typename Element > struct element_signals { typedef boost::signal < void(model const &, Element const &) > event_signal_t; typedef boost::signal < void(model const &, Element const &, std::vector < std::string > const &) > modified_signal_t; typedef boost::fusion::vector < std::tr1::shared_ptr < event_signal_t >, // add std::tr1::shared_ptr < event_signal_t >, // remove std::tr1::shared_ptr < modified_signal_t > // modified > signals_t; typedef boost::fusion::pair < Element, signals_t > signals_pair_t; }; typedef boost::fusion::map < element_signals < vertex_iterator > ::signals_pair_t, element_signals < edge_iterator > ::signals_pair_t > signals_t; Now, I am trying to do something like this pseudo-code: signals_t signals; for_each(signals, for_each(_1, _1 = typeof(_1)(new typeof(_1)::element_type) ) ); Problems: 1) How do I get the type of the current element in the for_each loop without resorting to functors? 2) I tried to use a MPL placeholder for the _1 in the outer for_each loop, but it didn't seem to work. Does Fusion have its own placeholders, or what am I missing? Regards,

1 0

[1.35][GIL] No copyright/license on docs?
by John Maddock 16 Mar '08

16 Mar '08

Currently the biggest single group of failures in the inspection report comes from GIL: http://mysite.verizon.net/beman/inspect.html#gil Is there any easy way we can regenerate this documentation with an appropriate license declaration? John.

2 1

[proto] comments on documentation #2
by Markus Werle 15 Mar '08

15 Mar '08

Hi! <anecdote> This morning (6:45 CET) I was sitting at the breakfast table and was reading the printed PDF of proto docs. My little son (6 years old) entered the scene and the first question he asked was: "What kind of puzzle are you trying to solve?". Kids always have a keen sense of what's really going on ... </anecdote> Before I start nagging, I should say that a large subset of the docs are well-done, near perfect. The setup of the first chapters makes it easy to approach proto. But I got lost in the middle with transforms and that is a BadThing (TM), because those are the beasts everybody needs in order to get the maximum out of proto. The transform chapter leaves me with the same feeling I had 1998, 2 weeks after my decision to learn C++, when I was reading Stroustrup's TCPPL chapter about templates. I wish Vandevoorde/Josuttis would have written their book _before_ I had to use templates (and gcc). Same here: I beg for some step-by-step-by-example introduction right now. Nothing of this part of the docs reached my heart and mind. Without tiny little examples I am totally lost here. This serves well as reference documentation, but not as main entry point to a feature of a library. I will try to work through the examples now, but any introductory material appreciated here. Keep me informed about updates in that section, please. Minor issues: First of all: Expression Extensions can go a long way without transforms. So I would recommend to put this chapter in front of the one about transforms. Then introduce transforms later for those with the sword of metaprogramming knowledge and the will to survive. extends<> is useful even without transforms and so why not give it a chance before readers are drawn away by the more advanced, but horrible-to-catch features. Also it might make sense to show an example which uses std::algorithms like the original std::transform example in order to show the power of proto here. AFAICS _make_terminal drops in from heaven without introduction - right? Do we need that one? is terminal<>::type not equivalent? if yes, remove _make_terminal. ------------------------------------- The decltype stuff distracts from the key points. Unaware readers get into panik when seeing static references to types and a keyword yet not in C++. How about typedef ...implementation defined ... result_type; Then move the decltype stuff to the comment paragraph below the code as extra information. Also: why ::result_type and not ::type? Is this consistent with mpl? ----------- Could you provide a full (compilable) example for increment_ints? That would help education (though I feel like I got that one) Maybe even extend the example to an initialization action based on operator new ... ----------- sed -es,no temporaries!,no temporary vectors!,g Maybe state that there are no temporary vectors, but of course the integer 2 in stored as temporary in [2]. Also state that every modern compiler since intel's 8.1 is capable of optimizing that one away, so nobody should care, and then: Look ma! no template code on-board after optimization -> the abstraction penalty is zero! ----------------------------------------------------------- Now it is time to share some time with the kids. Read you later in this group ... Markus

2 4

[1.35][ASIO] Broken index.html
by John Maddock 15 Mar '08

15 Mar '08

The links to the ASIO docs from the main documentation index page is broken, likewise the forwarding HTML file in libs/asio also forwards to a non-existent file. So.... where have the docs moved to... or were they not committed? Thanks, John.

5 6