- Boost - lists.boost.org

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