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

regex patches available
by John Maddock 03 May '04

03 May '04

All users of Boost.Regex-1.31.1 should be aware that there are now a set of patches available for this release - see https://sourceforge.net/project/showfiles.php?group_id=7586 for downloads. Issues fixed include: POSIX style regular expressions not behaving correctly with regex_grep. Non-greedy repeats not backtracking correctly in some cases. Backreferences cause some repeat operators to behave incorrectly. Some wide character expressions weren't getting correctly optimised, leading to thrown exceptions in trivial cases. Misc. compiler compatibility fixes. Regards, John Maddock

1 0

Compiling BOOST_1_30_0 UNDER HPUX B.11.11
by Albert Gome 03 May '04

03 May '04

Hi, I am trying to Install BOOST_1_30_0 on HPUX B.11.11 using aCC Version HP ANSI C++ B3910B A.03.33. Fisrtly i tried to build the thread libaray under <BOOST_ROOT>/lib/thread/build using statement bjam -sTOOLS="acc" -sBuild="debug release" I tried thread first because the regex compilation was also giving problems. Though Compiling the threads library result in MkDir1 ../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi aCC-C++-action ../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o Error 19: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # Unexpected 'template'. ::template result_<T> ^^^^^^^^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # '{' expected instead of '<'. ::template result_<T> ^ Error 20: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # '<' expected before '>'. ::template result_<T> ^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 60 # ';' expected instead of '{'. { ^ Error 318: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # A template name was expected instead of 'T'. Did you forget to define the template? ::template result_<T> ^^ Error 263: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # Object expected in declaration list. ::template result_<T> ^^ Error 19: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # Unexpected 'template'. struct enable_if : public enabled<Enabled>::template base<T> ^^^^^^^^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # '{' expected instead of '<'. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 20: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # '<' expected before '>'. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 323 # ';' expected instead of '{'. { ^ Error 419: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # 'T' is used as a type, but has not been defined as a type. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 318: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # A template name was expected instead of '<type inserted by compiler>'. Did you forget to define the template? struct enable_if : public enabled<Enabled>::template base<T> ^ Error 699: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # Error limit reached; halting compilation. struct enable_if : public enabled<Enabled>::template base<T> ^ aCC -AA -c +W823 -I/mnt/r7/apal3/lib/boost_1_30_0 -DBOOST_THREAD_BUILD_DLL=1 -mt -g +Z -I"../../../libs/thread/build" -I"/mnt/r7/apal3/lib/boost_1_30_0" -o "../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o" "../src/condition.cpp" ...failed aCC-C++-action ../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o... Then i downloaded the lates is_functions.hpp from the CVS which again resulted in aCC-C++-action ../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o Error 19: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # Unexpected 'template'. ::BOOST_NESTED_TEMPLATE result_<T> ^^^^^^^^^^^^^^^^^^^^^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # '{' expected instead of '<'. ::BOOST_NESTED_TEMPLATE result_<T> ^ Error 20: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # '<' expected before '>'. ::BOOST_NESTED_TEMPLATE result_<T> ^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 60 # ';' expected instead of '{'. { ^ Error 318: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # A template name was expected instead of 'T'. Did you forget to define the template? ::BOOST_NESTED_TEMPLATE result_<T> ^^ Error 263: "/mnt/r7/apal3/lib/boost_1_30_0/boost/type_traits/is_function.hpp", line 59 # Object expected in declaration list. ::BOOST_NESTED_TEMPLATE result_<T> ^^ Error 19: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # Unexpected 'template'. struct enable_if : public enabled<Enabled>::template base<T> ^^^^^^^^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # '{' expected instead of '<'. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 20: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # '<' expected before '>'. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 24: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 323 # ';' expected instead of '{'. { ^ Error 419: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # 'T' is used as a type, but has not been defined as a type. struct enable_if : public enabled<Enabled>::template base<T> ^ Error 318: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # A template name was expected instead of '<type inserted by compiler>'. Did you forget to define the template? struct enable_if : public enabled<Enabled>::template base<T> ^ Error 699: "/mnt/r7/apal3/lib/boost_1_30_0/boost/function/function_base.hpp", line 322 # Error limit reached; halting compilation. struct enable_if : public enabled<Enabled>::template base<T> ^ aCC -AA -c +W823 -I/mnt/r7/apal3/lib/boost_1_30_0 -DBOOST_THREAD_BUILD_DLL=1 -mt -g +Z -I"../../../libs/thread/build" -I"/mnt/r7/apal3/lib/boost_1_30_0" -o "../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o" "../src/condition.cpp" ...failed aCC-C++-action ../../../libs/thread/build/bin/libboost_thread.so/acc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o... which is agian the same later i also tried to run configure using export CXX="aCC" export CXXFLAGS="-Aa -DAportable -D__HPACC_THREAD_SAFE_RB_TREE -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE" export LDFLAGS="-DAportable" export LIBS="-lpthread" ./configure and coping the user.hpp to right location still the same error presist. Is there any way out to compile this? what can be done to resolve it. I don't want to use GCC on HPUX. Rgds Albert --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs

3 3

Problem building Boost 1.31.0 for VC6
by Estese 02 May '04

02 May '04

Hi, I'm trying to build the Boost 1.31.0 libraries for VC6 (on WinXP). My installation of MSVC is "C:\Program Files\Microsoft Visual Studio\VC98". All my user environment variables point to this location, as they should. I created the bjam executable, placed it in my Boost root (C:/boost_1_31_0), and then ran bjam with the following command: bjam "-sTools=msvc" However, it attempts to run the following command for every library: "CALL D:\Program Files\Microsoft Visual Studio .NET 2003\VC7\bin\cl" I don't even have .NET installed on my PC! Why would it be doing this? I tried explicitly telling bjam where vc6 is with the -sMSVC_ROOT argument, but it always outputs the same result. I've verified all my user environment variables, and they all point to C: and to VC6, as they should. I don't know why bjam insists on trying to build the boost libraries for Visual Studio .NET. Any thoughts? Sean Estey __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

2 1

serialization library
by Russell Balest 01 May '04

01 May '04

Robert, Thank you for writing the serialization library. I'm in awe that someone finally did this so well. I've been using it for 2 days and think it's fantastic. I've been mucking with serialization frameworks myself for 8 years; now this will trump all my efforts and I'll give up and switch. Many Thanks, Russell Balest

1 0

RE: [Boost-users] Re: Config question:BOOST_NO_INTRINSIC_WCHAR_T(Intel7.1)
by Ben Hutchings 01 May '04

01 May '04

Christopher D. Russell <cdr(a)encapsule.com> wrote: > Thanks to Ben, Aleksey & John for the quick responses. > >And yes we know this is pain > Actually adding a command line switch, or punching the define into > user.hpp isn't all too bad in the grand scheme of things. > > Until Intel provides the cues required, may I suggest that a comment > be placed in boost/type_traits/is_integral.h at line 38: > > #ifndef BOOST_NO_INTRINSIC_WCHAR_T > // If the following line fails to compile and you're using the Intel > // compiler, see > // http://lists.boost.org/MailArchives/boost-users/msg06567.php <snip> It seems to me that it would be better still to put #ifdef BOOST_NO_INTRINSIC_WCHAR_T BOOST_STATIC_ASSERT(is_same<unsigned short, wchar_t>::value); #else BOOST_STATIC_ASSERT(!is_same<unsigned short, wchar_t>::value); #endif after the conditional definition of BOOST_NO_INTRINSIC_WCHAR_T to verify that the macro has been set/unset correctly. Ben.

3 3

lexical_cast<string> of type char
by DY, JERRY U (SBCSI) 01 May '04

01 May '04

I'm converting our code to use lexical_cast for converting between our numeric types to string. It worked mostly but was surprised to see what looked like graphic characters on my screen. It turns out that when we wanted to display the ascii value of a character, lexical_cast<string> doesn't work -- it doesn't treat the char as a numeric, which when we really think about it, makes a lot of sense. Casting the char to int solves the problem. But I was just wondering how the experts would handle this. char c = 65; string s1 = lexical_cast<string>(c) // s1 = "A" string s2 = lexical_cast<string>((int)c) // s2 = "65" Thanks! -Jerry

3 3

A BUG WITH THE BGL
by Hugues Joly 01 May '04

01 May '04

Hi, I have found a bug with the adjacency_list. It seems that there's a bug with the deletion of a vertex. See the attachment for a small program that triggers the problem. Thanks in advance. __________________________________________________________ Lèche-vitrine ou lèche-écran ? magasinage.yahoo.ca // test.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include <boost/config.hpp> #include <iostream> #include <boost/graph/subgraph.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graph_utility.hpp> int _tmain(int argc, _TCHAR* argv[]) { using namespace boost; //typedef adjacency_list_traits<vecS, vecS, directedS> Traits;// Does nothing? typedef boost::property<boost::vertex_color_t, int, boost::property< boost::vertex_name_t, std::string > > VertexProperty; typedef adjacency_list<vecS, vecS, directedS, VertexProperty, property<edge_index_t, int> > Graph; Graph G0; Graph::vertex_descriptor v_descr[4]; Graph::edge_descriptor e_descr[4]; for (int i = 0; i < 4; i++) { v_descr[i] = boost::add_vertex(G0); } for (int i = 0; i < 4; i++) { boost::remove_vertex(v_descr[i], G0); } return 0; }

2 1

string/wstring conversion using lexical_cast
by Tony Djordjevski 30 Apr '04

30 Apr '04

Hi, I'm using Boost 1.31.0 with VC++ 7.1 and I'm having some problems converting std::string to std::wstring and back. Here's the code that I'm trying to get to compile: std::wstring x = boost::lexical_cast<std::wstring>( std::string("this doesn't work")); std::string y = boost::lexical_cast<std::string>( std::wstring(L"neither does this")); The error I get for string to wstring: lexical_cast.hpp(150): error C2679: binary '>>' : no operator found which takes a right-hand operand of type 'std::wstring' (or there is no acceptable conversion) And the errors I get for wstring to string: lexical_cast.hpp(144): error C2679: binary '<<' : no operator found which takes a right-hand operand of type 'const std::basic_string<_Elem,_Traits,_Ax>' (or there is no acceptable conversion) with [ _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t> ] lexical_cast.hpp(144): error C2228: left of '.fail' must have class/struct/union type Any ideas of what I'm doing wrong? Best Regards, Tony Djordjevski

2 1

RE: [Boost-users] Regex simple code can't compile on linux, but it can be built on windows VC6.
by Ben Hutchings 30 Apr '04

30 Apr '04

John Maddock <john(a)johnmaddock.co.uk> wrote: <snip> > The g++ linker is pretty brain-dead - the libraries have to appear > on the command line *after* the source files that use them. This is not brain-dead. It is useful to be able to control the order in which symbols are looked for since they may be defined in more than one library. It is a bit weird that -l is not placed before the file names as is the Unix convention for options, but it *isn't* an option - it is a shortcut for specifying a file in the library search path that follows the usual library name convention (lib<name>.a) and is exactly equivalent to specifying the full file name (AFAIK). Secondly, there is no g++ linker. g++ can use various Unix linkers though it is most commonly used together with the linker from GNU binutils. However, all Unix linkers should behave this way. Ben.

1 0

Config question: BOOST_NO_INTRINSIC_WCHAR_T (Intel 7.1)
by Christopher D. Russell 30 Apr '04

30 Apr '04

Hello folks, I'm just getting around to upgrade to Boost 1_31_0 from Boost 1_30_0. I'm attempting to use 1_31_0 out-of-the-box (w/no bjam) but am confused about how to resolve problems related to native wchar_t support (or lack thereof). Some details: I'm using MSV6 with the Intel 7.1 compiler. Specifically I'm using: Intel(R) C++ Compiler for 32-bit applications, Version 7.1 Build 20030609Z I added a few #pragma messages to the config headers and have verified that config indeed seems to making the right decisions - at least at a high level: [Boost Configure: Selected Intel Compiler] [Boost Configure: Selected STLport Standard Library] [Boost Configure: Selected Win32 Platform] The specific error I encounter: d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost/type_traits/is_inte gral.hpp(38): error: class "boost::is_integral<unsigned short>" has already been defined BOOST_TT_AUX_BOOL_TRAIT_CV_SPEC1(is_integral,wchar_t,true) ^ d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost/type_traits/is_inte gral.hpp(38): error: class "boost::is_integral<const unsigned short>" has already been defined BOOST_TT_AUX_BOOL_TRAIT_CV_SPEC1(is_integral,wchar_t,true) ^ d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost/type_traits/is_inte gral.hpp(38): error: class "boost::is_integral<volatile unsigned short>" has already been defined BOOST_TT_AUX_BOOL_TRAIT_CV_SPEC1(is_integral,wchar_t,true) ^ d:\ENCAPSULE-EXTLIB\boost\boost_1_31_0\boost_1_31_0\boost/type_traits/is_inte gral.hpp(38): error: class "boost::is_integral<const volatile unsigned short>" has already been defined BOOST_TT_AUX_BOOL_TRAIT_CV_SPEC1(is_integral,wchar_t,true) ^ ... tracked back into .../1_31_0/boost/type_traits/is_integral.hpp #ifndef BOOST_NO_INTRINSIC_WCHAR_T BOOST_TT_AUX_BOOL_TRAIT_CV_SPEC1(is_integral,wchar_t,true) #endif ... where BOOST_NO_INTRINSIC_WCHAR_T is defined in ../1_31_0/boost/config/compiler/intel.hpp // See http://aspn.activestate.com/ASPN/Mail/Message/boost/1614864 #if BOOST_INTEL_CXX_VERSION < 700 # define BOOST_NO_INTRINSIC_WCHAR_T #else // _WCHAR_T_DEFINED is the Win32 spelling // _WCHAR_T is the Linux spelling # if !defined(_WCHAR_T_DEFINED) && !defined(_WCHAR_T) # define BOOST_NO_INTRINSIC_WCHAR_T # endif #endif I read the post on ActiveState but I'm still confused. With the frequency of Intel compiler updates is it possible this particular release is not setting the expected macros correctly? If someone could give me a kick in the right direction I would appreciate it. I really want to try some of these nifty Spirit v1.8 facilities (wow Joel). - Thanks Chris

2 4