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

Re: [boost] Namespace for a Boost Hashing Library
by Anders Dalvander 10 May '10

10 May '10

Scott McMurray wrote: > Some possibilities: > > - boost::hashes > - boost::hash_algo or boost::hash_algorithms > - boost::hashing or boost::hashing_algorithms > - boost::digests or boost::message_digest > - boost::fingerprint (or boost::dactylogram) > > Which one(s) do you prefer or dislike? > > Thanks, > ~ Scott McMurray > My votes goes to, in order: 1. boost::hash_algo 2. boost::crypto_hash 3. boost::hashes 4. boost::c11c_hash (not an actual proposal) Regards, Anders Dalvander

1 0

[website] favicon path was incorrect
by Jeremiah Willcock 10 May '10

10 May '10

Look at https://svn.boost.org/favicon.ico or the file I attached; /htdocs/site/favicon.ico is still the old, larger icon. -- Jeremiah Willcock

1 0

New list moderators needed!
by Beman Dawes 10 May '10

10 May '10

It is high time we added additional mailing list moderators. The current moderators have been in place for years, but in the meantime their day job responsibilities have changed, or other distractions are preventing them from giving list moderation the attention it deserves. While the current moderators will make the final decision, it would be helpful to hear nominations from the list for several new moderators. Who are some regular posters with the "right stuff" to keep the list civil, productive, and interesting? Actually moderating postings doesn't take a lot of time, since only postings from new posters need manual moderation. But we need moderators who read all or most postings, and step in when guidelines aren't being observed. --Beman

4 4

[cstdint] Why no cstdint.hpp merge from trunk for 1.43.0?
by Number Cruncher 10 May '10

10 May '10

I've just been looking at the latest 1.43 and noticed the same issue with the redefinition of INT*_C macros as 1.42, yet the fix was committed to the trunk 3 months ago: https://svn.boost.org/trac/boost/changeset/59430/trunk/boost/cstdint.hpp Any ideas why this didn't make the 1.43 release? Thanks, Simon

2 1

[asio] boost include problem
by Elimentz 10 May '10

10 May '10

Hey I'm trying to use a Boost asio Basic_serial_port in my project, so I include the file asio.hpp like this: #include <boost/asio.hpp> This file contains a lot of other includes, but it seems it is impossible for my project to include these, not a single one... how can I fix this? I mean, this should work, right? these files were written by the developers themselves!! -- View this message in context: http://old.nabble.com/-asio--boost-include-problem-tp28502931p28502931.html Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[thread] thread_specific_ptr and static initialization order
by Tanguy Fautré 09 May '10

09 May '10

Hi, After upgrading from 1.42 to 1.43 (using VC10 x64), I encounter an access violation related to thread_specific_ptr. The program used to run fine with previous version of Boost on several platforms (Win x32, Win x64 and Linux x64). I've managed to create a small program that reproduces the problem. It seems to be a static initialization order related problem. If the TSS is initialized by a static object, the program fails (nullptr exception). However, if the static object is commented out, and the TSS is solely initialized in the main, the program runs fine. Is thread_specific_ptr supposed to work even when initialized by another static object? Or does it require to be initialized only after entering main? Regards, Tanguy #include <boost/thread/thread.hpp> #include <boost/thread/tss.hpp> #include <iostream> #include <stdexcept> namespace { boost::thread_specific_ptr<int> tss; void verifyTss() { if (tss.get() == nullptr) throw std::runtime_error("verifyTss failed (nullptr)"); } class InitTss { public: InitTss() { tss.reset(new int); } }; InitTss init_tss; } int main(int argc, char argv[]) { try { tss.reset(new int); verifyTss(); boost::thread thread([] () { tss.reset(new int); }); thread.join(); verifyTss(); } catch (const std::exception & error) { std::cerr << "ERROR: " << error.what() << std::endl; } }

2 4

Is release branch open for merges?
by Andrey Semashev 09 May '10

09 May '10

Now that 1.43 is released, is the release branch open for merges?

2 1

[lambda][cast] 1.42 and 1.43 boost/lambda/cast.hpp requires #include before it - bug?
by Krzysztof Czainski 09 May '10

09 May '10

I have noticed, that with includes in this order: #include <boost/lambda/cast.hpp> #include <boost/lambda/lambda.hpp> later using ll_static_cast fails to compile with first message (gcc-4.3): /usr/include/boost/lambda/casts.hpp:93: error: ‘return_type_N’ is not a template However, including lambda.hpp before cast.hpp fixes the error. I have tested this with boost 1.42.0 and 1.43.0. Regards Krzysztof Czainski

2 1

Like boost::enable_if, but takes a "priority number" and changes overload resolution order
by Dennis Ferron 09 May '10

09 May '10

>From the Boost documentation: "The enable_if family of templates is a set of tools to allow a function template or a class template specialization to include or exclude itself from a set of matching functions or specializations based on properties of its template arguments." Sometimes instead of completely excluding a function from overload resolution, I only really want to "tweak" C++'s overload resolution order, or disambiguate an edge case. Instead of relying on C++'s overload priorities, sometimes I'd like to explicitly set the overload priority, like this: template <typename T> void func(boost::overload_priority<1> dummy, ArgType1 arg) {} template <typename T> void func(boost::overload_priority<2> dummy, ArgType2 arg) {} template <typename T> void func(boost::overload_priority<3> dummy, ArgType3 arg) {} Whereas enable_if causes a "hard" error to trigger SFINAE and take a function out of consideration, overload_priority would have some sort of "soft" effect that "tricks" the C++ compiler into thinking it is a less specific match than it is, moving it down in the order of which gets chosen, without actually invalidating it. It isn't obvious that this is even possible, but then, I would never have believed "enable_if" was possible before I heard of it. Whereas enable_if works by wrapping the return type of the function, I believe this would have to wrap a function argument to work. What I have in mind is that the overload_priority class would look like this: template <int N> class overload_priority { public: overload_priority(int x) { ... } }; You would call the overloaded function like this: func(0, the_actual_arg); I'm thinking it would affect the overload priority by some trick like causing an N-deep nested conversion sequence (overload_priority<3> constructed from overload_priority<2>, from overload_priority<1>, from the integer 0) or by the constructor having N extra parameters with default arguments. Any comments or ideas for improving this?

2 1

[parameter] accessing param type within signature
by Lorenzo Caminiti 09 May '10

09 May '10

Hello all, I am new to Boost.Parameter. I am having troubles getting the depth_first_search() example from the documentation section 2.1.5.6.2 to compile. Was the example in section 2.1.5.6.2 even compiled? If so, can someone point to the code that can be compiled? (I did look into Boost sandbox libs/parameter/... but I did not see it there.) 1) I need to access graph_type to write type requirements of following parameters. 2) The documentation section 2.1.5.6.1 says I can use graph_type (or xyz_type in general) from within the signature to refer to the parameter type. However, that seems not to be the case (also looking at the preprocessed code, xyz_type is a template parameter available only in the function body but not in the signature). 3) The documentation section 2.1.5.6.2 seems to use tag::graph::_ instead of graph_type to access the type (also sometimes graphs::graph::_ is used but I think that might be a typo... because the tag namespace should be there as in graphs::tag::graph::_). 4) Finally, even when I try to use tag::graph::_ to refer to graph_type, I get the GCC error below. What am I doing wrong? // File: g00.cpp #include <boost/parameter.hpp> namespace graphs { BOOST_PARAMETER_NAME(graph) BOOST_PARAMETER_NAME(graph2) BOOST_PARAMETER_FUNCTION( (void), depth_first_search, tag, (required (graph, *) (graph2, (tag::graph::_)) // Trying to use graph's type here... but I can't use graph_type and graph::_ does not compile... ) ) { // Here I can use graph_type. } } // namespace int main() { graphs::depth_first_search(1, 2); return 0; } $ g++ -Wall -Werror -I./src -DCONTRACT_CHECK_BLOCK_INVARIANT -DCONTRACT_CHECK_CLASS_INVARIANT -DCONTRACT_CHECK_PRECONDITION -DCONTRACT_CHECK_POSTCONDITION example/Own/parameter/g00.cpp /usr/include/boost/parameter/value_type.hpp: In instantiation of ‘boost::parameter::value_type<mpl_::arg<2>, graphs::tag::graph, boost::parameter::void_>’: example/Own/parameter/g00.cpp:9: instantiated from ‘typename graphs::boost_param_result_17depth_first_search<Args>::type graphs::boost_param_impldepth_first_search(const Args&) [with Args = boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<graphs::tag::graph2, const int>, boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<graphs::tag::graph, const int>, boost::parameter::aux::empty_arg_list> >]’ example/Own/parameter/g00.cpp:9: instantiated from ‘typename graphs::boost_param_result_17depth_first_search<typename boost::parameter::aux::argument_pack<graphs::boost_param_params_17depth_first_search<int>, const ParameterArgumentType0, const ParameterArgumentType1, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type>::type graphs::depth_first_search(const ParameterArgumentType0&, const ParameterArgumentType1&, typename boost::parameter::aux::match<graphs::boost_param_params_17depth_first_search<int>, ParameterArgumentType0, ParameterArgumentType1, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type) [with ParameterArgumentType0 = int, ParameterArgumentType1 = int]’ example/Own/parameter/g00.cpp:24: instantiated from here /usr/include/boost/parameter/value_type.hpp:60: error: no type named ‘binding’ in ‘struct mpl_::arg<2>’ /usr/include/boost/parameter/value_type.hpp:62: error: no type named ‘binding’ in ‘struct mpl_::arg<2>’ example/Own/parameter/g00.cpp: In function ‘typename graphs::boost_param_result_17depth_first_search<Args>::type graphs::boost_param_impldepth_first_search(const Args&) [with Args = boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<graphs::tag::graph2, const int>, boost::parameter::aux::arg_list<boost::parameter::aux::tagged_argument<graphs::tag::graph, const int>, boost::parameter::aux::empty_arg_list> >]’: example/Own/parameter/g00.cpp:9: instantiated from ‘typename graphs::boost_param_result_17depth_first_search<typename boost::parameter::aux::argument_pack<graphs::boost_param_params_17depth_first_search<int>, const ParameterArgumentType0, const ParameterArgumentType1, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type>::type graphs::depth_first_search(const ParameterArgumentType0&, const ParameterArgumentType1&, typename boost::parameter::aux::match<graphs::boost_param_params_17depth_first_search<int>, ParameterArgumentType0, ParameterArgumentType1, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::type) [with ParameterArgumentType0 = int, ParameterArgumentType1 = int]’ example/Own/parameter/g00.cpp:24: instantiated from here example/Own/parameter/g00.cpp:9: error: no matching function for call to ‘boost::parameter::aux::cast<void ()(boost::parameter::value_type<mpl_::arg<2>, graphs::tag::graph, boost::parameter::void_>)>::execute(const int&)’ /usr/include/boost/parameter/aux_/cast.hpp:99: note: candidates are: static boost::parameter::aux::use_default_tag boost::parameter::aux::cast<void ()(T)>::execute(boost::parameter::aux::use_default_tag) [with T = boost::parameter::value_type<mpl_::arg<2>, graphs::tag::graph, boost::parameter::void_>] /usr/include/boost/parameter/aux_/cast.hpp:109: note: static T boost::parameter::aux::cast<void ()(T)>::execute(T) [with T = boost::parameter::value_type<mpl_::arg<2>, graphs::tag::graph, boost::parameter::void_>] example/Own/parameter/g00.cpp:9: error: return-statement with a value, in function returning 'void' $ g++ --version g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Copyright (C) 2007 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. I have tried this on Boost 1.42.0 and 1.34.1 (same errors). Thank you very much. -- Lorenzo

1 0

Problem with Property Tree under WinXP, Eclipse, mingw
by Rouven Walter 09 May '10

09 May '10

Hello, I have posted the message below in the users boost mailinglist before. But there was no satisfying answer, so I decided to post it once again on the developers list. It seems to be a more technical problem. I'm looking forward for your answers, thanks, Cyraid ---- Hello, I use Windows XP with MinGW and Eclipse for C++ developing. I want to use the xml parser included in the property tree library of boost. I started trying the example at [1]http://www.boost.org/doc/libs/1_43_0/doc/html/boost_propertytree/tutorial .html but it failed with the following error: **** Build of configuration Debug for project Test CPP Project **** **** Internal Builder is used for build **** g++ -IC:\Programme\boost_1_42_0 -O0 -g3 -Wall -c -fmessage-length=0 -osrc\Test.o ..\src\Test.cpp C:/Programme/boost_1_42_0/boost/property_tree/detail/ptree_utils.hpp:In function `std::string boost::property_tree::detail::narrow(const Ch*) [with Ch = wchar_t]': C:/Programme/boost_1_42_0/boost/property_tree/string_path.hpp:62: instantiated from here C:/Programme/boost_1_42_0/boost/property_tree/detail/ptree_utils.hpp:76: warning: comparison between signed and unsigned integer expressions C:/Programme/boost_1_42_0/boost/property_tree/detail/ptree_utils.hpp:76: warning: comparison is always false due to limited range of data type C:/Programme/boost_1_42_0/boost/property_tree/detail/xml_parser_read_rapidxm l.hpp: In function `void boost::property_tree::xml_parser::read_xml_internal(std::basic_istream<typen ame Ptree::key_type::value_type, std::char_traits<typename Ptree::key_type::value_type> >&, Ptree&, int, const std::string&) [with Ptree = boost::property_tree::basic_ptree<std::string, std::string, std::less<std::string> >]': C:/Programme/boost_1_42_0/boost/property_tree/xml_parser.hpp:85: instantiated from `void boost::property_tree::xml_parser::read_xml(const std::string&, Ptree&, int, const std::locale&) [with Ptree = boost::property_tree::ptree]' ..\src\Test.cpp:39: instantiated from here C:/Programme/boost_1_42_0/boost/property_tree/detail/xml_parser_read_rapidxm l.hpp:108: error: non-constant `(((int)f_c) | 3072)' cannot be used as template argument C:/Programme/boost_1_42_0/boost/property_tree/detail/xml_parser_read_rapidxm l.hpp:108: error: no matching function for call to `rapidxml::xml_document<char>::parse(char*)' Build error occurred, build is stopped Time consumed: 4109 ms. I have included the necessary header files in the eclipse project properties. For me, the error message seems to be some internal failure in the library? Or where could I have done a mistake ? Best regards, Cyraid GRATIS: Movie-Flat mit über 300 Top-Videos. Für WEB.DE Nutzer dauerhaft kostenlos! Jetzt freischalten unter http://movieflat.web.de References 1. http://www.boost.org/doc/libs/1_43_0/doc/html/boost_propertytree/tutorial.h…

1 0

[1.43.0] PDF build of docs now available.
by John Maddock 09 May '10

09 May '10

The PDF build of the documentation for 1.43 (for those libraries that support this) is now available from the sourceforge download page: http://sourceforge.net/projects/boost/files/ The direct links are: http://sourceforge.net/projects/boost/files/boost-docs/1.43.0/boost_pdf_1_4… http://sourceforge.net/projects/boost/files/boost-docs/1.43.0/boost_pdf_1_4… http://sourceforge.net/projects/boost/files/boost-docs/1.43.0/boost_pdf_1.4… http://sourceforge.net/projects/boost/files/boost-docs/1.43.0/boost_pdf_1.4… Enjoy! John.

1 0

Problem building Boost test framework
by Matthias Troyer 09 May '10

09 May '10

Hi, I am trying to build the libraries for the Boost test framework myself (using my own CMake files) instead of using bjam. When trying to link the file execution_monitor.cpp debug.cpp cpp_main.cpp into a dynamic library libboost_prg_exec_monitor.dylib I get the following linker erros: Linking CXX shared library libboost_prg_exec_monitor.dylib ld: warning: duplicate dylib /usr/lib/libpthread.dylib Undefined symbols: "boost::debug::attach_debugger(bool)", referenced from: _execution_monitor_attaching_signal_handler in execution_monitor.cpp.o "boost::debug::under_debugger()", referenced from: boost::execution_monitor::execute(boost::unit_test::callback0<int> const&)in execution_monitor.cpp.o Do I need to link additional files? Matthias

2 1

[xint] Third release is ready, requesting preliminary review
by Chad Nelson 09 May '10

09 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm happy to announce that the third release of the Extended Integer library is ready, in both the sandbox and the Vault. This is a major overhaul of the library, taking into account all of the feedback and recommendations provided on the first two: * The exception-blocking system is gone, replaced by a separate nothrow_integer class. * There's now a fixed_integer class template as well. * The test functions now use Boost.Test, and the documentation has been moved to Doxygen. * Nearly every function received a thorough examination as well; many of them were tweaked, and a few completely replaced. Please take a look and let me know what you think of the changes. I'm very happy with them. - -- Chad Nelson Oak Circle Software, Inc. * * * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvabA0ACgkQp9x9jeZ9/wSwvACcCJ18QkRbKWmByYO7Q1xe6qYx EUYAnRl4+mzw9X2VvGCCFPl0Q0VWLhRN =fhbW -----END PGP SIGNATURE-----

21 230

Re: [boost] [rfc] Preliminary Hash Library
by Sean Chittenden 08 May '10

08 May '10

re: Possible namespaces. Why not use boost::digest? "Cryptographic hashes" are more pedantically known as one-way digests of blobs of data. A "hash," as hijacked by perl (or dictionary, or unordered_map), is an ADT comprised of a digest of a key and a value. crc's a digest as well, but for legacy reasons already has a top-level namespace. Some digests are crypto grade, some aren't, but they all fall in to the digest category. $0.02. -sc -- Sean Chittenden sean(a)chittenden.org

1 0

[constrained-value] with 1.43.0
by Neal Becker 08 May '10

08 May '10

I found my code using constrained_value compiles with boost-1.42.0, but not with 1.43.0. Rather mysterious error message: /usr/local/src/boost.hg/boost/constrained_value/constrained.hpp:64: error: 'template<class ExceptionType> struct boost::constrained_value::throw_exception' is not a function, /usr/local/src/boost.hg/boost/throw_exception.hpp:74: error: conflict with 'template<class E> void boost::throw_exception(const E&)' /usr/local/src/boost.hg/boost/throw_exception.hpp:54: error: in call to 'throw_exception' scons: *** [mod/fixed_pt.os] Error 1

3 8

[proto][can_be_called]
by Andy Venikov 08 May '10

08 May '10

Currently, can_be_called<> expects only functors. Is it possible to extend it so that it can take any type and return true if that type can be called with the list of given parameters. For example, function<int (int, char, long)> functor; int f(int, char, long); int dummyInt; int main(int argc, char ** argv) { assert(false == test(functor, argc, 11, argv)); assert(true == test(functor, 10, 11, 12)); assert(true == test(f, 10, 11, 12)); assert(false == test(dummyInt, 1)); } Thanks, Andy.

5 10

Re: [boost] [castor] Interest in Logic Paradigm for C++ ?
by William Byrd 08 May '10

08 May '10

Hi Roshan! I'm a newbie C++ programmer, but I have experience designing logic programming languages (e.g., miniKanren in Scheme). I'm curious why Castor doesn't implement full unification. Is this because of the historical relationship between Castor and Leda? There are many interesting logic programs that can't be written naturally without full unification. (My dissertation contains many such programs, so I'm biased!) Many people in the logic programming community don't consider Mercury to be a real logic programming language precisely because it doesn't support full unification. Is Castor aiming towards the Mercury model, with the idea of adding mode annotations, etc., in the future? That might be a nice sweet spot for the Boost libraries. Otherwise, I would prefer to see full unification in any official Boost logic programming language/library. How hard would it be to add full unification to Castor, or to at least allow full unification as an option? --Will

2 1

Re: [boost] [rfc] Preliminary Hash Library
by Minh Phanivong 08 May '10

08 May '10

How about boost::hash_algo? Sent from my iPhone On 08/05/2010, at 11:51 PM, "Stewart, Robert" <Robert.Stewart(a)sig.com> wrote: Scott McMurray wrote: On 6 May 2010 06:01, Daniel James <dnljms(a)gmail.com> wrote: This will collide with the existing 'boost::hash' (an implementation of 'std::hash'). The simplest fix would be just changing the namespace to boost::hashes. Alternatively, the library could be renamed to Cryptographic_Hash and use boost::cryptographic_hash as its namespace, though that would cut off the possibility of following Paul Bristow's suggestion. Adding just one letter at the end makes for a rather slim differentiator, but I don't think it will hurt. We already have boost::tuple and boost::tuples, right? Unless you intend to create the Boost Cryptographic Hashing Library versus one that supports a wider range of hashing algorithms, don't include "cryptographic" in the name or namespace. What about Boost Hashing Algorithms Library with namespace boost::hashing_algorithms? A handy namespace alias would be "hal" or "ha." ;) _____ Rob Stewart robert.stewart(a)sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

[rfc] Preliminary Hash Library
by Scott McMurray 08 May '10

08 May '10

I've boostified, cleaned up, and documented the Hash Library I mentioned here about a month ago. Comments, complaints, suggestions, and questions appreciated. Source code is in the sandbox at http://svn.boost.org/svn/boost/sandbox/hash/ Documentation can be read online at http://www.cs.mcgill.ca/~smcmur/hash/ I was very pleased by how the implementation came together, as templates mean that all the hash algorithms share a substantial portion of their code. Those details are all hidden from the user, though. Here's an example showing the simplest use of the library: #include <boost/hash.hpp> #include <iostream> #include <string> int main() { std::string s = "Hello World!"; typedef boost::hash::sha2<256> HashPolicy; HashPolicy::digest_type digest = boost::hash::compute_digest<HashPolicy>(s); std::cout << digest << "\n"; } Thanks, ~ Scott McMurray

7 14

[ASIO] Compilation improvements of 1.43 (well done)
by Artyom 08 May '10

08 May '10

Hello, In release notes of 1.43.0 version of Boost.Asio I had noticed improvements in compilation times and executable size. I must admit: WELL DONE!!! I'm in process of replacement of Boost.Asio event loop with my own that has very similar API but uses templates only where they absolutely necessary. I did some comparisons of my CppCMS library that implements with Asio. - HTTP server (tcp), - SCGI-server (tcp+unix-sockets), - FCGI-server (tcp+unix-sockets). - Memcached-like blocking-client and non-blocking server (TCP). Compiled with g++-4.3.2, on Debian, amd64, Linux 2.6.26 ------------------------------------------------------- Library size (after strip -s): ------------------------------ Boost.Asio 1.41.0 - 3,527,856 Boost.Asio 1.43.0 - 3,003,504 My AIO - 2,607,848 (2,455,344 cppcms-lib + 152,504 aio-lib). Moving from 1.41 to 1.43 reduced library by 0.5mb and this is huge difference However replacing Asio with my AIO (that hides almost everything behind pimpl) reduced additional 0.4mb Compilation times: HTTP-Server (tcp) 1.41.0 - 12.87s 1.43.0 - 7.45s my-aio - 4.30s SCGI-Server (tcp&unix) note Asio requires template based implementation as Unix socket class is different from tcp/ip ones so code almost can't be shared. My-AIO has same class so the code is not template based 1.41.0 - 14.31s 1.43.0 - 7.12s my-aio - 2.55s Again - huge difference: moving from 1.41 to 1.43 reduces time by half, but my-aio gives even better improvements. ---------------------------------------------- My Notes: 1. I'm really interested what had been done to give such huge improvements from 1.41 to 1.43? 2. Maybe it is wide to consider making Asio compiled library rather then header-only one? Artyom ------------ P.S.: I replace ASIO with my own library for several reasons not connected to quality of this specific library (it is great) but rather with issues I have with Boost and it's design. Also my library influenced by boost.asio API so rewriting was almost as simple as running several "sed" scripts over the source code.

2 1

[Serialization] 1.42.0 oserializer.hpp:394 bug?
by Krzysztof Czainski 08 May '10

08 May '10

File: serialization/oserializer.hpp, line 394: if(NULL == true_type){ boost::serialization::throw_exception( archive_exception( archive_exception::unregistered_class, true_type->get_debug_info() ) ); } I think, that if true_type is NULL, then true_type->get_debug_info() is UB.

3 2

Re: [boost] [Iterators] Iterators and higher-order programming
by Thomas Jordan 07 May '10

07 May '10

Mathias Gaunard wrote: -------------------------------------------------------------------- Message: 2 Date: Sun, 25 Apr 2010 12:33:51 +0100 From: Mathias Gaunard <mathias.gaunard(a)ens-lyon.org> To: boost(a)lists.boost.org Subject: Re: [boost] [Iterators] Iterators and higher-order programming Message-ID: <hr19av$sgp$1(a)dough.gmane.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Thomas Jordan a ?crit : > Hi, > One of the interesting things about the iterators library, it seems to me, is the additional support it gives for higher-order, > functional-style programming. For example, you can use the transform and filter iterators to produce a simple 'Comprehension' object > which permits list-comprehension type of syntax to be used, instead of conventional loops You might want to look at the range library then, which has been recently modified to add support for things like: some_range | transformed(f) | filtered(p) ----------------------------------------- Thanks/merci, Mathias (and apologies for my late reply), I am now looking at 1.43.0 Boost::Range! T.

2 1

bjam's use of O_NONBLOCK in execunix.c
by Dan Gohman 07 May '10

07 May '10

Hello, Why does bjam on "unix" platforms set the O_NONBLOCK flag when creating standard output and error pipes from the child process to the parent process? https://svn.boost.org/trac/boost/browser/trunk/tools/jam/src/execunix.c#L189 This was introduced in change r38009: https://svn.boost.org/trac/boost/changeset/38009 The parent process uses select(2) to block and wait for output from children, so it doesn't appear to need non-blocking file descriptors. Child processes are unrelated programs, and it seems mistaken to assume that they will want their stdout and stderr to be non-blocking. A project that I'm involved in recently had to add code to handle EAGAIN from a write(2) call by spinning until it succeeds, and it seems to be fairly common practice. It would seem to be better if the parent would just leave the file descriptors in blocking mode. Thanks, Dan

2 1

[fusion] BOOST_FUSION_ADAPT_CLASS* not documented
by Michael Caisse 07 May '10

07 May '10

I may be able to submit a patch after boostcon but I thought I would first check to see if this is just an issues with the latest docs not being checked in. I just verified the trunk is missing docs about the class adaption macros. regards - michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com

2 1