- Boost - lists.boost.org

[type_traits] please update is_convertible.hpp header in the RC branch
by Boris Gubenko 15 Jan '07

15 Jan '07

The version of boost/type_traits/is_convertible.hpp in RC_1_34_0 branch has wrong conditionalization for HP-UX. It has been fixed in CVS HEAD -- see below. This bug is causing two tests to fail on HP-UX/aCC6 in RC_1_34_0: . is_convertible_test from type_traits library . tr1_is_convertible_test from tr1 library I've confirmed, that with the HEAD version of the header, the two tests above pass (the type_traits library is, actually, becomes green) and using the HEAD version of the header in RC_1_34_0 testing does not introduce any regressions. Please, update boost/type_traits/is_convertible.hpp header in the RC branch with the version in CVS HEAD. As you can see from the attached differences, this bugfix is the only change in this header between CVS HEAD and the RC branch. Thanks, Boris Index: is_convertible.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/type_traits/is_convertible.hpp,v retrieving revision 1.37 retrieving revision 1.38 diff -r1.37 -r1.38 343c343 < #ifndef __HP_aCC --- > #if !BOOST_WORKAROUND(__HP_aCC, < 60700)

2 1

[xpressive] HEAD doc issue
by Vladimir Prus 15 Jan '07

15 Jan '07

At the moment, CVS HEAD has this in lib/xpressive/doc/Jamfile.v2: xml xpressive : xpressive.qbk : <dependency>autodoc ; What is the reason for <dependency>autodoc here? I don't think that the target is used during generation of xpressive.xml, and I also believe that this change breaks doc build. With it, running bjam in that dir does not work. Without it works. I think this problem exists since the change was committed on 22 Oct 2006. Comments? - Volodya

4 13

Re: [boost] [shared_ptr] how does quick_allocator free its memory pool?
by Steven Watanabe 14 Jan '07

14 Jan '07

AMDG > Peter Dimov wrote: > >> > gchen wrote: >> >>> >> But it seems that quick_allocator never free the memory pool (blocks) >>> >> after my program exits, do I miss something? >>> >> > >> > It doesn't. After your program exits, all memory is automatically freed by >> > the OS. There's no need to free it explicitly, except maybe to keep >> > simplistic leak checkers happy. >> > >> Maybe we can have a special allocation function for when the memory might never be freed. void* allocate_potentially_unfreed_memory(std::size_t size) { #ifdef BOOST_SIMPLISTIC_LEAK_CHECKER char* result = static_cast<char*>(::operator new(size + (std::max)(MAXIMUM_ALIGNMENT, 16))); std::strcpy(result, "boost::unfreed"); return(result + (std::max)(MAXIMUM_ALIGNMENT, 16)); #else return(::operator new(size)); #endif } In Christ, Steven Watanabe

1 0

Re: [boost] Warning from share_ptr
by Steven Watanabe 14 Jan '07

14 Jan '07

AMDG "Peter Dimov" wrote: > Avoiding the ... isn't as trivial as it appears. You might want to try > replacing > > inline void sp_enable_shared_from_this( shared_count const & /*pn*/, ... ) > { > } > > with > > struct sp_any_pointer > { > template<class T> sp_any_pointer( T* ) {} > }; > > inline void sp_enable_shared_from_this( shared_count const & /*pn*/, > sp_any_pointer, sp_any_pointer ) > { > } > > for the _MANAGED case and see if it helps. Also, you can make the return type non-void and use sizeof to avoid calling it. struct enable_shared_from_this_t { enable_shared_from_this_t operator,(int); }; typedef char no; struct yes { no dummy[2]; }; no test_sp_enable_shared_from_this(enable_shared_from_this_t); template<class T> yes test_sp_enable_shared_from_this( T const &); template<class T, class Y> void sp_enable_shared_from_this( shared_count const & pn, boost::enable_shared_from_this<T> const * pe, Y const * px ) { if(pe != 0) pe->_internal_weak_this._internal_assign(const_cast<Y*>(px), pn); } struct sp_any_pointer { template<class T> sp_any_pointer( T* ) {} }; inline void sp_enable_shared_from_this( shared_count const & /*pn*/, sp_any_pointer, sp_any_pointer ) { } //inline enable_shared_from_this_t sp_enable_shared_from_this( shared_count const & /*pn*/, ... ); template<class T, class Y> void call_sp_enable_shared_from_this_impl( shared_count const & pn, T const * pe, Y const * px, boost::mpl::true_ ) { sp_enable_shared_from_this(pn, pe, px); } template<class T, class Y> void call_sp_enable_shared_from_this_impl( shared_count const &, T const *, Y const *, boost::mpl::false_ ) { } template<class T, class Y> void call_sp_enable_shared_from_this( shared_count const & pn, T const * pe, Y const * px) { boost::mpl::bool_<sizeof( test_sp_enable_shared_from_this((sp_enable_shared_from_this(pn, pe, px),0)) )==sizeof(yes)> condition; call_sp_enable_shared_from_this_impl(pn, pe, px, condition); } In Christ, Steven Watanabe

1 0

[Report] 25 regressions on RC_1_34_0
by Douglas Gregor 14 Jan '07

14 Jan '07

Boost Regression test failures Report time: 2007-01-14T08:21:02Z 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… 25 failures in 6 libraries concept_check (15) date_time (1) regex (1) test (2) utility (1) wave (5) |concept_check| class_concept_fail_expected: borland-5.6.4 borland-5.8.2 borland-5.8.2 msvc-6.5 msvc-6.5 msvc-7.0 stl_concept_covering: borland-5.8.2 borland-5.8.2 gcc-3.3.6 gcc-3.4.5_linux gcc-3.4.5_linux_x86_64 gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc |date_time| testgenerators: qcc-3.3.5_gpp |regex| regex_regress_threaded: msvc-6.5 |test| prg_exec_fail2: darwin-4.0.1 prg_exec_fail3: cw-9.4 |utility| operators_test: gcc-3.4.5_linux_x86_64 |wave| testwave: darwin-4.0.1 gcc-4.1.1_sunos_i86pc testwave_dll: darwin-4.0.1 gcc-3.3.6 gcc-4.1.1_sunos_i86pc

2 1

[shared_ptr] how does quick_allocator free its memory pool?
by gchen 14 Jan '07

14 Jan '07

I am trying to enable BOOST_SP_USE_QUICK_ALLOCATOR while using shared_ptr, so to make shared_ptr to use quick_allocator to alloc/dealloc memory, But it seems that quick_allocator never free the memory pool (blocks) after my program exits, do I miss something? Or do I need extra step to use quick_allocator? I am using boost cvs head, vs2005, and disabled BOOST_HAS_THREADS (yes, for speed issue, same reason for using quick_allocator), vs2005.

2 2

[Threads] uncoditional scoped lock?
by Sohail Somani 14 Jan '07

14 Jan '07

Hi, Somewhat longer-than-normal-noise follows :) Consider the following pseudo-code which has a race condition: condition g_some_cond; mutex g_condition_mtx; void thread_fn() { { ... // get lock g_some_cond.wait(condition_lock); } // do work } void main_thread() { thread_group grp; // Start all threads and have them wait on the condition for(i in [0,N)) grp.create_thread(&thread_fn); { ... // get lock g_some_cond.notify_all(); // let threads continue } } The race condition is of course that it is possible that not all threads actually start waiting on the condition before notify_all() is called. In this case, it is possible to solve the race condition in two ways: 1) Have the last thread that reaches the condition wait, signal to the main thread 2) Have the main thread checking the condition before notify_all() I don't really like the first case because it requires bi-directional signalling between the threads. Though in my ignorance, I really do consider it the correct solution. The second solution would look something like this: while(true) { scoped_lock cond_lock(g_condition_mtx); // .num_waiting_threads() is made up if(N_EXPECTED_THREADS==g_some_cond.num_waiting_threads()){break;} // release lock } Should the second pattern be encapsulated in the condition object somehow? It is almost like timed_wait(mtx,xt,pred) but there is no timeout. So maybe untimed_wait()? Is there another way to do this? Thanks for your eyes! Sohail

4 6

[Boost-bugs] [ boost-Support Requests-1635211 ] Crash on RH machine with gcc < 3.4
by SourceForge.net 14 Jan '07

14 Jan '07

Support Requests item #1635211, was opened at 2007-01-14 07:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1635211&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: regex Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: John Maddock (johnmaddock) Summary: Crash on RH machine with gcc < 3.4 Initial Comment: The following code crshes with Seg.Fault while running on RH machine (kernel 7.1, compiler gcc-3.3.2) #include <boost/regex.hpp> #include <string> #include <stdlib.h> int main() { boost::regex expression("abc"); boost::match_results<std::string::const_iterator> what; boost::match_flag_type flags = boost::match_default; std::string str("abcabc"); if (regex_search( str, what, expression, flags) == true) { printf ("FOUND\n"); } return 0; } Is it a known issue? Thanks, Genia ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1635211&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[GIL] Update on GIL
by Lubomir Bourdev 14 Jan '07

14 Jan '07

I just wanted to give the list an update regarding GIL. We are still waiting for the review summary from Tom. In the meantime I am making some fairly significant updates and enhancements to GIL, in part based on suggestions during the review. After those updates are complete (within a couple of months) I will upload the latest GIL to the Boost vault. In the mean time we may post incremental updates on GIL's web page at http://opensource.adobe.com/gil We would like to continue using this web page for people who want to get the latest GIL between Boost releases. I am hoping GIL will be included in the release after 1.34.0 (is that 1.35.0 targeted around the end of 2007?) Thanks, Lubomir

4 3

[GIL] Update on GIL
by Tom Brinkman 14 Jan '07

14 Jan '07

I started a small project using GIL and will relay my experiences in my "review summary" shortly. GIL is a very large library with many innovative features for graphics programmers -- its taken me a few months to get my "head" around it -- and I still have much to learn. >> Why GIL cannot be added to the next release 1.34.0 since it has been voted >> in? I was thinking that once a library has been accepted into Boost it is >> good to go. Do you need to add stuff to the docs or do further changes? GIL needs lots of work to make it "boost" friendly, including the documentation, tests, and examples. As GIL is also part of the "Adobe Open Source" library, which has its own documentation standards, hopefully some compromise can be made between the needs of both projects. I've discussed this with Lubomir before "of-list". My opinion is that GIL has the potential to be a very popular library, but the documentation and examples needs to signifigently expanded to include "a getting started guide" and many more samples, similar to boost::spirit, which is the "gold-standard" for boost::libraries in these areas.

1 0