- Boost-users - lists.preview.boost.org

Regex: option for case insensitive match
by Kiran Reddy 11 Aug '05

11 Aug '05

Hello, I need to make an case insensitive match using regex_match() algorithm. How do I specify that? Thanks in advance. Regards Kiran

3 2

boost::test in 1.33
by Serge Skorokhodov 11 Aug '05

11 Aug '05

Hi, What happend with boost::unit_test::register_exception_translator? I couldn't track it in the boost 1.33:( How to register custom exceptions? The documentation provides no hints:( TIA -- Serge

2 7

problems using overloaded output operator with program_optoins::optoins_description in debug mode vc++ 7.1
by stark 11 Aug '05

11 Aug '05

Hi I'm trying to use the program_options header to satisfy my command line needs, and I have have run into the following quirk with boost version 1.32 and microsoft visual c++ 7.1 when trying to use 'cout<<' to output the program_options::options_description. Appartently there is a limit to the length of the program option name. When not specifying short optoins names, the option name seems to be limited to 12 characters. greater than this and I get a debug assertion failure in dbgheap.c line 1132 expression: _CrtIsValidHeapPointer(pUserData) . When specifying a short option name, the limit for the full name seems to be 6 characters. More than this results in a debug assertion falure in debug mode (msvc++ 7.1, file dbgdel.cpp, line 52) _BLOCK_TYPE_IS_VALID(pHead->nBlockUse). Is there something I can do to to fix this or work around the problem (besides restricting the length of my option names)? Is this a compiler specific problem? Something wrong with my settings? many thanks, Glen Stark

2 1

Prombles compiling 1.33 RC1 with Intel C++ 8.1 on Windows XP
by Sean Huang 11 Aug '05

11 Aug '05

BlankI'm having problems compiling signals library 1.33 RC1 with Intel C++ 8.1. Looks like it only happens when building dll version of signals library. Eveything else compiles fine. It also compiles with VC7.1. I have set the following environment variables: set TOOLS=intel-win32-8_1 set INTEL_BASE_MSVC_TOOLSET=vc-7_1 set INTEL_PATH="c:\Program Files\Intel\CPP\Compiler80\Ia32" set INTEL_VERSION=8.1 The command line I use is bjam "--builddir=D:\Boost_Build\1_33_0" stage. The intel compiler version is: W_CC_PC_8.1.030 I got error messages like the following: vc-C++ D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj named_slot_map.cpp C:\Program Files\boost_1_33_0\boost/iterator/iterator_facade.hpp(529): error: class "boost::signals::detail::named_slot_map_iterator" has no member "decrement" f.decrement(); ^ detected during: instantiation of "void boost::iterator_core_access::decrement(Facade &) [with Facade=boost::signals::detail::named_slot_map_iterator]" at line 682 instantiation of "Derived &boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::operator--() [with Derived=boost::signals::detail::named_slot_map_iterator, Value=boost::signals::detail::connection_slot_pair, CategoryOrTraversal=boost::forward_traversal_tag, Reference=boost::signals::detail::connection_slot_pair &, Difference=ptrdiff_t={int}]" C:\Program Files\boost_1_33_0\boost/iterator/iterator_facade.hpp(547): error: class "boost::signals::detail::named_slot_map_iterator" has no member "advance" f.advance(n); ^ detected during: instantiation of "void boost::iterator_core_access::advance(Facade &, Facade::difference_type) [with Facade=boost::signals::detail::named_slot_map_iterator]" at line 695 instantiation of "Derived &boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::operator+=(boost::iterator_facade<Derived, Value, CategoryOrTraversal, Reference, Difference>::difference_type) [with Derived=boost::signals::detail::named_slot_map_iterator, Value=boost::signals::detail::connection_slot_pair, CategoryOrTraversal=boost::forward_traversal_tag, Reference=boost::signals::detail::connection_slot_pair &, Difference=ptrdiff_t={int}]" CALL "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\ICLVARS.BAT" > nul "c:\Program Files\Intel\CPP\Compiler80\Ia32\bin\icl" /Zm800 -nologo /EHsc -c -DBOOST_SIGNALS_DYN_LINK=1 -DBOOST_SIGNALS_NO_LIB=1 /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /DBOOST_ALL_NO_LIB=1 /wd4675 /Zc:forScope /Zc:wchar_t /Qwn5 /Qwd985 /Qwe556 -Qoption,c,--arg_dep_lookup /Qansi_alias /Qvc7.1 -D_NATIVE_WCHAR_T_DEFINED -I"D:\Boost_Build\1_33_0\bin\boost\libs\signals\build" -I"C:\Program les\boost_1_33_0" -Fo"D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj" -Tp"C:\Program Files\boost_1_33_0\libs\signals\build\../src/named_slot_map.cpp" ..failed vc-C++ D:\Boost_Build\1_33_0\bin\boost\libs\signals\build\boost_signals.dll\intel-win32-8_1\debug\threading-multi\named_slot_map.obj...

4 8

tribool question
by Serge Skorokhodov 11 Aug '05

11 Aug '05

Hi, I'm using boost::logic::tribool for expressing logical flags that may be nulls by their nature (patient not asked, he/she doesn't know etc.). Default initialization to 'false' seems to be quite unnatural in this context and initialization to 'undetermined' seems to be prefered. Is any significant reason for boost::logic::tribool default constructor initializing the value to 'false'? TIA -- Serge

7 12

numeric/interval overflow & test_float failures
by Steven Solie 11 Aug '05

11 Aug '05

I really don't understand the following math library test failures (Boost 1.32.0): 1) test_float.output /Code/boost-os4/libs/numeric/interval/test/test_float.cpp(55): fatal error in "call_test_main": test subset(rIT2, rII) failed 2) overflow.output /Code/boost-os4/libs/numeric/interval/test/overflow.cpp(22): test in(x, y) failed in function: 'void test_one(typename I::base_type, typename I::base_type) [with I = boost::numeric::interval<float, boost::numeric::interval_lib::policies<boost::numeric::interval_lib::rounded_math<float>, boost::numeric::interval_lib::checking_strict<float> > >]' /Code/boost-os4/libs/numeric/interval/test/overflow.cpp(22): test in(x, y) failed in function: 'void test_one(typename I::base_type, typename I::base_type) [with I = boost::numeric::interval<long double, boost::numeric::interval_lib::policies<boost::numeric::interval_lib::rounded_math<long double>, boost::numeric::interval_lib::checking_strict<long double> > >]' I'm using GCC 3.4.4 on AmigaOS PowerPC. First, what do these errors mean in English? Second, any ideas what I could do to get them to pass? Thanks, --Steven

2 1

shared_ptr conundrum
by Timothy Ritchey 11 Aug '05

11 Aug '05

We have been using shared_ptrs pretty successfully throughout our application, but I have run across something that has just completely stumped me. BTW - this is a Windows .NET 2003 + Intel 8.1 compiler compiling in Debug mode on a multi-processor machine (dual Xeon Dell workstation). The code in question is: void Router::routeEnvelope(shared_ptr<Envelope> envelope) { if(!running || !envelope) return; GUID target = envelope->getTo(); if(target == guid) { // PATH 1 // check to see if it is a failure envelope shared_ptr<EnvelopeFailure> envelopeFailure = shared_dynamic_cast<EnvelopeFailure>(envelope); if(envelopeFailure) { // there was a problem sending the original envelope failedEnvelope(envelopeFailure->getFrom()); } // pass it on up the stack envelopeController.injectEnvelope(envelope); } else { // PATH 2 mutex::scoped_lock lock(envelopeQueueMonitor); envelopeQueue.push(envelope); envelopeReady.notify_all(); } } The first envelope that comes in has a guid that matches target, so it takes code path 1. If I comment out both code path 1 and code path 2, the envelope is released properly, and I can see its destructor get called. Here is where it gets strange--if I uncomment anything in code path 2, and only code path 2, I no longer see the envelope get released, even though that code path is not executed at all. I've been doing this testing on an SMP machine. On a UP machine, the program runs fine without any issues. I am at a complete loss. The original envelope object is created in the function that calls this function, and as far as I can tell , is not touched by any other thread in the application. Thanks for any advice. Cheers, tim

2 2

archive stuck?
by Gennadiy Rozental 11 Aug '05

11 Aug '05

I don't see this month messages here: http://lists.boost.org/boost/2005/08/date.php Gennadiy

1 0

Boost 1.33.0 RC2: VS 8.0 / AMD64 Build Patch
by p.klotz＠icoserve.com 10 Aug '05

10 Aug '05

The attached patch fixes a bug in the vc-8_0-amd64 Toolset of Boost 1.33.0 RC2. Best regards, Peter.

3 2

Boost 1.33.0 RC2: Boost.Threads does not link under VC 8.0/AMD64
by p.klotz＠icoserve.com 10 Aug '05

10 Aug '05

Hi Linking of Boost.Threads (Boost 1.33.0 RC2) fails under VC 8.0/AMD64 with the following error: vc-C++ bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\xtime.obj xtime.cpp vc-Link bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.lib Creating library bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt -gd-1_33.lib and object bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc8 0-mt-gd-1_33.exp once.obj : error LNK2019: unresolved external symbol _InterlockedCompareExchange referenced in function "long __cdecl `a nonymous namespace'::compare_exchange(long * volatile,long,long)" (?compare_exchange@?A0x083100d6@@YAJREAJJJ@Z) bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll : fatal error LNK1120: 1 unresolved externals Microsoft (R) Manifest Tool version 6.0.4071.0 Copyright (c) Microsoft Corporation 2004. All rights reserved. mt.exe:general error c101008d:Failed to write the updated manifest to the resource of file "bin\boost\libs\thread\build\ boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33.dll". The system cannot find the file s pecified. CALL "C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\amd64\vcvarsamd64.BAT" >nul "C:\Program Files (x86)\Microsoft Visual Studio 8\Common7\Tools\..\..\VC\bin\amd64\link" /nologo /INCREMENTAL:NO / DEBUG /DLL /subsystem:console /out:"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\bo ost_thread-vc80-mt-gd-1_33.dll" /IMPLIB:"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-mult i\boost_thread-vc80-mt-gd-1_33.lib" @"bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-mult i\boost_thread-vc80-mt-gd-1_33.CMD" mt -manifest bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd -1_33.dll.manifest -outputresource:bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boos t_thread-vc80-mt-gd-1_33.dll;#2 ...failed vc-Link bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-g d-1_33.dll bin\boost\libs\thread\build\boost_thread.dll\vc-8_0-amd64\debug\threading-multi\boost_thread-vc80-mt-gd-1_33. lib... ...failed updating 1 target... ...updated 682 targets... Any help is welcome. Best regards, Peter.

1 0