- Boost - lists.boost.org

Cast free NULLs in algorithms
by Michael Marcin 02 Aug '07

02 Aug '07

Hello, I have something like: class A; boost::array<A*,10> the_array; std::fill( the_array.begin(), the_array.end(), NULL ); Which wont compile (at least under Visual Studio 2005) without a cast for NULL... I've had this problem before and decided to try to find an easy cast free expressive solution for it. After a few minutes I came up with: namespace detail { struct null_ptr_impl { template< typename T > operator T* () const { return static_cast<T*>(0); } }; } // end namespace detail const detail::null_ptr_impl null_ptr; std::fill( the_array.begin(), the_array.end(), null_ptr ); Does this exist somewhere already? Is it a good solution? Thanks, Michael Marcin

12 24

[type_traits] missing boost::is_complex<T>
by dherring＠ll.mit.edu 02 Aug '07

02 Aug '07

Whatever happened to boost::is_complex<T>? It looks like the idea was accepted back in 2005, but nobody ever added it to trunk... http://thread.gmane.org/gmane.comp.lib.boost.user/13692/focus=13696 http://svn.boost.org/trac/boost/ticket/492 Thanks, Daniel

1 0

about: tutorial for using boost 'Unit Test Framework'
by Jagsir Singh 02 Aug '07

02 Aug '07

Hi All, I am sure, this might allready be answered here on the list. Is there a simple step by step tutorial for using the Unit Test Framework, and the bjam,(simplest jam file). It will be highly appreciated. Is there a searchable mailing list for boost some place ? in other words, --can you search through the mailing list archives ? -- /*/Jagsir /*/////////////

3 4

[Report] 0 regressions on RC_1_34_0 (2007-08-02)
by Douglas Gregor 02 Aug '07

02 Aug '07

Boost Regression test failures Report time: 2007-07-30T10:21:37Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… No failures! Yay!

1 0

Looking for project
by Sergey Razin 02 Aug '07

02 Aug '07

Hello! My name is Sergey Razin, and it was recommended to me by one of the Boost peoplzz to contact the dev. list on that question. I've e-mailed a few days ago but did not see my topic/request being included in the e-mails, therefore I've decided to try again. As I started to have more free time I would like to contribute it to Boost as a huge fan of C++ as well as Boost user. I was wondering if any of the current Boost projects require help? I will be glad to jump in and help or start a new one as well. I am looking forward to contributing to Boost as well as to help open source community with such a great set of libraries. Thank you! Sergey A. Razin, Ph.D. Software Engineer _________________________________________________________________ See what you’re getting into…before you go there. http://newlivehotmail.com

2 1

[Multi-index] questions on max_size, incomplete docs, and common code
by Daryle Walker 02 Aug '07

02 Aug '07

I'm trying out a multi-indexed container that uses a set-like (ordered_unique) interface and a vector-like (random_access) interface. Each interface has a "max_size" member function. Could they ever return different values? Some functions, like (member) swap and clear, have no definitions given. It seems like the author assumes that we'll assume that the undefined functions work like those in STL. But I'll prefer something more precise, to (1) confirm the exact semantics and (2) know the exact complexity these functions may have. (I noticed this problem while I was trying to define the complexity of my wrapper class's member functions.) Some member functions, like the aforementioned "max_size" and "clear," seem to be same for all index styles. Could those be re-factored into the main class, like "get_allocator" is? Or would that mess up the ability to keep each index's interface independent? -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

2 1

Non-reentrant implementation of data_time/c_time.hpp under MS-Windows VC 8.0
by Alexis Wilke 02 Aug '07

02 Aug '07

Hi guys, In the code below, there are three severe bugs: 1. The addition of the #pragma warning instead of using the localtime_s() and gmtime_s() functions which are similar to the localtime_r() and gmtime_r() functions (the parameters are swapped.) Thus, if _MSC_VER >= 1400, you need a new implementation with the "safe" versions. 2. The documentation says: //! requires a pointer to a user created std::tm struct because the function is expected to WRITE in that buffer. At this time, it does not do so and if you don't use the returned pointer, the pointer to the user defined tm struct is useless. You are missing a couple of asterisks in there! *result = *std::localtime(t); 3. In a multi-thread environment, which you detect with some BOOST_THREAD_ENABLED flag, you must use a scoped lock to protect these calls. Lock, call, return is what I'd expect to see here (is it prohibited for the c_time.hpp file to include the thread lock mechanism?) I hope I will see these three bugs fixed in a future version. Thank you, Alexis Wilke P.S. I tried to post this text to your Trac system and it was rejected by Akismet. According to them, it is spam. #if (defined(_MSC_VER) && (_MSC_VER >= 1400)) #pragma warning(push) // preserve warning settings #pragma warning(disable : 4996) // disable depricated localtime/gmtime warning on vc8 #endif // _MSC_VER >= 1400 //! requires a pointer to a user created std::tm struct inline static std::tm* localtime(const std::time_t* t, std::tm* result) { result = std::localtime(t); return result; } //! requires a pointer to a user created std::tm struct inline static std::tm* gmtime(const std::time_t* t, std::tm* result) { result = std::gmtime(t); return result; } #if (defined(_MSC_VER) && (_MSC_VER >= 1400)) #pragma warning(pop) // restore warnings to previous state #endif // _MSC_VER >= 1400 ------------ Alexis Wilke President Made to Order Software, Corporation e-mail: alexis(a)m2osw.com cell-text: alexis.cell(a)m2osw.com (please, only small messages) Web Pages: http://www.m2osw.com http://www.turnwatcher.com Company e-mail: contact(a)m2osw.com Phone: +(1) 916 220 6482 Fax: +(1) 916 988 1450 Address: 9275 Blue Oak Drive Orangevale, California 95662 United States of America CONFIDENTIAL This document contains non-public proprietary information that is subject to restrictions on use and/or disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this e-mail message in error, please e-mail the sender and delete all copies. Thank you.

1 0

Re: [boost] Boost C++/tcl integration lib
by Maciej Sobczak 01 Aug '07

01 Aug '07

Fanzhe Cui wrote: > On the boost document page it has entry of the library: > C++/Tcl - C++/Tcl is a library that allows the easy integration of C++ and > Tcl. As was already mentioned, C++/Tcl is not a Boost library. It just uses Boost. > But the pkg from ActiveState is not free. It is free: http://www.activestate.com/store/activetcl/ Follow the "Download" link to get the free package. Distributions from ActiveState are probably the most easy way to get Tcl up and running on Windows and I recommend them for use with C++/Tcl. Regards, -- Maciej Sobczak : http://www.msobczak.com/ Programming : http://www.msobczak.com/prog/

2 1

[Accumulators] Passing construction arguments to dependent statistics
by Hugo Duncan 01 Aug '07

01 Aug '07

Given recent discussion on Time Series and Accumulators, I thought I would have a go at implementing a FIR filter for Accumulators, and have run into a problem. I decided to do this in two parts; first create a (reusable) delay statistic (similar to tail) that provides a history buffer for the signal and then create the filter (similar to tail_variate) , that will depend on the delay buffer. I have created the delay buffer with a length determined by a cache_size argument. This works well. I am now creating the filter, which has a "coefficents" argument to set the filter coefficients. I would like to pass the size of the coefficients list as the cache_size argument to the underlying delay buffer. Is this possible?

2 10

[thread_safe_signals] assertion failure (patch)
by Rodolfo Schulz de Lima 01 Aug '07

01 Aug '07

There's a little bug in member function nolock_force_unique_connection_list which causes an assertion inside nolock_cleanup_connections because the _shared_state.unique() is false because the local variable newState also references _shared_state. The attached patch corrects this rather simple bug. Regards, Rodolfo Lima.

1 0