- Boost-users - lists.boost.org

RE: [Boost-Users] Problem with 1.30.0 lexical_cast
by Tom Matelich 28 Mar '03

28 Mar '03

I agree :( I tried to use the debugger, but once it went into stlport_icl.dll I couldn't see which ostream function was being called. I'm currently trying to change the ostream signature to take a reference rather than a copy, in hopes that that will help. Unfortunately the amount of code to compile between these areas is quite large. > -----Original Message----- > From: Terje Slettebø [mailto:tslettebo@chello.no] > Sent: Wednesday, March 26, 2003 9:15 PM > To: Boost-Users(a)yahoogroups.com > Subject: Re: [Boost-Users] Problem with 1.30.0 lexical_cast > > > >From: "Tom Matelich" <tmatelich(a)zetec.com> > > > Compiler: gcc 3.2 and 3.2.2 > > > > I believe this is actually a bug in gcc, but I'm going to > post it hopes > that > > someone can help me. We have a handy little tool for > generating enums > with > > associated string conversion and stream > insertion/extraction functions. > > When we upgraded to boost 1.30.0, lexical_cast'ing one of > these enums to > > std::string started behaving incorrectly, rather than the > name, it is > giving > > me the integral value. It seems that the lexical_stream is > being used. > > Unfortunately, my test case is working fine. The complete test case > > (including definition of ZAcquisition::PPG) is appended at > the end. The > > code I am seeing failure with looks like: > > > > void foo(ZAcquisition::PPG::Type gt) > > { > > ... > > std::string str; > > str = boost::lexical_cast<std::string>(gt); > > std::cerr << "DEBUG, storing encode for PPG: " << str << > ", aka " << gt > > << std::endl; > > ... > > } > > > > This outputs (for example): > > DEBUG, storing encode for PPG: 0, aka ONE > > > > I tried boost::lexical_cast<std::string, > ZAcquisition::PPG::Type>(gt) as > > well. > > > > Anyone have any ideas? For now I'm going to back out to 1.29.0's > > lexical_cast. > > > It happens on my Windows/Intel 7.0 box as well. > > It's a little difficult when you don't have a failing test > case. If you had > that, I could have looked into it. The above code works > correctly on Intel > C++ 7.0 (Windows), here. > > > Regards, > > Terje > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Get 128 Bit SSL Encryption! > http://us.click.yahoo.com/xaxhjB/hdqFAA/xGHJAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > Info: <http://www.boost.org> > Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> > Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> > > > Your use of Yahoo! Groups is subject to > http://docs.yahoo.com/info/terms/ > > ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

1 0

very basic questions
by jeremmim 28 Mar '03

28 Mar '03

hello, i have downloaded the boost_1_30_0.tar.gz package. and have unzipped it. it has worked succesfully. we don't know what to do next: we'd like to use this library to build a graph. jeremie

2 1

test report_level in 1.30.0
by John Van Horne 27 Mar '03

27 Mar '03

We just upgraded from 1.29.0 to 1.30.0 and started having a problem running in the unit test framework. When we start the test with the command line parameter "--report_level=detailed" the tests crash. They work fine if we set the environment parameter BOOST_TEST_REPORT_LEVEL=detailed, or when we set other command line parameters, such as "--log_level=detailed". I looked at the code in libs/test/src/unit_test_main.cpp and saw that the command line parsing for report_level doesn't occur until after the unit test suite has been invoked. It appears that the unit test is then getting a command line that contains "--report_level=detailed". In our case, it doesn't know what to do with this. I hacked our copy of unit_test_main.cpp to parse the command line for --report_level before starting the unit test suite, storing the value locally. Has anyone else had this problem? Are we using the unit test framework the wrong way? Do you think I fixed it the right way, and will there be an official fix soon? Thanks, -John Van Horne

3 3

Building Boost with MSVC 6
by Alex 27 Mar '03

27 Mar '03

I fail to build the Boost libraries with MSVC 6. Specifically, I need to build the BGL but is complains that GRAPHVIZ_GRAPH is not defined. I am running: bjam "-sTOOLS=msvc" Please help!

3 4

Most efficient way to convert a run of Perl substitutions til boost::regex?
by Anders Johansen 27 Mar '03

27 Mar '03

Hi! I'm converting a Perl program that basically consists of a succession of regex transformations of the input string, eg.: #Case 1 - mutually exclusive endings s/erens$/\@r\@ns_/; s/ernes$/\@rn\@s_/; s/endes$/\@n\@s_/; s/estes$/\@st\@s_/; #Case 2: - a load of manipulations done in sequence s/jou/sju/g; s/jau/sjo/g; s/nch/ngk/g; Now the question is, how do I convert this to boost::regex code that runs as fast as possible. I expect to have to call the function implementing these transformations (there are /many/) about half a million times at runtime, and as I'm concerned about runtime performance, I'd obviously like to use the most efficient method available. I expect that Case #2 is simple, as I can use the regex_merge function, and nest the calls as in: static const boost::regex re1("jou"); static const boost::regex re1("jau"); static const boost::regex re1("nch"); static const std::string fs1("sju"); static const std::string fs2("sjo"); static const std::string fs3("ngk"); std::string res = regex_merge( regex_merge( regex_merge(input_string, re1, fs1) , re2, fs2) , re3, fs3); As to case 1, I guess I'd have to use a combination of the grep and format functions, and in the case as shown it'd be easy, as there is either one match or none for each line. Any suggestions wrt. improving run-time performance? Sincerely Anders S. Johansen

2 3

Re: [Boost-Users] newbie build question (threads and win32)
by p_i_r_x＠gmx.net 27 Mar '03

27 Mar '03

From: Dave Viner [mailto:daveviner@yahoo.com] Hi, I'm trying to use Boost's threads on WIN32 using VC++ and having some difficulty. I've built the source cd D:\boost\boost_1_30_0; bjam "-sTOOLS=msvc" and after the build is done, there are some errors, but they all appear related to the regression testing. Then I cd libs\thread\build; bjam "-sTOOLS=msvc" and everything appears to work fine. However, my simple program can't compile. I get this error: d:\boost\boost_1_30_0\boost\thread\thread.hpp(17) : fatal error C1189: #error : Thread support is unavailable! My test program simply is: #include <boost/thread/thread.hpp> int main(int argc, char* argv[]) { printf("Hello World!\n"); return 0; } I can't seem to figure out why threads aren't enabled. I realize this is a very simple question, but I'd love to hear what silly thing I've done wrong. Thanks in advance for your help. dave try to set up project/settings/c++/code generation/run-time libary to multithreaded ... ciao andreas -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!

1 0

Error with Thread in 1.30.0: Tempate Depth
by Reed Hedges 27 Mar '03

27 Mar '03

Hello, Has anyone else had this problem? I am trying to build a program that uses the boost_thread library (v. 1.30.0), but get this error repeatedly: /usr/local/include/boost/type_traits/is_convertible.hpp: At top level: /usr/local/include/boost/type_traits/is_convertible.hpp:184: template instantiation depth exceeds maximum of 17 (use -ftemplate-depth-NN to increase the maximum) instantiating `struct boost::add_reference<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/is_convertible.hpp:184: instantiated from `boost::detail::is_convertible_impl<VOS::AsyncConnect &, boost::detail::int_convertible>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::is_convertible<VOS::AsyncConnect &, boost::detail::int_convertible>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::detail::is_enum_helper<false>::type<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::detail::is_enum_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_scalar.hpp:30: instantiated from `boost::is_enum<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_scalar.hpp:30: instantiated from `boost::detail::is_scalar_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_pod.hpp:35: instantiated from `boost::is_scalar<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_pod.hpp:35: instantiated from `boost::detail::is_pod_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::is_POD<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::is_pod<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::detail::has_trivial_ctor_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_stateless.hpp:31: instantiated from `boost::has_trivial_constructor<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_stateless.hpp:31: instantiated from `boost::detail::is_stateless_impl<VOS::AsyncConnect>' /usr/local/include/boost/function/function_base.hpp:195: instantiated from `boost::is_stateless<VOS::AsyncConnect>' /usr/local/include/boost/function/function_base.hpp:195: instantiated from `boost::detail::function::get_function_tag<VOS::AsyncConnect>' /usr/local/include/boost/function/function_template.hpp:431: instantiated from `boost::function0<R, Allocator>::assign_to (Functor) [with Functor = VOS::AsyncConnect, R = void, Allocator = allocator<boost::function_base>]' /usr/local/include/boost/function/function_template.hpp:293: instantiated from `boost::function0<R, Allocator>::function0 (Functor) [with Functor = VOS::AsyncConnect, R = void, Allocator = allocator<boost::function_base>]' remotesocketsite.cc:565: instantiated from here /usr/local/include/boost/type_traits/is_convertible.hpp:184: invalid use of undefined type `struct boost::add_reference<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/add_reference.hpp:78: forward declaration of `struct boost::add_reference<VOS::AsyncConnect &>' VOS::AsyncConnect is my program's class. Setting -ftempate-depth-20 resolves the problem. This problem does not appear in Boost 1.29.0 Any information is greatly appreciated. Thanks reed PS. Here is the full source files: http://www-robotics.cs.umass.edu/~reed/remotesocketsite.hh http://www-robotics.cs.umass.edu/~reed/remotesocketsite.cc The entire project can be downloaded from anonymous CVS (see http://interreality.org)

2 1

Problem with 1.30.0 lexical_cast
by Tom Matelich 27 Mar '03

27 Mar '03

Compiler: gcc 3.2 and 3.2.2 I believe this is actually a bug in gcc, but I'm going to post it hopes that someone can help me. We have a handy little tool for generating enums with associated string conversion and stream insertion/extraction functions. When we upgraded to boost 1.30.0, lexical_cast'ing one of these enums to std::string started behaving incorrectly, rather than the name, it is giving me the integral value. It seems that the lexical_stream is being used. Unfortunately, my test case is working fine. The complete test case (including definition of ZAcquisition::PPG) is appended at the end. The code I am seeing failure with looks like: void foo(ZAcquisition::PPG::Type gt) { ... std::string str; str = boost::lexical_cast<std::string>(gt); std::cerr << "DEBUG, storing encode for PPG: " << str << ", aka " << gt << std::endl; ... } This outputs (for example): DEBUG, storing encode for PPG: 0, aka ONE I tried boost::lexical_cast<std::string, ZAcquisition::PPG::Type>(gt) as well. Anyone have any ideas? For now I'm going to back out to 1.29.0's lexical_cast. Thanks, Tom --------Complete Passing Test Case #include <boost/lexical_cast.hpp> #include <string> #include <cassert> #include <iostream> namespace ZAcquisition { namespace PPG { enum Type { ONE = 0, TWO, THREE, FOUR, INVALID = 100 }; Type stringToType(std::string const&); std::string typeToString(PPG::Type); const int size = 5; const Type values[size] = { ONE, TWO, THREE, FOUR, INVALID }; } } std::ostream& operator<<(std::ostream&, ZAcquisition::PPG::Type); std::istream& operator>>(std::istream&, ZAcquisition::PPG::Type&); namespace { const char s_PPG_ONE[] = "ONE"; const char s_PPG_TWO[] = "TWO"; const char s_PPG_THREE[] = "THREE"; const char s_PPG_FOUR[] = "FOUR"; const char s_PPG_INVALID[] = "INVALID"; } std::string ZAcquisition::PPG::typeToString(ZAcquisition::PPG::Type type) { std::string ret("Invalid_PPG_type"); switch(type) { case PPG::ONE: ret = s_PPG_ONE; break; case PPG::TWO: ret = s_PPG_TWO; break; case PPG::THREE: ret = s_PPG_THREE; break; case PPG::FOUR: ret = s_PPG_FOUR; break; case PPG::INVALID: ret = s_PPG_INVALID; break; default: std::cerr << static_cast<int>(type) << " is not a valid PPG enumeration." << std::endl; } return ret; } ZAcquisition::PPG::Type ZAcquisition::PPG::stringToType(std::string const& str) { PPG::Type ret = PPG::ONE; if(0 == str.compare(s_PPG_TWO)) { ret = PPG::TWO; } else if(0 == str.compare(s_PPG_THREE)) { ret = PPG::THREE; } else if(0 == str.compare(s_PPG_FOUR)) { ret = PPG::FOUR; } else if(0 == str.compare(s_PPG_INVALID)) { ret = PPG::INVALID; } return ret; } std::ostream& operator<<(std::ostream& out, ZAcquisition::PPG::Type type) { return out << ZAcquisition::PPG::typeToString(type); } std::istream& operator>>(std::istream& in, ZAcquisition::PPG::Type& type) { std::string str; in >> str; type = ZAcquisition::PPG::stringToType(str); return in; } int main() { assert(std::string("ONE") == boost::lexical_cast<std::string>(ZAcquisition::PPG::ONE)); return 0; } ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

2 1

Boost thread question
by Michael 27 Mar '03

27 Mar '03

I am having trouble getting the boost thread library to work. I am using Borland C++Builder 6 (on Win2k), and I tried the 1.29.0 release and the 1.30.0.b1 beta release and both give me the same errors in the condition.hpp file: line 93: " 'operator!' not implemented in type 'recursive_mutex' for arguments of the same type" and line 96: " 'recursive_mutex::m_mutex' is not accessible" Plus another 5 errors. I tried to look at the condition and recursive_mutex class definitions and I do not understand how they are implemented. Am I using it wrong to get that error? Let me know if you need a code sample. Thanks, Michael

3 3

multi_array iterators ??
by dbkita 27 Mar '03

27 Mar '03

I am intersted in a simple way to iterate on a multi_array (or better yet a multi_array_view) regardless of dimension or ranges or order of access. I suppose for the entire multi_array one can use the data() method to return a T* and step through the contiguous memory block. But the case for a multi_array_view doesn't not seem nearly so simple taking into account strides, offsets, and degenerate ranges and all. Thanks in advance for any advice.

1 0