- Boost - lists.boost.org

[asio] One more asio::ip::tcp::iostream question
by Gregory Dai 17 Oct '08

17 Oct '08

Does asio::ip::tcp::iostream support HTTPS? I'm very happy that it works for me using HTTP.

1 0

[algorithm][string] regex_finder examples
by Robert Dailey 17 Oct '08

17 Oct '08

Hi, I noticed that there are no examples for using regex_finder with find_iterator. I checked the test & example directories in libs, and also the documentation. I found nothing useful. Could someone provide a quick example? So far here is what I have, but it does not compile: *#include <iostream> #include <string> #include <boost/algorithm/string.hpp> #include <boost/algorithm/string_regex.hpp> #include <boost/regex.hpp> int main() { std::string queryKey = "/foo/bar//stuff/"; boost::find_iterator<std::string::iterator> keyIt( queryKey, boost::regex_finder( boost::regex( "/.*?" ) ) ); boost::find_iterator<std::string::iterator> end; for( ; keyIt != end; ++keyIt ) { std::cout << "\"" << *keyIt << "\"\t" << (*keyIt).size() << std::endl; } std::cout << std::endl; system( "pause" ); return 0; }*

2 1

[date_time] Library status?
by Andrey Semashev 17 Oct '08

17 Oct '08

The Boost.DateTime library is very useful, and it is unfortunate to admit that according to Trac report and personal experience, its current state is anything but good. There are long standing tickets, some of them are trivial to fix and have patches already attached. The most annoying ones are missing includes and name clashes (tickets 642, 1740, 1615, 2083, 2091 to name some of them). Is this library still maintained?

5 10

[Range] boost::begin() & end( ) for istream?
by Robert Jones 17 Oct '08

17 Oct '08

Is there any mechanism to have the boost.range algorithms iterate over a stream? Given typedef std::istream_iterator<int> in; std::for_each( in(std::cin), in(), std::cout << (_1 * 3) << " " ); can I write this using range algorithms? - Thanks, Rob.

3 5

[UUID] version v12
by Johannes Brunen 17 Oct '08

17 Oct '08

Hello Andy, I just did a small test with the latest uuid library from the vault. IMHO, I found a small error in file uuid.hpp (line 303): function hash_value must be inlined as it is not a template function. Additional is seems that the documentation is out of sync with the implementation. The section 'design notes' is still refering to a former implementation with the create(...) functions. Otherwise, I could compile and link the code on msvc .net 2008 with my setup. thanks for your library, best Johannes

5 10

Re: [boost] New library in Vault: Msm (Meta State Machine)
by christophe henry 16 Oct '08

16 Oct '08

Hi Andreas, > What do t & D stand for (they do not appear in Figure 2)? They don't seem to be necessary to implement the chart?You should also read the mini doc I included. I added them to make the problem a bit more interesting and show how to solve it with flags. > 1) Is it possible to implement the transitions exactly as shown in the chart? It is not, again as explained in the mini doc. I see this as an UML goto and decided to implement superior tools instead. > 2) If no, is this why you introduced two self-transitions to C, one with a guard to prevent transition from B?I didn't. They were there before, I just made them cleaner by using state flagging and a guard condition instead of crossing state boundaries. The UML diagram of the doc looks, in my opinion, cleaner now, less like spaghetti. Of course I could implement these entry and exit goto-like pseudo states if users want them. I just strongly doubt they are needed. _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE

2 1

New library in the Vault: ConstantTimeSize
by vicente.botet 16 Oct '08

16 Oct '08

Hi, Boost.ConstantTimeSize defines a configurable wrapper to the stl container list providing a size function with constant, linear or quasy_constant complexity. You can find the sources, documentation and some test in the Boost Vault. http://www.boostpro.com/vault/index.php?action=downloadfile&filename=consta… Any comments are wellcome, Vicente

8 17

[thread_safe_signals][signals2] call for reviewers (review tentatively scheduled Nov 1st - Nov 10th)
by Stjepan Rajko 16 Oct '08

16 Oct '08

Hello all, The review for the Signals2 library (formerly known as thread_safe_signals - description below) submitted by Frank Mori Hess has been tentatively scheduled for Nov 1st - Nov 10th. As per a recent discussion on the review process (http://tinyurl.com/48tdjs) and after consulting with the review wizards, we would like to try something new for this review: have a number of reviewers commit beforehand to submitting a review. The goal of signing up is to ensure that there is both sufficient interest in the library, and that there will be enough reviews submitted for an informed decision on acceptance. If you are interested in this library, I encourage you to sign up now to be a reviewer (by this you commit to submitting a review preferably by the end of the review period). Of course, additional reviews from non-signed-up reviewers will also be welcome, but without enough reviewers signing up beforehand it is not clear that we should proceed with a review at this time. To sign up, please send me a reply (here or privately), and let me know whether the review period is suitable for you (we can make some adjustments if necessary). I strongly encourage participation from reviewers that would examine the library from a purely user standpoint (commenting on the interface and / or the documentation), as well as reviewers that would be willing to look into the details of the implementation (i.e., you don't have to focus on both). I you would like to sign up, please let me know by this Saturday (October 18th). About the library: -------- * The library can be downloaded from: http://www.boostpro.com/vault/index.php?&directory=thread_safe_signals (latest version is signals2-2008-10-08.zip) * Documentation is also available online: http://www.comedi.org/projects/signals2/libs/signals2/doc/html/index.html * A synopsis: The Boost.Signals2 library (formerly known as thread_safe_signals) is an implementation of a managed signals and slots system. Signals represent callbacks with multiple targets, and are also called publishers or events in similar systems. Signals are connected to some set of slots, which are callback receivers (also called event targets or subscribers), which are called when the signal is "emitted." Signals and slots are managed, in that signals and slots (or, more properly, objects that occur as part of the slots) can track connections and are capable of automatically disconnecting signal/slot connections when either is destroyed. This enables the user to make signal/slot connections without expending a great effort to manage the lifetimes of those connections with regard to the lifetimes of all objects involved. When signals are connected to multiple slots, there is a question regarding the relationship between the return values of the slots and the return value of the signals. Boost.Signals2 allows the user to specify the manner in which multiple return values are combined. * Relationship to Boost.Signals: This is a thread-safe variant of the original Boost.Signals library. There have been some changes to the interface to support thread-safety, mostly with respect to automatic connection management. The following thread offers some more details on the differences between the two implementations, as well as a plan of a phased replacement of Boost.Signals should Signals2 be accepted: http://tinyurl.com/4sqau3 [nabble] Again, if you are interested in this library, please consider signing up as a reviewer. Kind regards, Stjepan (review manager)

6 12

Build doc update
by Vladimir Prus 16 Oct '08

16 Oct '08

According to: http://www.boost.org/development/index.html we're supposed to have beta release tomorrow, and final release on 31st. Are doc changes allowed in between? What becomes apparent on IRC, is that the current install docs have issues: - Boost.Build command line syntax docs are not very good, because they split information across several pages - Getting started fails to refer to command line syntax directly. - Getting started lists various variants that may be built, and their names, but does not give Boost.Build options to request those variants, so people start to improvise various interesting syntaxes. - It fails to clearly say that 'configure'/'make' is the approach that's only good for native, all-default build. I think it would be good to clear this up, and can work on this, but of course only if the changes can be gotten in. Comments? - Volodya

4 5

[1.37][Function] Request permission to merge changes
by Doug Gregor 16 Oct '08

16 Oct '08

Aleksey pointed out that Boost.Function in 1.36.0 has a critical thread-safety problem. I've now fixed the problem on the trunk, and---after regression tests cycle---would like to merge these changes (along with other long-stable fixes to Function) to the release branch. Okay? - Doug

4 9