- Boost - lists.preview.boost.org

String Algo bug.
by John Maddock 30 Jul '04

30 Jul '04

There seems to be a bug in the string algorithm library that results in a valid container iterator being compared to a "singular" default constructed iterator: this operation is not supported by the iterator requirements and results in an assertion being thrown when testing with VC7.1+STLPort (or any other compiler with STLPort for that matter). The call stack is: stlport_vc71_stldebug46.dll!_STL::__stl_debug_engine<bool>::_Terminate() Line 324 C++ stlport_vc71_stldebug46.dll!_STL::__stl_debug_engine<bool>::_Assert(const char * __expr=0x0057420c, const char * __f=0x00574180, int __l=0x0000012d) Line 308 C++ regex_test.exe!_STL::operator==<_STL::_Nondebug_string<char,_STL::char_trait s<char>,_STL::allocator<char> > >(const _STL::_DBG_iter_base<_STL::_Nondebug_string<char,_STL::char_traits<char>,_ST L::allocator<char> > > & __x={...}, const _STL::_DBG_iter_base<_STL::_Nondebug_string<char,_STL::char_traits<char>,_ST L::allocator<char> > > & __y={...}) Line 301 + 0x2e C++ regex_test.exe!boost::algorithm::iterator_range<_STL::_DBG_iter<_STL::_Nonde bug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >::operator==<_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits< char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >() Line 119 + 0x47 C++ regex_test.exe!boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondeb ug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >::equal(const boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<char, _STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > & Other={...}) Line 147 + 0x12 C++ regex_test.exe!boost::iterator_core_access::equal<boost::algorithm::find_ite rator<_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_S TL::allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > >() Line 518 C++ regex_test.exe!boost::operator==<boost::algorithm::find_iterator<_STL::_DBG_ iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<cha r> >,_STL::_Const_traits<char> > >,boost::algorithm::iterator_range<_STL::_DBG_iter<_STL::_Nondebug_string<ch ar,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const ,boost::forward_traversal_tag,boost::algorithm::iterator_range<_STL::_DBG_it er<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const &,int,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string <char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::iterator_range<_STL::_DBG_iter<_STL::_Nondebug_string<ch ar,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const ,boost::forward_traversal_tag,boost::algorithm::iterator_range<_STL::_DBG_it er<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const &,int>(const boost::iterator_facade<boost::algorithm::find_iterator<_STL::_DBG_iter<_STL: :_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::iterator_range<_STL::_DBG_iter<_STL::_Nondebug_string<ch ar,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const ,boost::forward_traversal_tag,boost::algorithm::iterator_range<_STL::_DBG_it er<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const &,int> & lhs={...}, const boost::iterator_facade<boost::algorithm::find_iterator<_STL::_DBG_iter<_STL: :_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::iterator_range<_STL::_DBG_iter<_STL::_Nondebug_string<ch ar,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const ,boost::forward_traversal_tag,boost::algorithm::iterator_range<_STL::_DBG_it er<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > > const &,int> & rhs={...}) Line 819 + 0x32 C++ regex_test.exe!boost::iterator_adaptor<boost::transform_iterator<boost::algo rithm::detail::copy_iterator_rangeF<_STL::basic_string<char,_STL::char_trait s<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,boost::algorithm::find_iterator<_ST L::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::alloc ator<char> >,_STL::_Const_traits<char> > >,_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,boost::use_default,_STL::basic_string<char,_STL::char_traits<char>,_STL::a llocator<char> >,boost::use_default>::equal<boost::transform_iterator<boost::algorithm::det ail::copy_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char>,_S TL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,boost::algorithm::find_iterator<_ST L::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL::alloc ator<char> >,_STL::_Const_traits<char> > >,_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,boost::use_default,_STL::basic_string<char,_STL::char_traits<char>,_STL::a llocator<char> >,boost::use_default>() Line 297 + 0x12 C++ regex_test.exe!boost::iterator_core_access::equal<boost::transform_iterator< boost::algorithm::detail::copy_iterator_rangeF<_STL::basic_string<char,_STL: :char_traits<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,boost::transform_iterator<boost::al gorithm::detail::copy_iterator_rangeF<_STL::basic_string<char,_STL::char_tra its<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default> >() Line 518 C++ regex_test.exe!boost::operator!=<boost::transform_iterator<boost::algorithm: :detail::copy_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char >,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,_STL::basic_string<char,_STL::char_ traits<char>,_STL::allocator<char> >,boost::forward_traversal_tag,_STL::basic_string<char,_STL::char_traits<cha r>,_STL::allocator<char> >,int,boost::transform_iterator<boost::algorithm::detail::copy_iterator_rang eF<_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,_STL::basic_string<char,_STL::char_ traits<char>,_STL::allocator<char> >,boost::forward_traversal_tag,_STL::basic_string<char,_STL::char_traits<cha r>,_STL::allocator<char> >,int>(const boost::iterator_facade<boost::transform_iterator<boost::algorithm::detail::c opy_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char>,_STL::al locator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,_STL::basic_string<char,_STL::char_ traits<char>,_STL::allocator<char> >,boost::forward_traversal_tag,_STL::basic_string<char,_STL::char_traits<cha r>,_STL::allocator<char> >,int> & lhs={...}, const boost::iterator_facade<boost::transform_iterator<boost::algorithm::detail::c opy_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char>,_STL::al locator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default>,_STL::basic_string<char,_STL::char_ traits<char>,_STL::allocator<char> >,boost::forward_traversal_tag,_STL::basic_string<char,_STL::char_traits<cha r>,_STL::allocator<char> >,int> & rhs={...}) Line 820 + 0x32 C++ regex_test.exe!_STL::__vector<_STL::basic_string<char,_STL::char_traits<char >,_STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >::_M_range_initialize<boost::transform_iterator<boost::algorithm::detail::c opy_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char>,_STL::al locator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default> >() Line 535 + 0x17 C++ regex_test.exe!_STL::__vector<_STL::basic_string<char,_STL::char_traits<char >,_STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >::_M_initialize_aux<boost::transform_iterator<boost::algorithm::detail::cop y_iterator_rangeF<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default> >() Line 231 C++ regex_test.exe!_STL::__vector<_STL::basic_string<char,_STL::char_traits<char >,_STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >::__vector<_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator< char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > ><boost::transform_iterator<boost::algorithm::detail::copy_iterator_rangeF<_ STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default> >() Line 248 C++ regex_test.exe!_STL::vector<_STL::basic_string<char,_STL::char_traits<char>, _STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >::vector<_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<ch ar> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > ><boost::transform_iterator<boost::algorithm::detail::copy_iterator_rangeF<_ STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_DBG_iter<_STL::_Nondebug_string<char,_STL::char_traits<char>,_STL:: allocator<char> >,_STL::_Const_traits<char> > >,boost::algorithm::find_iterator<_STL::_DBG_iter<_STL::_Nondebug_string<cha r,_STL::char_traits<char>,_STL::allocator<char> >,_STL::_Const_traits<char> > >,boost::use_default,boost::use_default> >() Line 164 + 0x93 C++ regex_test.exe!boost::algorithm::iter_find<_STL::vector<_STL::basic_string<c har,_STL::char_traits<char>,_STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >,_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> > const ,boost::algorithm::detail::find_regexF<boost::reg_expression<char,boost::reg ex_traits<char>,_STL::allocator<char> > > >(_STL::vector<_STL::basic_string<char,_STL::char_traits<char>,_STL::allocat or<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > > & Result={...}, const _STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> > & Input={...}, boost::algorithm::detail::find_regexF<boost::reg_expression<char,boost::rege x_traits<char>,_STL::allocator<char> > > Finder={...}) Line 97 + 0x7e C++ regex_test.exe!boost::algorithm::find_all_regex<_STL::vector<_STL::basic_str ing<char,_STL::char_traits<char>,_STL::allocator<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > >,_STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> >,char,boost::regex_traits<char>,_STL::allocator<char> >(_STL::vector<_STL::basic_string<char,_STL::char_traits<char>,_STL::allocat or<char> >,_STL::allocator<_STL::basic_string<char,_STL::char_traits<char>,_STL::allo cator<char> > > > & Result={...}, const _STL::basic_string<char,_STL::char_traits<char>,_STL::allocator<char> > & Input={...}, const boost::reg_expression<char,boost::regex_traits<char>,_STL::allocator<char> > & Rx={...}, boost::regex_constants::_match_flags Flags=match_default) Line 429 + 0x2b C++ regex_test.exe!find_test() Line 68 + 0x16 C++ regex_test.exe!test_main(int __formal=0x00000001, int __formal=0x00000001) Line 134 C++ regex_test.exe!`anonymous namespace'::call_test_main() Line 37 + 0x12 C++ regex_test.exe!boost::unit_test::function_test_case::do_run() Line 138 + 0x2b C++ regex_test.exe!boost::unit_test::ut_detail::unit_test_monitor::function() Line 77 + 0x14 C++ regex_test.exe!boost::execution_monitor::run_function() Line 188 + 0x54 C++ regex_test.exe!boost::detail::catch_signals(boost::execution_monitor & exmon={...}, bool __formal=true, bool __formal=true) Line 472 C++ regex_test.exe!boost::execution_monitor::execute(bool catch_system_errors=true, int timeout=0x00000000) Line 211 + 0x11 C++ regex_test.exe!boost::unit_test::ut_detail::unit_test_monitor::execute_and_t ranslate(boost::unit_test::test_case * target_test_case=0x009c9990, void (void)* f=0x0047d339, int timeout=0x00000000) Line 43 + 0x13 C++ regex_test.exe!boost::unit_test::test_case::run() Line 145 + 0x6c C++ regex_test.exe!main(int argc=0x00000001, char * * argv=0x009c6bb8) Line 83 C++ And the actual problem I think is caused by (iter_find.hpp#98): transform_iter_type itBegin= make_transform_iterator( find_iterator_type( begin(Input), InputEnd, Finder ), copy_range_type()); transform_iter_type itEnd= make_transform_iterator( find_iterator_type(), // end iterator is default constructed here!! copy_range_type()); SequenceSequenceT Tmp(itBegin, itEnd); // assertion here There may be other occurances of course, this is just the first assertion to be triggered... John.

5 23

RE: [boost] Re: Lock unification [move]
by Batov, Vladimir 30 Jul '04

30 Jul '04

Howard, Thank you for your time to get the spec. together. A must to move forward. A few comments. 1. explicit scoped_lock(mutex_type& m); 2. scoped_lock(mutex_type& m, locking_enum lock_it); 3. scoped_lock(mutex_type& m, blocking_enum block_it); 4. scoped_lock(mutex_type& m, const elapsed_time& elps_time); Do we need (3)? Isn't is covered by (4) with elps_time = INFINITE (blocking) and - 0 (non blocking)? If it is intended as a "convenience" interface, my expectation would be that average users would use thin and more explicit wrappers around the general lock. Like try_lock and timed_lock. Then, those thin wrappers would address the "convenience" issue better. (1) and (2) overlap as (1) is (2) with lock_it = true. Does not it mean that some functionality will have to be duplicated in (1) and (2)? How about avoiding the overlap with 1. explicit scoped_lock(mutex_type& m); 2. scoped_lock(mutex_type& m, deferred_t); Then, every constructor would do just one thing. My 2c. Best, V. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Howard Hinnant > Sent: Sunday, 18 July 2004 2:32 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Lock unification [move] > > I have attempted a specification of moving > scoped_lock/read_lock/upgradable_read_lock/write_lock at: > > http://home.twcny.rr.com/hinnant/cpp_extensions/threads.html > > This is an attempt to look forward to locks+move semantics, taking into > account the recent discussions. Because of the length of the > specification I put it in an html on my personal website instead of > stuffing it into an email. Comments welcome. Any response from me is > likely to be delayed by several days due to travel. > > -Howard > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

8 36

Spirit: Some more regressions
by Joel de Guzman 30 Jul '04

30 Jul '04

Hi, The CVS (Boost) state for Spirit is very good. However, there are still some few regressions remaining. I do not understand some of the reports on compilers that I do not have access to. I wonder if some of you guys can help out. I'd appreciate that a lot. Help might mean as simple as peeking into the reports and forming an educated guess. TIA... <http://www.meta-comm.com/engineering/boost-regression/developer/spirit.html> 1) Comeau: http://tinyurl.com/5h5f6 2) VC8: http://tinyurl.com/3jmem The other errors are either boost.threads errors (still) or similar to the 2 above. I'll inquire about the threads errors in a separate post. Ah, yes, intel- win32- 7.1- vc6- stlport- 4.5.3 has runtime failures (e.g. http://tinyurl.com/4tfq6) Hartmut diagnosed these: <q> These two are easy. The reason for these errors comes from the fact, that the STLPort library is compiled independently from the test application and the command line options, which define, whether the wchar_t is an intrinsic type or not are different for the two compilation units. As a result the wrong std::numeric_limits specialisation gets picked during the compilation of the test program, which at runtime leads to the failed assertion. For a long time it wasn't possible to detect from inside a program (while compiled with the Intel on the Windows platfrom), whether it is compiled with wchar_t as an intrinsic time or not (for the Intel V8 this fact fixed recently), so I don't see a way to fix the problems right now </q> Any ideas, anyone? Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

1 0

Re: Re: Threads Rewrite?
by Tonko Juricic 29 Jul '04

29 Jul '04

Stefan Seefeld wrote: > That's often impossible: objects and threads are > orthogonal by nature: you don't always control what > thread executes your code. But as it is your code > that needs TLS you may have to inject TLS variables > in *any* thread that comes your way, and so it has > to be cleaned up in a uniform way. Let me try to understand it better. We start with the fact that some parts of your code can be executed by both boost and non-boost threads. A stumbling block in my case is understanding how can your code be executed by a non-boost thread unless, at some level, you explicitly make it possible. So, if I didn't completely miss the point, TLS cleanup for non-boost threads is there to spare the programmer from having to analyze complex scenarious and calling sequences which may lead to a non-boost thread visiting the 'unsuspecting' method on your object. Tony __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 3

Algorithm/minmax lib missing copyrights
by John Maddock 29 Jul '04

29 Jul '04

The following files are missing copyrights in the minmax lib: libs/algorithm/minmax/example/minmax_ex.cpp libs/algorithm/minmax/example/minmax_timer.cpp libs/algorithm/minmax/test/minmax_element_test.cpp libs/algorithm/minmax/test/minmax_test.cpp Can the Author please fix? Many thanks, John Maddock.

2 1

[assign][multi_array] possible problem with both libs together?
by JOAQUIN LOPEZ MU?Z 29 Jul '04

29 Jul '04

I thought I'd bring this mail from the users list to your attention: http://lists.boost.org/MailArchives/boost-users/msg07311.php Joaquín M López Muñoz Telefónica, Investigación y Desarrollo Original message To: boost-users@xxxxxxxxxxxxxxx Subject: [Boost-users] Assign and MultiArray conflict with precompiledheaders From: Bruno Martínez Aguerre <br1@xxxxxxxxxxxxxxx> Date: Wed, 28 Jul 2004 16:49:42 -0300 Reply-to: boost-users@xxxxxxxxxxxxxxx Sender: news <news@xxxxxxxxxxxxx> User-agent: Opera M2/7.51 (Win32, build 3798) -------------------------------------------------------------------------------- Hi. I'm trying out the recently accepted Assign library, and also the MultiArray library, which is new to me. I'm in VC7.1, and using the post review version of Assign. Depending on the order I include the libraries in my precompiled header, the linker complains about double definition of MultiArray's extents object. Here are the files that reproduce the problem. //stdafx.h #pragma once #include "boost/multi_array.hpp" #include "boost/assign.hpp" //main.cpp #include "stdafx.h" int main() { boost::multi_array<int, 2> t(boost::extents[3][4]); } I couldn't find relation between the two libraries. Thanks in advance, Bruno Martínez

1 0

Re:Re: Re:Javascript Tree Control [was: Serialization Menu
by Robert Ramey 29 Jul '04

29 Jul '04

Jonathan Turkanis >I agree with all of this. But I think that having a tree control component >is still useful: I didn't mean to suggest otherwise. My experience with this was a) fiddling around with Javascript and DOM (IE and Netscape) to get things to work. b) making my own tree by hand. Basically both of these were hacks and I'm happy to see a) done in a professional way. b) was really tedious and I saw the need to automate this process which seemed very much in the spirit of Boost Book (which I havn't spent any time with either) Basically we've got a) we need a)+b). I'm happy to leave the details to you guys as you know much more about it and it seems that there is broad agreement on the basic idea. Robert Ramey

2 1

Re: [boost] Re: Javascript Tree Control [was: Serialization Menu]
by Reece Dunn 29 Jul '04

29 Jul '04

Jeff Garland wrote: >On Wed, 28 Jul 2004 09:41:22 -0600, Jonathan Turkanis wrote > > "Jeff Garland" <jeff(a)crystalclearsoftware.com> wrote in message > > news:20040728115709.M55567@crystalclearsoftware.com... > > > On Tue, 27 Jul 2004 21:19:38 -0600, Jonathan Turkanis wrote > > > (I was able to do it with right mouse on the right pane, open in new > > > window/tab). However, is there a way to get the address bar to > > point to the > > > right frame instead of the left pane so that the current URL is > > immediately > > > accessible? My major objection to frames is that I can't see and > > grab the > > > current URL... > > > > I agree. See http://tinyurl.com/3sdu6. > >Thanks, for the pointer on sync. I didn't read all the rationale. I wish I >could come up with a more intuitive name -- it didn't hit me at first what >sync was for. Anyway, I was using Firefox 0.9.1 on Linux. I tested a >couple >more browsers: Galeon 1.3.12 and Epiphany 1.0.7 automatically sync -- very >cool! Konqueror 3.2.0 does not :( Would it be possible to do the sync automatically via the JavaScript control? It could be possible to do something like: <a href = "javascript:tree.load('id.1.2')">Chapter 1.2: Cool Stuff!</a> With load performing the URL redirection and synchronisation. I am not sure how portable this would be, but having it done automatically would mean that there would be less confusion and a simpler interface. >Oh, and I'm of course in support of boost-book initiatives to generate >these >capabilties -- after all, transformation to various forms is the whole >point >of getting the docs into xml... Exactly. Regards, Reece _________________________________________________________________ Use MSN Messenger to send music and pics to your friends http://www.msn.co.uk/messenger

2 1

property map, boost::identity_property_map
by Val Samko 29 Jul '04

29 Jul '04

Hi, is there any reason, why boost::identity_property_map implementation in <boost\property_map.hpp> is completely different from how it is documented in http://www.boost.org/libs/property_map/identity_property_map.html ? As mentioned in the implementation, boost::identity_property_map is a property map that applies the identity function to integers. On the other hand, documentation clearly states that one can use identity_property_map with any types. Valentin Samko http://val.samko.info

2 1

BOOST_MPL_AUX_AGLORITHM_NAMESPACE_END in wrong place
by Jonathan Wakely 29 Jul '04

29 Jul '04

In boost/mpl/if.hpp the BOOST_MPL_AUX_AGLORITHM_NAMESPACE_BEGIN macro is inside a test for BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION, but the corresponding BOOST_MPL_AUX_AGLORITHM_NAMESPACE_END is after the #endif that matches the test. This doesn't cause an error, since those macros only expand to anything meaningful for GCC3, which enters the first branch of the #if, so the begin/end macros are balanced - but it ain't right. Bug was found due to an error with missing #endif, which made GCC3 take a different path through that file and error. Note also those macros are spelled "AGLORITHM" not ALGORITHM. Untested patch attached. jon -- "Faith strikes me as intellectual laziness." - Robert Heinlein

2 2