September 2008 - Boost - lists.boost.org

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

04 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 03 Sep '08

03 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