- Boost - lists.preview.boost.org

binary operator raits
by frederic.bron＠alcan.com 05 Sep '08

05 Sep '08

I have just commited new traits in the sandbox (sandbox/type_traits) to know if a type is comparable or not. I have included tests but could not make bjam and quickbook run together so I have no documentation to commit. The names of the traits are based on standard header <functional>: is_less_comparable<T>, is_less_equal_comparable<T>, is_greater_comparable<T>, is_greater_equal_comparable<T>, is_ equal_to_comparable<T> and is_not_equal_to_comparable<T>. Some comments about these traits: - I was not able to remove the warnings, - the traits inherits from true_type is the operator exists, however, I am not sure if we should return true if the binary operator does not return a type convertible to bool F. Bron Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.

1 0

Asio and SSL problem
by Berserker 05 Sep '08

05 Sep '08

I tried to post this problem in the asio mailing list but I hadn't any feedback, so I'm reporting it here with the hope that someone can help me. I have a "stack overflow" problem with the following code (using boost 1.36): void test_handshake(const std::string &host, const std::string &cert) { boost::asio::io_service service; boost::asio::ssl::context sslContext(service, boost::asio::ssl::context::sslv23); sslContext.set_verify_mode(boost::asio::ssl::context::verify_peer); sslContext.load_verify_file(cert); boost::asio::ip::tcp::resolver resolver(service); boost::asio::ip::tcp::resolver::iterator endpoint_iterator = resolver.resolve(boost::asio::ip::tcp::resolver::query(host, "443")); boost::asio::ip::tcp::resolver::iterator end; boost::asio::ssl::stream<boost::asio::ip::tcp::socket> sslSocket(service, sslContext); boost::system::error_code error = boost::asio::error::host_not_found; while(error && endpoint_iterator != end) { sslSocket.next_layer().close(); sslSocket.next_layer().connect(*endpoint_iterator++, error); } if(error) throw boost::system::system_error(error); sslSocket.handshake(boost::asio::ssl::stream_base::client); // bla bla } When I call this function with a valid certificate for the host I have no problems, but when I pass a "custom" cerificate (not valid for the host specified) it results in a stack overflow error instead of throwing an exception as I expected... This example works: test_handshake("sourceforge.net", "cacerts.pem"); // grab cacerts.pem from here for example: http://www.cs.fsu.edu/~engelen/soapcacerts.html This causes, as I said, a stack overflow instead of an exception: test_handshake("sourceforge.net", "ca.pem"); // ca.pem was taken from the asio examples Plz help P.S.: is anyone using asio with ssl? It's very strange that nobody has reported this problem... _________________________________________________________________ Cerchi un locale per la serata? Chiedilo a Live Maps! http://maps.live.it/

2 1

Boost::log query
by Rajpal Dangi 05 Sep '08

05 Sep '08

While using rotating text file as stream, is it possible to keep most recent log file name same all the time? Currently what I observe is 'N' keeps incrementing and have to manually find out the most recent file. Also, is there some way to print severity in log file without explicitly passing it as part of message i.e. BOOST_LOG_SEV(my_logger, CRITICAL) Thanks

2 5

[testing] How not to mark up explicit failures
by David Abrahams 05 Sep '08

05 Sep '08

https://svn.boost.org/trac/boost/ticket/2258 describes a problem with explicit failure markup that I suspect is not atypical. I believe we need to establish some ground rules for markup that ensure * Boost problems don't pass unnoticed * there is a uniform standard for interpreting test results across libraries * "non-Boost problems" and non-problems don't add alarm bells for people reading test results You can view the markup in question here: https://svn.boost.org/trac/boost/browser/trunk/status/explicit-failures-mar… Aside from the specifics in the ticket, the following problems jump out at me just from looking at that XML: * even on compilers that do support nonstandard calling conventions, failures in these tests will never be flagged as problematic * even on compilers that don't support nonstandard calling conventions, these tests will fail and add useless noise to the chart. I can think of a few general principles and practices that will prevent such problems: * Boost regression tests should test the functionality of code that is expected to work, not to test the capabilities of the platform or C++ implementation. There is a place for capability testing, but it needs to be segregated from regular regression tests somehow. If/when we move to using CMake globally, capability tests should take place in its configure stage. In the meantime, such tests must be kept out of Boost regression testing. * Tests that do not apply to a given compiler or platform should ideally not be run on that compiler. * If we can't find a way to avoid running the test at all, the test should be written to trivially succeed on that compiler or platform. * Test annotation wildcards should be written restrictively so that they only match the compilers/platforms to which they apply. This is probably just a start; I'd like to hear other ideas. I intend that this thread will result in an official Boost policy for test annotation. Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

[review] FSM Second Call for Reviews
by Martin Vuille 04 Sep '08

04 Sep '08

The formal review for Andrey Semashev's Finite State Machines (FSM) library has been running for a week now and continues until the 20th. There have been some lively discussions about the library, but no one has yet entered an explicit yes or no vote. If there are no votes either way, the FSM library submission will be rejected by default. If you wish to review, but don't have time before the review period ends on the 20th, please let me know as it may be possible to extend the review period. And, finally, a reminder to include an explicit "for" or "against" vote in your review. ----------- The documentation (overview and reference) is available online: http://boost-extension.redshoelace.com/docs/boost/fsm/doc/state_machine.html http://boost-extension.redshoelace.com/docs/boost/fsm/doc/reference.html The current submission is available from the sandbox vault at http://tinyurl.com/yjozfn (or http://www.boostpro.com/vault/index.php?action=downloadfile&filename=FSM.zip &directory=&PHPSESSID=48493076c1ea60ae316f7b60f15b9ed1, if you prefer.) There has already been some discussion of the library since the rewiew was first announced: http://www.nabble.com/FSM-Review-Announcement-to18820219.html http://www.nabble.com/FSM-Review-Reminder-to18890305.html ----------- Description ----------- "The main goals of the library are: * Simplicity. It should be very simple to create state machine using this library. * Performance. The state machine infrastructure should not be very time and memory-consuming in order to be applicable in more use cases. * Extensibility. A developer may want to add more states to the existing state machine, and this addition should be relatively safe since it shouldn't interfere with the existing states. The developer should also be able to specify additional transitions and events for the machine with minimum modifications to the existing code." "Boost.FSM vs. Boost.Statechart There is another library in Boost that provides similar functionality: Boost.Statechart. Although it currently covers almost all major Boost.FSM features and provides ones that are not supported in this library, Boost.Statechart is more targeted to creation of big and complex state machines with possibility of distributed development. But this does not come at no price and Statechart has little tools for compile-time programming and does not provide as much run-time performance as Boost.FSM does. So there are main guidelines for users to make a decision between Boost.FSM and Boost.Statechart: [...]" "The following compilers are known to have problems or most likely will have ones: * Microsoft Visual C++ 6.0 and 7.0. Most probably will fail to compile due to lack of partial template specialization support. * Borland C++ Builder 5.5.1 (free version). Fails to compile due to lack of partial template specialization and in-class using declarations support. Some other minor problems also have been noticed. Newer versions of the compiler have not been tested. * OpenWatcom 1.5. Fails to compile due to problems with Boost.MPL code. Newer versions of the compiler have not been tested. * SunPro C++ Compiler 5.5 for Solaris (SPARC). Most likely will show problems with function overload resolution. Newer versions of the compiler have not been tested." The current submission is available from the sandbox vault at http://tinyurl.com/yjozfn (or http://www.boostpro.com/vault/index.php?action=downloadfile&filename=FSM.zip &directory=&PHPSESSID=48493076c1ea60ae316f7b60f15b9ed1, if you prefer.) ---------------------------------- What to include in Review Comments ---------------------------------- Your comments may be brief or lengthy, but basically the Review Manager needs your evaluation of the library. If you identify problems along the way, please note if they are minor, serious, or showstoppers. Here are some questions you might want to answer in your review: What is your evaluation of the design? What is your evaluation of the implementation? What is your evaluation of the documentation? What is your evaluation of the potential usefulness of the library? Did you try to use the library? With what compiler? Did you have any problems? How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Are you knowledgeable about the problem domain? And, finally, every review should answer this question: Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks in advance for your participation in this review. MV

7 26

[1.35.x] Any critical bugfixes?
by David Abrahams 04 Sep '08

04 Sep '08

Hi all, I'm trying to compile a list of critical bugfixes and workaround for users of Boost 1.35.0. I already got this information on Boost.Threads and Boost.Filesystem from their respective maintainers. If anyone knows of further issues I would appreciate hearing about them. The ideal would be to refer me to the changeset in our SVN that addresses the issue, but any information would be most appreciated. Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com

2 1

[iterator] could non-small predicates/functors be stored as boost::optional<T> to avoid double construction?
by Thorsten Ottosen 04 Sep '08

04 Sep '08

Hi, The headline pretty much says it all. Take transform iterator. When the predicate is not trivial, we also have a redundant construction of the object in the end iterator. Maybe that could be removed? best regards -Thorsten

5 8

[math] svn rev 48294 (2008-08-22) breaks gcc 3.2 builds
by Ralf W. Grosse-Kunstleve 04 Sep '08

04 Sep '08

Hi, This svn revision... ------------------------------------------------------------------------ r48294 | johnmaddock | 2008-08-22 05:51:40 -0700 (Fri, 22 Aug 2008) | 1 line Merged changes from sandbox, and regenerated the docs. ------------------------------------------------------------------------ broke our gcc 3.2 builds. (Sorry I couldn't report this earlier; I was out of town.) The minimal reproducer is simply: #include <boost/math/special_functions/atanh.hpp> % g++ -c -Iboost atanh.cpp In file included from boost/boost/math/special_functions/atanh.hpp:24, from atanh.cpp:1: boost/boost/math/special_functions/log1p.hpp:456: new declaration ` template<class T> T boost::math::log1pmx(T)' boost/boost/math/special_functions/math_fwd.hpp:491: ambiguates old declaration `template<class T> boost::math::tools::promote_args<RT, float, float, float, float, float>::type boost::math::log1pmx(T)' % g++ --version g++ (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-20) I can make the error go away with the simple-minded patch below, just to prove that the ifdefed-out code is the only problem for us. I'd be happy to try out ideas for proper workarounds. Ralf Index: boost/math/special_functions/log1p.hpp =================================================================== --- boost/math/special_functions/log1p.hpp (revision 48578) +++ boost/math/special_functions/log1p.hpp (working copy) @@ -451,11 +451,13 @@ return result; } +#if !(defined(__GNUC__) && __GNUC__ == 3 && __GNUC_MINOR__ == 2) template <class T> inline T log1pmx(T x) { return log1pmx(x, policies::policy<>()); } +#endif } // namespace math } // namespace boost

1 0

[iterator] Efficiency of transform_iterator
by Arno Schödl 04 Sep '08

04 Sep '08

Looking at other performance issues with stacked iterators, the fact that transform_iterators, in particular the ones doing calculation and returning by value, may get dereferenced many times and do the same calculation many times over seems bad to me, because it is so different from the behavior of trivial iterators, which are very cheap to dereference. I am sure this has been suggested many times, but why isn't there a cached_transform_iterator that contains an internal cache for its result? The actual calculation would be done in the ctor and after increment/decrement/advance. The cached_transform_iterator must know its end like a filter_iterator, because it must not dereference it. As invariant, the cache could either be always constructed, which saves some checks, but needs the value_type to be cheaply default-constructible, or only if not at end. tranform_iterators running on bidirectional_iterators could still claim that they are random_access, so that when advance is called, they skip N items of the underlying iterator and only do the computation on the destination item. This may be problematic because algorithmic choices may be made based on the traversal category, and performance suffer as a result. I am not sure how much of a problem that would be in practice. It would be nice to do the same for forward_iterators, defining a forward_random_access_traversal category. Arno -- Dr. Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

2 2

Re: [boost] [RFC] Boost library name mangling and Microsoft's 'secure STL' feature.
by Johannes Brunen 04 Sep '08

04 Sep '08

Hello Jurko, "Jurko Gospodnetic" <jurko.gospodnetic(a)docte.hr> schrieb im Newsbeitrag news:<g9neff$v6f$1(a)ger.gmane.org>... > First some collected background information related to Microsoft's > checked & debugging iterator support to get a clearer image of what we > are modeling. And could someone please collect a similar summary for > other compilers/libraries? Below you can find a excerpt of the stlports user config file. I do not use the stlport so maybe someone else can give more profound info. > Now the design summaries in order of preference. Note that the list > is a 'work in progress' and the ordering and the 'importance' are based > on my own personal choices and current understanding of all the feedback > received so far. Feel free to holler if you do not agree with them and > I'll update as needed. Currently, I favor design B. > -------- > Design B > -------- > Improved version of the originally suggested 'Design A' allowing for > debugging iterators and making the features msvc toolset specific, > although the exact implementation described here is based on the msvc > compiler documentation: > > Feature: <checked-iterators> > 'on' --> _SECURE_SCL=1 > 'off' (default) --> _SECURE_SCL=0 > > Name mangling: <checked-iterators> adds 'c' to library name if > enabled (assuming it's applicable). > > Feature: <debugging-iterators> > 'on' --> _HAS_ITERATOR_DEBUGGING defined > 'off' (default) --> _HAS_ITERATOR_DEBUGGING not defined > > <runtime-debugging>off & <debugging-iterators>on are incompatible. > > Name mangling: <debugging-iterators> adds 'e' to library name if > enabled (assuming it's applicable). > * We really need to mangle library names to make it clear which > libraries have checked/debugging iterators enabled and which do not, at > for those compiled with MSVC, as these options produce binary > incompatible libraries. This can be done by either adding new tag > letters for these features... Yes > * All this will affects only code compiled using MSVC compiler > versions 8.0 & above. It may also affect other non-MSVC toolsets as we > get more information on them. Stlport gives also additional support for checking. Greetings, Johannes P.S.: Excerpt from the STLport user-config.h file responsible for configuration of the library. I did take all entries which might be relevant in the context. /* * Set _STLP_DEBUG to turn the "Debug Mode" on. * That gets you checked iterators/ranges in the manner * of "Safe STL". Very useful for debugging. Thread-safe. * Please do not forget to link proper STLport library flavor * (e.g libstlportstlg.so or libstlportstlg.a) when you set this flag * in STLport iostreams mode, namespace customization guaranty that you * link to the right library. */ #define _STLP_DEBUG 1 /* * You can also choose the debug level: * STLport debug level: Default value * Check only what the STLport implementation consider as invalid. * It also change the iterator invalidation schema. * Standard debug level: Check for all operations the standard consider as "undefined behavior" * even if STlport implement it correctly. It also invalidates iterators * more often. */ #define _STLP_DEBUG_LEVEL _STLP_STLPORT_DBG_LEVEL #define _STLP_DEBUG_LEVEL _STLP_STANDARD_DBG_LEVEL /* When an inconsistency is detected by the 'safe STL' the program will abort. * If you prefer an exception define the following macro. The thrown exception * will be the Standard runtime_error exception. */ #define _STLP_DEBUG_MODE_THROWS /* * Use this option to catch uninitialized members in your classes. * When it is set, construct() and destroy() fill the class storage * with _STLP_SHRED_BYTE (see below). * Note : _STLP_DEBUG and _STLP_DEBUG_ALLOC don't set this option automatically. */ #define _STLP_DEBUG_UNINITIALIZED 1 #define _STLP_DEBUG_ALLOC 1 /* * Uncomment and provide a definition for the byte with which raw memory * will be filled if _STLP_DEBUG_ALLOC or _STLP_DEBUG_UNINITIALIZED is defined. * Choose a value which is likely to cause a noticeable problem if dereferenced * or otherwise abused. A good value may already be defined for your platform. */ #define _STLP_SHRED_BYTE 0xA3 ____________ Virus checked by G DATA AntiVirusKit Version: AVK 19.305 from 04.09.2008 Virus news: www.antiviruslab.com

1 0

[regex] Build with ICU broken
by Jürgen Hunold 04 Sep '08

04 Sep '08

Hi ! It seems that building Regex with ICU support is broken because of http://svn.boost.org/trac/boost/changeset/48454 compiling on SuSE 11.0 results in the attached error message. It seems that Boost.Build does not evaluate the added dependency. I crosspost to Boost.Build because I'm not sure if this is supposed to work or not. Or if anyone has a better idea. The regression table fro regex is green because obviously no one is using ICU in regression testing. I only use it to minimize the annoying startup messages from Boost.Build... Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 2

[exception] missing public header files in SVN
by vicente.botet 04 Sep '08

04 Sep '08

Hi Emil, What is going on the Boost.Exception library SVN repository? The following 1.36.0 public header files are missing: * boost/exception/enable_current_exception.hpp * boost/exception/enable_error_info.hpp Vicente --------------------------- Vicente Juan Botet Escriba

2 1

[dataflow][review] facilities for creating generic components
by Stjepan Rajko 04 Sep '08

04 Sep '08

Hello, I updated the Dataflow documentation with some examples showing how to create generic (in the sense that they can be used with a number of signal signatures) components for Dataflow.Signals with the help of some provided class templates. These class templates are applicator, conditional, instantiator, and modifier (there is also a conditional_modifier which is not documented, but it basically provides functionality of both conditional and modifier). The updated docs (with examples) are uploaded to: http://www.dancinghacker.com/code/dataflow/ You will find the mentioned class templates in the Components subsection of the Dataflow.Signals section. For example, the modifier documentation shows how to easily build a generic multiplier component, which will multiply each argument of the passing signal by a specified factor. The component could then be used as follows: { signals::storage<void (int, double)> result; multiplier<void (int, double)> multiply_by_3 (3); // result will store the result of the multiplication multiply_by_3 >>= result; multiply_by_3(1, 1.5); BOOST_ASSERT(result.at<0>() == 3); BOOST_ASSERT(result.at<1>() == 4.5); } { signals::storage<void (float, int, double)> result; multiplier<void (float, int, double)> multiply_by_half (0.5); // result will store the result of the multiplication multiply_by_half >>= result; multiply_by_half(1.0f, 9, 9.0); BOOST_ASSERT(result.at<0>() == 0.5f); BOOST_ASSERT(result.at<1>() == 4); BOOST_ASSERT(result.at<2>() == 4.5); } Note that without this facility, building such a generic multiplier would be somewhat involved (unless you are using variadic templates). Stjepan

1 0

min function that accepts any number of arguments
by Peng Yu 03 Sep '08

03 Sep '08

Hi, std::min accepts only two arguments. When I have more than two arguments to compare, it becomes inconvenient. I'm wondering it is possible to added a min function that accepts any number of arguments in the future version of boost? Thanks, Peng

5 5

[1.36.0, date_time] boost/date_time/compiler_config.hpp not copied by install?
by Stefan Heinzmann 03 Sep '08

03 Sep '08

Hi all, when building boost 1.36.0 on Windows using VS2008 SP1 I found that the file boost/date_time/compiler_config.hpp was not copied to the install target directory tree. Can anybody confirm this or have I made a mistake? Cheers Stefan __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com

1 0

[string _algo library] warning/issues under visual c++ 8
by Sean Farrow 03 Sep '08

03 Sep '08

Hi: When using the string algo library func tion is_any_of, I get the following warning under visual c++: c:\program files\boost\boost_trunk\boost/algorithm/string/detail/classification.hpp (102) : warning C4996: 'std::copy': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' Could secure warnings be turned off, or could we potentially look int o using checked iterators with visual c++? Also, I get the following isues: c:\program files\boost\boost_trunk\boost/algorithm/string/classification.hpp(206) : see reference to function template instantiation 'boost::algorithm::detail::is_any_ofF::is_any_ofF>(const RangeT &)' being compiled with [ CharT=char, IteratorT=const char *, RangeT=boost::iterator_range ] Is this something I should worry about, what does this mean? Any help apreciated. Sean. __________ Information from ESET NOD32 Antivirus, version of virus signature database 3406 (20080902) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 1

Re: [boost] Try-out Adler-32 code?
by Bram Neijt 02 Sep '08

02 Sep '08

That should be ok then. The RFC states: """The MD5 algorithm is being placed in the public domain for review and possible adoption as a standard."""" So there should be no problem then. I had problems with the code I used was to much of a "derived work", which ment: """License is also granted to make and use derivative works provided that such works are identified as "derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or referencing the derived work.""" I'm no lawyer but I think you are in the clear then :D Bram On Tue, 2008-09-02 at 04:42 -0400, Daryle Walker wrote: > I didn't take the implementation from any of the MD5 sources lying > around, I did a "clean room" build from the RFC's description. > (They're all byte-wise, while mine is bit-wise [the only one, > AFAIK].) I did use the RFC's sample code to get the values of the > various constants. Do I need to have some sort of licensing with the > RFC board; aren't they free for all?

3 3

[serialization] generic runtime helpers
by JOAQUIN M. LOPEZ MUÑOZ 02 Sep '08

02 Sep '08

Hello, The section on proposed case studies for Boost.Serialization talks about the poosible inclusion of a so-called "generic runtime helper": http://tinyurl.com/6khxns http://www.boost.org/doc/libs/1_36_0/libs/serialization/doc/new_case_studie… which subject I had the pleasure to discuss with Mr. Ramey some time ago. I've got a couple of questions regarding this feature: 1. Is there any tentative release version for getting this included? 2. Is the idea to include the generic runtime helper as part of the core API of an Archive, or will it be just an adaptor? In other words, would the core "Saving Archive" and "Loading Archive" concpets be extended to also feature this runtime helper? FWIW, I'm strongly in favor of having the runtime helper be part of the core Archive concepts: it is my stance that this can be incredibly useful to implement serialization code for types with special lifetime semantics (as is the case with boost::shared_ptr and boost::flyweight) without violating the encapsulation either of the type or of Boost.Serialization. The key and only property of such a runtime helper is its ability to associate an Archive object with a type-dependent helper object, which I see as a very modest, yet highly useful, extension to the Archive concept. Just to exemplify how useful helpers can be, allow me to sketch the serialization process of flyweight<T> as implemented with runtime helpers: * Saving: the helper<flyweight<T> > is just a bag of flyweight<T>s whose elements are *exemplars*. when saving a new flyweight, first we check whether an equivalent flyweight is already present in the helper: if so, the index of the exemplar is output, otherwise, the underlying T associated to the flyweight is saved and the flyweight is added to the helper as a new exemplar. * Loading: again the helper is a bag of flyweight<T>s. When loading a flyweight<T>, we can read either an index or a T object: in the former case we just initialize the flyweight with the corresponding exampler; in the latter case we load the T object, construct a flyweight from it, add it as new exemplar and initialize the loading flyweight with it. This implementation is totally non-intrusive and maximally efficient. An observant reader will also notice that it can be translated almost literally to a serialization scheme for shared_ptr, which shows the potential of the runtime helper feature. Currently, shared_ptr serialization relies on a non-documented adhoc helper, which technically makes it a non-serializable type: promoting the runtime helper to the Archive concept would allow to make shared_ptr a first-class citizen. I also think more types can benefit from this feature when implementing their serialization code. Valid concerns may be raised that extending the Archive concept would break backwards compatibility. However, it is easy to help programmers migrate their user-defined archives to the new concept: just provide a mix-in base class implementing the required functionality, so that if class my_archive { }; models the original Archive concept, just adding the following: class my_archive: public boost::archive::runtime_helper_impl { }; would automatically make my_archive model the new concept. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[iostreams][trunk] patch for msvc 7.1 error
by David Walthall 02 Sep '08

02 Sep '08

The following patch fixes the mapped_file_test compilation error for msvc 7.1 (daw-msvc71): Index: libs/iostreams/src/mapped_file.cpp =================================================================== --- libs/iostreams/src/mapped_file.cpp (revision 48407) +++ libs/iostreams/src/mapped_file.cpp (working copy) @@ -434,7 +434,7 @@ void mapped_file_source::close() { pimpl_->close(); } -mapped_file_source::operator safe_bool() const +mapped_file_source::operator mapped_file_source::safe_bool() const { return pimpl_->error() ? &safe_bool_helper::x : 0; } bool mapped_file_source::operator!() const David PS Is this the right place to post patches? Should I use Trac instead?

2 2

function with const parameters (MSVC 7.1)
by Bernd Martin Wollny 02 Sep '08

02 Sep '08

Hello, I Tried to build a function Map. This is working for my. But if I change the function Parameter to const MSVC 7.1 failed to build. I am using boost 1.35 With gcc 4.3.1 i can compile it. Have some one a solution for me ? ##### source ##### #include <string> #include <map> #include <iostream> #include <boost/function.hpp> typedef boost::function<unsigned int (const bool)> measure_func; class X { public: X(void); unsigned int Exec(const std::string s,const bool b); protected: unsigned int f1(const bool b); unsigned int f2(const bool b); std::map<const std::string,measure_func> measure_map; }; X::X(void) { measure_map["1"]=std::bind1st(std::mem_fun(&X::f1), this); measure_map["2"]=std::bind1st(std::mem_fun(&X::f2), this); } unsigned int X::f1(bool b) { std::cout << "f1: " << b << std::endl; return 1; } unsigned int X::f2(bool b) { std::cout << "f2: " << b << std::endl; return 2; } unsigned int X::Exec(const std::string s,const bool b) { measure_func executer = measure_map[s]; if ( executer ) { return executer(b); } return 0; } // int main(int argc, char* argv[] ) // gcc main int _tmain(int argc, _TCHAR* argv[]) //VC main { X x; unsigned int n=x.Exec("1",true); std::cout << n << std::endl; return 0; } ####### MSVC 7.1 output ##### c:\Programme\Microsoft Visual Studio .NET 2003\Vc7\include\functional(278) : error C2535: 'std::binder1st<_Fn2>::result_type std::binder1st<_Fn2>::operator ()(const std::binder1st<_Fn2>::argument_type &) const' : member function already defined or declared with [ _Fn2=std::mem_fun1_t<unsigned int,X,const bool> ] c:\Programme\Microsoft Visual Studio .NET 2003\Vc7\include\functional(272) : see declaration of 'std::binder1st<_Fn2>::operator`()'' with [ _Fn2=std::mem_fun1_t<unsigned int,X,const bool> ] d:\Devel\test\Boost_test\Bind\Bind.cpp(29) : see reference to class template instantiation 'std::binder1st<_Fn2>' being compiled with [ _Fn2=std::mem_fun1_t<unsigned int,X,const bool> ] -- Bernd Martin Wollny TRIOPTICS GmbH - www.trioptics.com b.wollny(a)trioptics.com Hafenstrasse 39, 22880 Wedel/GERMANY Software Designer Geschäftsführer: Dipl.-Ing. Eugen Dumitrescu phone / fax: +49 (0)4103 18006-26 /-20 Amtsgericht Pinneberg HRB 3215

2 2

Re: [boost] install boost_1_34_1 on fedora (keren hochman)
by 兴冯 02 Sep '08

02 Sep '08

Dear keren hochman: i think you might make the wrong command path.If you take care you may notice the path of bjam in your make error is "./tools/jam/src//bjam", see too slash before bjam. Hava a nice day:) boost-request(a)lists.boost.org 写道： Send Boost mailing list submissions to boost(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.boost.org/mailman/listinfo.cgi/boost or, via email, send a message with subject or body 'help' to boost-request(a)lists.boost.org You can reach the person managing the list at boost-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost digest..." The boost archives may be found at: http://lists.boost.org/MailArchives/boost/ Today's Topics: 1. install boost_1_34_1 on fedora (keren hochman) 2. Re: [log] filtering performance (Andrey Semashev) 3. Re: [interprocess][process] Synchronizing libraries and efforts (+ bugs) (Ion Gazta?aga) 4. Re: [interprocess][process] Synchronizing libraries and efforts (+ bugs) (Ion Gazta?aga) ---------------------------------------------------------------------- Message: 1 Date: Mon, 1 Sep 2008 18:10:21 +0300 From: "keren hochman" Subject: [boost] install boost_1_34_1 on fedora To: boost(a)lists.boost.org Message-ID: <290181000809010810t4752a609s536c965814f9f504(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Im trying to install boost_1_34_1 on fedora (reference to http://www.boost.org/doc/libs/1_36_0...-boost-library ) But after make install i receive the following error message: bin/sh: ./tools/jam/src//bjam: No such file or directory Not all Boost libraries built properly. Could anyone advise me ? ------------------------------ Message: 2 Date: Mon, 01 Sep 2008 19:25:25 +0400 From: Andrey Semashev Subject: Re: [boost] [log] filtering performance To: boost(a)lists.boost.org Message-ID: <48BC0965.5040904(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Igor Nazarenko wrote: > It seems that the library does quite a bit of work before filtering > away a record, unless the logging is turned off entirely. There's at > least two mutex locks, some memory allocation, etc. Callgrind claims > ~2500 instructions when the record is thrown away by the global > severity filter. Shortened callgrind output is in-line below; full > output and the test program attached. Compiled by gcc 4.2.3 using > boost.build variant=release threading=multi. Although I didn't extensively profile the code, I believe that is quite possible. ------------------------------ Message: 3 Date: Mon, 01 Sep 2008 17:44:56 +0200 From: Ion Gazta?aga Subject: Re: [boost] [interprocess][process] Synchronizing libraries and efforts (+ bugs) To: boost(a)lists.boost.org Message-ID: <48BC0DF8.10804(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Boris wrote: >> -> Using named pipes has been problematic because it returns errors >> when launching multiple processes aggressively: Error 231 - All Pipes >> are Busy. This does not happen with anonymous pipes and I think it has >> some relationship with the guid code. By the way, I think a uuid >> library is too much to create a unique identifier to be shared with >> the child a simple atomic count would to the job in my opinion. That >> would reduce Boost.Process dependencies. > > An atomic count might not be sufficient as it would be unique only per > process. As I used Boost.Uuid only for convenience though I'll replace > it with an atomic count plus a random number to drop the dependency. The PID of the parent plus an atomic count wouldn't be enough? >> -> systembuf::close() should call sync() to push the last charaters >> into the pipe, othewise, characters are lost if the user does not >> flush the stream. > > Changed (in postream::close()). I think we must change this in systembuf, because a user might use the streambuf directly and it would be surprised to see that unlike std::filebuf, already written characters are missed. Regards, Ion ------------------------------ Message: 4 Date: Mon, 01 Sep 2008 17:52:52 +0200 From: Ion Gazta?aga Subject: Re: [boost] [interprocess][process] Synchronizing libraries and efforts (+ bugs) To: boost(a)lists.boost.org Message-ID: <48BC0FD4.8010200(a)gmail.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Boris wrote: > On Sun, 31 Aug 2008 23:20:10 +0200, Ion Gazta?aga > wrote: > >> [...]I understand async I/O should be tied with ASIO. I think >> Boost.Iostreams > > To give you an idea how asynchronous I/O with Boost.Process and > Boost.Asio currently looks like: > > boost::process::child child; // somehow launched > #if defined(_WIN32) > boost::asio::windows::stream_handle out(io_service, > child.get_stdin().handle().release()); > boost::asio::windows::stream_handle in(io_service, > child.get_stdout().handle().release()); > #else > boost::asio::posix::stream_descriptor out(io_service, > child.get_stdin().handle().release()); > boost::asio::posix::stream_descriptor in(io_service, > child.get_stdout().handle().release()); > #endif > in.async_read_some(...); I don't know ASIO but it's a shame that it does not offer a portable interface for async I/O. >> [...]I can wait ;-) Since you are working hard on the library, I think >> it's better to wait until you consider the library mature enough. Feel >> free to contact me if you have any question. > > OK, I'll tell you once I'm done (as I said I expect until mid > September). The code is nearly done. But with all the changes which I > had to merge I definitely need to update the documentation and samples. Ok. > By the way, I would be very interested in a communication channel > between a parent and a child process based on Boost.Interprocess. I need > asynchronous I/O though. Before I picked up Boost.Process I had created > a Boost.Asio extension boost::asio::shared_memory which can be used like > boost::asio::socket. The only (but big :) problem I haven't solved yet > is how to handle more than one communication channel. As read/write > operations in Boost.Interprocess need to be synchronized the calls might > block. A parent process with many children will then have to use at > least one thread per child. What would be required is a demultiplexer > which would work like select() for file descriptors. Then I think > asynchronous I/O could be done with Boost.Interprocess. The question is > though what would that demultiplexer look like? You are not working on > supporting asynchronous I/O in Boost.Interprocess? ;) I don't have much idea about async I/O but we can try to write something once we know what we need. I might be completly wrong but boost::interprocess::shared_memory_object is based on a file descriptor (shm_open in unix and a plan file on windows) so we can just obtain the handle and see if select() and WaitForMultipleObject() work on them. After all, write() should work on UNIX with a shared memory object descritor. Regards, Ion ------------------------------ _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost End of Boost Digest, Vol 2293, Issue 3 ************************************** --------------------------------- 雅虎邮箱，您的终生邮箱！

2 1

New user: ld: library not found for -lboost_python
by Michel Valstar 02 Sep '08

02 Sep '08

Hi, I've recently acquired a Mac and I'm trying to port some software to it. The program I want to port uses scons as a build tool. Scons seems to work fine, however, somewhere during compilation I get the following error: ld: library not found for -lboost_python collect2: ld returned 1 exit status scons: *** [trackerbase/libtrackerbasewrapper.dylib] Error 1 scons: building terminated because of errors. I had build the binaries from source using sudo ./configure --with-libraries=python sudo make sudo make install It seems a library linking problem, but I'm not sure how to tackle this. Any suggestions? -- Dr. Michel Valstar, Research Associate http://www.doc.ic.ac.uk/~mvalstar <http://www.doc.ic.ac.uk/%7Emvalstar> Department of Computing Imperial College London 180 Queens' Gate London SW7 2AZ, U.K. tel.: +44 20 7594 8225 fax: +44 20 7581 8024

2 1

[flyweight] making the post-review version of Boost.Flyweight work with Boost 1.36
by JOAQUIN M. LOPEZ MUÑOZ 02 Sep '08

02 Sep '08

Hello, The recently announced post-review version of Boost.Flyweight depends on some material (boost::swap) that is present in Boost SVN trunk but has not been officially released yet. To make Boost.Flywewight work with Boost 1.36, you just have to add the missing material to your local Boost directory. This material is packed for your convenience in a file named flyweight_compatibility_pack_1_36.zip located at the Vault: http://tinyurl.com/hrdm6 http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… Best regards, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Re: [boost] Boost 1.36.0 release notes missing Circular Buffer changes
by Jan Gaspar 02 Sep '08

02 Sep '08

Yes, that's true. Not sure it is possible at this stage when Boost 1.36 has been released but all will be OK in the next version. Jan ----- Original Message ---- From: Dean Michael Berris <mikhailberis(a)gmail.com> To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> Sent: Monday, 1 September, 2008 9:25:49 Subject: [boost] Boost 1.36.0 release notes missing Circular Buffer changes Hi, I took a look at the code in trunk and in 1.36.0, and I notice the release notes don't mention the change in behavior of Boost.Circular_Buffer WRT the default constructor. Should we add: Circular Buffer: * default constructor now doesn't allocate memory, and sets the capacity of the buffer to 0 To the 1.36 release notes? -- Dean Michael C. Berris Software Engineer, Friendster, Inc. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

5 6

Error compiling date_time with Sun Studio 11 on Solaris 8
by ow 02 Sep '08

02 Sep '08

Am getting the following error(s) when trying to include "boost/date_time/local_time/local_time.hpp" on the sun platform. Same code compiles ok on linux and windows. Error, nomatchoverin: Could not find a match for std::has_facet<std::Facet>(std::locale) needed in boost::gregorian::operator<<<char, std::char_traits<char>>(std::ostream &, const boost::gregorian::date&). Can anyone help ? -- View this message in context: http://www.nabble.com/Error-compiling-date_time-with-Sun-Studio-11-on-Solar… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1