- Boost-users - lists.boost.org

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

Regex simple code can't compile on linux, but it can be built on windows VC6.
by Guan Bin 30 Apr '04

30 Apr '04

Hi, the simple code is below: ____________________________________________________________________ #include <iostream> #include <string> #include "boost/regex.hpp" using namespace boost; regex expression("this is ([[:digit:]]*)"); int main(int argc, char* argv[]) { while (true) { char buf[1000]; memset(buf, 0, 1000); std::cin.getline(buf, 1000); std::string str(buf); cmatch match; if (!regex_match(str, match, expression)) { std::cout<<"Don't match"<<std::endl; continue; } for (int i = 0; i < match.size(); i++) { std::string msg; msg.assign(match[i].first, match[i].second); std::cout<<msg<<std::endl; } } return 0; } ____________________________________________________________________________________ the makefile is below ------------------------------------------------------ INCLUDE_DIR = /unzipped/boost_1_31_0/ -I/usr/local/include/stlport/ #INCLUDE_DIR = /unzipped/boost_1_31_0/ LIB_DIR = /unzipped/boost_1_31_0/libs/regex/build/gcc/ -L/usr/local/lib/ #LIB_DIR = /unzipped/boost_1_31_0/libs/regex/build/gcc/ LINK = boost_regex-gcc-1_31 -lstlport_gcc #LINK = boost_regex-gcc-1_31 FLG = -Wall all : regex_sample.o g++ regex_sample.o -L$(LIB_DIR) $(FLG) -l$(LINK) -o sample %.o : %.cpp g++ -I$(INCLUDE_DIR) -L$(LIB_DIR) $(FLG) -l$(LINK) -c $< -------------------------------------------------------------- and the error information is : ------------------------------------------------------------ [root@guanbin regex]# make g++ -I/unzipped/boost_1_31_0/ -I/usr/local/include/stlport/ -L/unzipped/boost_1_31_0/libs/regex/build/gcc/ -L/usr/local/lib/ -Wall -lboost_regex-gcc-1_31 -lstlport_gcc -c regex_sample.cpp regex_sample.cpp: In function `int main(int, char**)': regex_sample.cpp:37: warning: comparison between signed and unsigned integer expressions g++: -lboost_regex-gcc-1_31: linker input file unused because linking not done g++: -lstlport_gcc: linker input file unused because linking not done g++ regex_sample.o -L/unzipped/boost_1_31_0/libs/regex/build/gcc/ -L/usr/local/lib/ -Wall -lboost_regex-gcc-1_31 -lstlport_gcc -o sample regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matcherIPKcN4_STL9allocatorINS_9sub_matchIS3_EEEENS_12regex_traitsIcEENS5_IcEEEC1ES3_S3_RNS_13match_resultsIS3_S8_EERKNS_14reg_expressionIcSA_SB_EENS_15regex_constants12_match_flagsE+0x51): In function `boost::re_detail::perl_matcher<char const*, _STL::allocator<boost::sub_match<char const*> >, boost::regex_traits<char>, _STL::allocator<char> >::perl_matcher[in-charge](char const*, char const*, boost::match_results<char const*, _STL::allocator<boost::sub_match<char const*> > >&, boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&, boost::regex_constants::_match_flags)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::get_traits() const' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matcherIPKcN4_STL9allocatorINS_9sub_matchIS3_EEEENS_12regex_traitsIcEENS5_IcEEEC1ES3_S3_RNS_13match_resultsIS3_S8_EERKNS_14reg_expressionIcSA_SB_EENS_15regex_constants12_match_flagsE+0x8a): In function `boost::re_detail::perl_matcher<char const*, _STL::allocator<boost::sub_match<char const*> >, boost::regex_traits<char>, _STL::allocator<char> >::perl_matcher[in-charge](char const*, char const*, boost::match_results<char const*, _STL::allocator<boost::sub_match<char const*> > >&, boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&, boost::regex_constants::_match_flags)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::empty() const' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matcherIPKcN4_STL9allocatorINS_9sub_matchIS3_EEEENS_12regex_traitsIcEENS5_IcEEE24estimate_max_state_countEPNS4_26random_access_iterator_tagE+0x2c): In function `boost::re_detail::perl_matcher<char const*, _STL::allocator<boost::sub_match<char const*> >, boost::regex_traits<char>, _STL::allocator<char> >::estimate_max_state_count(_STL::random_access_iterator_tag*)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::size() const' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail12perl_matcherIPKcN4_STL9allocatorINS_9sub_matchIS3_EEEENS_12regex_traitsIcEENS5_IcEEE9match_impEv+0x94): In function `boost::re_detail::perl_matcher<char const*, _STL::allocator<boost::sub_match<char const*> >, boost::regex_traits<char>, _STL::allocator<char> >::match_imp()': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::mark_count() const' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail8access_tIcNS_12regex_traitsIcEEN4_STL9allocatorIcEEE5firstERKNS_14reg_expressionIcS3_S6_EE+0xd): In function `boost::re_detail::access_t<char, boost::regex_traits<char>, _STL::allocator<char> >::first(boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::first(boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail11raise_errorINS_12regex_traitsIcEEEEvRKT_j+0x21): In function `void boost::re_detail::raise_error<boost::regex_traits<char> >(boost::regex_traits<char> const&, unsigned)': : undefined reference to `boost::re_detail::raise_regex_exception(_STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char> > const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail8access_tIcNS_12regex_traitsIcEEN4_STL9allocatorIcEEE9can_startEcPKhh+0x24): In function `boost::re_detail::access_t<char, boost::regex_traits<char>, _STL::allocator<char> >::can_start(char, unsigned char const*, unsigned char)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::can_start(char, unsigned char const*, unsigned char, boost::re_detail::_narrow_type const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail16re_is_set_memberIPKccNS_12regex_traitsIcEEN4_STL9allocatorIcEEEET_S9_S9_PKNS0_11re_set_longERKNS_14reg_expressionIT0_T1_T2_EE+0x41): In function `char const* boost::re_detail::re_is_set_member<char const*, char, boost::regex_traits<char>, _STL::allocator<char> >(char const*, char const*, boost::re_detail::re_set_long const*, boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::get_traits() const' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail16re_is_set_memberIPKccNS_12regex_traitsIcEEN4_STL9allocatorIcEEEET_S9_S9_PKNS0_11re_set_longERKNS_14reg_expressionIT0_T1_T2_EE+0x258): In function `char const* boost::re_detail::re_is_set_member<char const*, char, boost::regex_traits<char>, _STL::allocator<char> >(char const*, char const*, boost::re_detail::re_set_long const*, boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&)': : undefined reference to `boost::c_regex_traits<char>::transform(_STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char> >&, _STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char> > const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost9re_detail16re_is_set_memberIPKccNS_12regex_traitsIcEEN4_STL9allocatorIcEEEET_S9_S9_PKNS0_11re_set_longERKNS_14reg_expressionIT0_T1_T2_EE+0x34b): In function `char const* boost::re_detail::re_is_set_member<char const*, char, boost::regex_traits<char>, _STL::allocator<char> >(char const*, char const*, boost::re_detail::re_set_long const*, boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> > const&)': : undefined reference to `boost::c_regex_traits<char>::transform_primary(_STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char> >&, _STL::basic_string<char, _STL::char_traits<char>, _STL::allocator<char> > const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost11basic_regexIcNS_12regex_traitsIcEEN4_STL9allocatorIcEEEC1EPKcjRKS5_+0x13): In function `boost::basic_regex<char, boost::regex_traits<char>, _STL::allocator<char> >::basic_regex[in-charge](char const*, unsigned, _STL::allocator<char> const&)': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::reg_expression[not-in-charge](char const*, unsigned, _STL::allocator<char> const&)' regex_sample.o(.gnu.linkonce.t._ZN5boost11basic_regexIcNS_12regex_traitsIcEEN4_STL9allocatorIcEEED1Ev+0xd): In function `boost::basic_regex<char, boost::regex_traits<char>, _STL::allocator<char> >::~basic_regex [in-charge]()': : undefined reference to `boost::reg_expression<char, boost::regex_traits<char>, _STL::allocator<char> >::~reg_expression [not-in-charge]()' collect2: ld returned 1 exit status make: *** [all] Error 1 ------------------------------------------------------------------------------------- the environment is : linux redhat 9.0 gcc 3.2.2 boost_1_31_0 stlport_4_6_2 Who can help me? thanks Guan Bin gb0519(a)hotmail.com

2 1

Problem with Boost 1.31.0 Regex for tru64cxx65
by Richard Hadsell 29 Apr '04

29 Apr '04

Having found out how to build Bjam, I have tried to build the libraries of Boost 1.31.0 for tru64cxx65. I'm only interested in Regex at the moment, so I won't bother you with the problems building other libraries. When the build gets to this point: tru64cxx65-C++-action bin/boost/libs/regex/build/libboost_regex.so/tru64cxx65/release/cregex.o it hangs. I have run into this situation with other large files, and my usual remedy is to decrease the optimization level. How can I do that? If I can't do it for just this file, I'm willing to reduce the optimization level for the entire library, or even for all libraries. (This is not a platform that I worry about performance; it's just there to support a few vestigial machines.) -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

2 2

Cannot build bjam for tru64cxx
by Richard Hadsell 29 Apr '04

29 Apr '04

I am trying to upgrade from Boost 1.30.0 to 1.31.0. I am unable to build bjam from the source in tools/build/jam_src: 67% build.sh tru64cxx ### ### Using 'tru64cxx' toolset. ### rm -rf bootstrap.tru64cxx mkdir bootstrap.tru64cxx cc -o bootstrap.tru64cxx/jam0 command.c compile.c execnt.c execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c command.c: compile.c: [snip] modules/sequence.c: ./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx --toolset-root= clean ...found 1 target... ...updating 1 target... ...updated 1 target... ./bootstrap.tru64cxx/jam0 -f build.jam --toolset=tru64cxx --toolset-root= don't know how to make ...found 1 target... ...can't find 1 target... -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601

3 5

Re: [Boost-users] Re: Config question: BOOST_NO_INTRINSIC_WCHAR_T(Intel7.1)
by Aleksey Gurtovoy 29 Apr '04

29 Apr '04

Christopher D. Russell writes: > Some additional information pertaining to BOOST_NO_INTRINSIC_WCHAR_T using > the Intel C++ 7.1 compiler in my MSVC 6 SP6 environment: > > Using Boost v1.31.0 + STLport v5.0-125 + Intel C++ v7.1 (I updated to build > 20030910Z) inside of MSVC 6 SP6 with a fairly recent MS Platform SDK, I > simply could not get boost/config/compiler/intel.hpp to send me down the road > to glory. In short, if you are running Intel in MSVC6 compatibility-mode and you are not compiling through bjam, you have to define BOOST_NO_INTRINSIC_WCHAR_T yourself -- either through command line or in the user config. If you are using bjam, the Intel toolset (http://tinyurl.com/2codz) does that for you. > > Inside of config/compiler/intel.hpp, _WCHAR_T_DEFINED is defined resulting in > BOOST_NO_INTRINSIC_WCHAR_T not being set. Subsequently, this results in the > compile-time error: > > boost/type_traits/is_integral.hpp(38): error: class > "boost::is_integral<unsigned short>" has already been defined > > Per "Compiler errors with Intel 7.1 and type_traits" > (http://lists.boost.org/MailArchives/boost/msg53033.php) specifically John > Maddock's reply (http://lists.boost.org/MailArchives/boost/msg53121.php) I > short-circuited the logic in config/compiler/intel.hpp and explicitly defined > BOOST_NO_INTRINSIC_WCHAR_T in config/user.hpp. This seems to work acceptably > for this project. But I'm not at all comfortable with this solution because I > really don't understand what the fundamental issue is with all this wchar_t > stuff. > > Forgive my ignorance but if, with my current working config, if I declare a > wchar_t type in my code I will get a 16-bit UCS-2 character. Correct? Having > now poured over all postings related to this subject in the archive, I have > an inkling that the root of all this stems from the way the compiler handles > type aliasing? Yes, more or less. > That is, with BOOST_NO_INTRINSIC_WCHAR_T a defined a wchar_t is actually an > alias for an unsigned int More likely 'unsigned short', but otherwise yes. > whereas in the case > !defined(BOOST_NO_INTRINSIC_WCHAR_T), the compiler treats wchar_t as an > intrinsic type? Yes. Or, rather, to be precisely clear, BOOST_NO_INTRINSIC_WCHAR_T _indicates_ to the Boost code that on the particular compiler/configuration 'wchar_t' is simply an alias for some other built-in integral type. It doesn't change the compiler's behavior. > And from this we get these template specialization errors? Yep. -- Aleksey Gurtovoy MetaCommunications Engineering

1 0

Boost won't build
by Charles Polisher 28 Apr '04

28 Apr '04

$ pwd /BUILD_TREES/boost $ bjam "-sTOOLS=gcc" /usr/bin/locate/allyourbase.jam: Not a directory /usr/bin/locate/boost-base.jam: Not a directory /BUILD_TREES/boost/tools/build/v1/bootstrap.jam:22: in boost-build rule load-jamfiles unknown in module /BUILD_TREES/boost/boost-build.jam:16: in module scope $ gcc -v <snip> gcc version 3.3 20030226 (prerelease) (SuSE Linux) I get the same result with both the latest release (1.31.0) on sourceforge and with the CVS version. Google, the FAQ and the list archives haven't yielded up a clue. I *must* be overlooking something obvious. Help!

2 3