- Boost - lists.boost.org

[any] Multimethod for boost::any and modified boost::any to fit multi method
by nowake＠fiercewinds.net 20 Feb '09

20 Feb '09

Hi All. I create multi method for boost::any using Modern C++ Design's multi method technique. It can dispatch method dynamically like this: _________________________________________________________________________ struct T1 { string operator()(int value) const { return string("T1(int)"); }; string operator()(double value) const { return string("T1(double)"); }; string operator()(A value) const { return string("T1(A)"); }; }; // "entry" to Multi method bool t10(Multimethod::entry<any, any, T1, int>()); bool t11(Multimethod::entry<any, any, T1, double>()); bool t12(Multimethod::entry<any, any, T1, A>()); struct T2 { string operator()(int value) const { return string("T2(int)"); }; }; // "entry" to Multi method bool t20(Multimethod::entry<any, any, T2, int>()); BOOST_AUTO_TEST_CASE(test04) { any m((T1())); any a(0); BOOST_CHECK_EQUAL( any_cast<string>(Multimethod::apply<any>(m, a)), "T1(int)"); a = 0.0; BOOST_CHECK_EQUAL( any_cast<string>(Multimethod::apply<any>(m, a)), "T1(double)"); a = A(); BOOST_CHECK_EQUAL( any_cast<string>(Multimethod::apply<any>(m, a)), "T1(A)"); m = T2(); a = 0; BOOST_CHECK_EQUAL( any_cast<string>(Multimethod::apply<any>(m, a)), "T2(int)"); }; __________________________________________________________________________ If you are interested in this multi method, please see #2749 for detail. https://svn.boost.org/trac/boost/ticket/2749 Thanks, Nowake

4 10

[asio] two-lock queue deadlocks?
by Dean Michael Berris 20 Feb '09

20 Feb '09

Hi Guys, I've run into an issue with defining BOOST_ASIO_ENABLE_TWO_LOCK_QUEUE when using Boost.Asio in Boost 1.38.0. I'm currently implementing an asynchronous HTTP client and when I wanted to try the experimental feature and on a single-core machine apparently I run into a deadlock when the asynchronous handler is itself posting to the same io_service queue that hosted it. Is this a known issue with BOOST_ASIO_ENABLE_TWO_LOCK_QUEUE, or is this a usage issue? -- Dean Michael Berris | Software Engineer, Friendster, Inc. blog.cplusplus-soup.com | twitter.com/mikhailberis | linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis | deanberris.com

1 0

[asio] Received 3 times RST, ACK before the boost TCP returns connection failure
by allen han 20 Feb '09

20 Feb '09

Hi: Pretty new to use the boost library for networking and experienced a problem to use the TCP socket on client side. 1. using the call below to connect server: mSocket.async_connect(endpoint,boost::bind(&handleConnect, this, boost::asio::placeholders::error, ++aEndPointIterator)); 2. found connection is failed, then close the socket void handleConnect(const boost::system::error_code &aErr, boost::asio::ip::tcp::resolver::iterator aEndPointIter) { if (!aErr) { ... } else if (aEndPointIter != boost::asio::ip::tcp::resolver::iterator()) { doClose(); ... } else { ... doClose(); } } 3. From Ethereal, found that SYN, RST/ACK have been sent 3 times before the connection is closed, Client sent Server SYN, Server sent Clinet RST, ACK Client sent Server SYN, Server sent Clinet RST, ACK Client sent Server SYN, Server sent Clinet RST, ACK Question: Any flag to inform the boost TCP stack to return error if it receives the first RST,ACK?

2 1

[1.38] PDF docs release candidate available
by John Maddock 19 Feb '09

19 Feb '09

The release candidate for the PDF build of the 1.38 docs is now available from http://boost.cowic.de/rc/pdf/, unless anyone spots any last minute issues, I'll put these on sourceforge at the weekend. Enjoy, John.

3 6

[date_time] How to build the docs?
by John Maddock 19 Feb '09

19 Feb '09

Am I correct in thinking that the date_time docs need some manual intervention to build correctly? Any instructions? Thanks, John.

1 0

[fusion] C++0x support?
by Ein Held 19 Feb '09

19 Feb '09

Hello is there any chance for c++0x support (rvalue forwarding for the containers' constructors and operator=s' in particular) for fusion in 1.39? Thank you

1 0

[date_time] Trouble with operator+ and microsec(BIG_NUMBER)
by Christoph Mathys 19 Feb '09

19 Feb '09

Hello I'm using date_time on a 32b Ubuntu machine (1.36, gcc 4.2.4). The following code shows the problem (at least on my machine): (compiled with -O2 -Wall, without warnings) #include <iostream> #include <boost/date_time/posix_time/posix_time.hpp> #include <boost/date_time/gregorian/gregorian_types.hpp> using namespace std; namespace bpt = boost::posix_time; int main(int, char**) { const int64_t timeInNs = 1235051546649264674LL; const bpt::ptime EPOCH(boost::gregorian::date(1970, 1, 1)); bpt::ptime offset = EPOCH + bpt::microsec(timeInNs / 1000); cout << offset << std::endl; return 0; } I expect this program to print a date after 1.Jan 1970. However, I get the following output: 1969-Dec-21 19:28:13.710725 If I change timeInNs to 1235051546649264LL (I removed the last 3 digits), the date is after 1.1.1970. Whats wrong? Christoph

1 0

[log] Review-ready version in the Vault
by Andrey Semashev 19 Feb '09

19 Feb '09

After a long time of documenting, polishing and testing I'm glad to announce that Boost.Log has reached the level where public review request can be submitted. The automatic tests aren't entirely complete, however, the basic functionality is covered and most of what is not covered has been tried by hand. Major changes since my last publicly announced version: * Substantial documentation improvement. * Added several Windows-specific sinks: Event Log (simplified and advanced), Windows debugger and experimental Event Trace for Windows Vista and later. * Loggers now consist of a number of independent features that can be composed the way the user needs. User-defined features can be developed and injected into the mix. * Attribute value extractors improved. With the new extract function attribute values can be extracted from the attribute values view by employing lambda functors. * Some files and classes were moved or renamed to improve code clarity and shorten names. * A number of bugs fixed. * Added tests. The archive with the library source code, tests and docs is available in the Vault: http://tinyurl.com/cm9lum The online docs are also available on the SourceForge page: http://boost-log.sourceforge.net The latest code snapshot can be downloaded from CVS on the SourceForge project page: http://sourceforge.net/projects/boost-log The code should be compatible with Boost 1.38. Might also work with 1.37, but I didn't try. Comments are welcome.

15 69

Proposal: Post-Release Maintenance Team (WAS Re: [test] [gcc-4.3.2] check_is_close and check_is_small issues)
by Dean Michael Berris 19 Feb '09

19 Feb '09

On Thu, Feb 19, 2009 at 3:58 PM, Juergen Hunold <juergen.hunold(a)ivembh.de> wrote: > Hi Dean ! > > On Thursday 19 February 2009 02:34:05 Dean Michael Berris wrote: > >> Thanks for these links! Did they apply cleanly to Boost 1.38.0 for >> you? I tried both (in the given order above) and I got some rejections >> when I applied them to a cleanly unpacked distribution. > > Well, actually not ;-(( > I think you can safely ignore the patch to utils/runtime/cla/parameter.hpp as > this just fixes a regression which happened in between the changes. > I'll dig further into this and ask the maintainer for permission to merge at > least the warning fixes to the release branch. > Alright. Now this time, would there be any objections if I (or other people) tried managing a patch release for 1.38.0? Would anybody else be interested in helping release a 1.38.1 with fixes hand-ported from trunk to 1.38.0? I've found some Jamfile fixes required to work around the (I'm guessing, now defunct) 'message' function in Boost.Build v2 that's bundled with Boost 1.38 that might be worth looking at. I'm also interested in bringing in a newer version of Boost.Build from the nightly builds into the 1.38.0 release to be packaged as 1.38.1; HTH -- Dean Michael Berris | Software Engineer, Friendster, Inc. blog.cplusplus-soup.com | twitter.com/mikhailberis | linkedin.com/in/mikhailberis | profiles.friendster.com/mikhailberis | deanberris.com

2 3

[Serialization] BOOST_CLASS_EXPORT regression on SunCC
by Sohail Somani 19 Feb '09

19 Feb '09

>From version 1.34 to 1.35, the export of classes was modified so that all the archives did not need to be included before calls to BOOST_CLASS_EXPORT. I don't know why this was a problem to begin with. Anyway, this feature used to work on SunCC but with the new changes, there is a regression. This is caused by the dependence on ADL to instantiate the ptr_serialization_support members: SunCC just doesn't do it. So the instantiations never occur and you get an assertion failure when running the serialization tests under debug: Assertion failed: it != boost::serialization::singleton< oserializer_map<Archive> >::get_const_instance().end(), file vendor/boost_1_37_0/boost/archive/impl/archive_pointer_oseri\ alizer.ipp, line 64 I know how to fix it (instantiating manually for each Archive,Serializable pair, not a huge problem). I would suggest that Boost Serialization should have a fallback mechanism for these compilers. Perhaps along the lines of the old export functionality where the user would define the archives they are interested in. Thoughts?

5 32