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

Re: [Boost-Users] ScopeGuard Implementation
by Jon Wang 04 Jul '02

04 Jul '02

>This solution won't work, because you are storing a reference to a >temporary object, which will cease to exist after the constructor call. >Then the destructor is accessing memory that has already been destructed >and probably reused. Sorry! A silly mistake here:-) Well, what I meant is typedef const scoped_guard_impl& scoped_guard; // not "typedef scoped_guard_impl& scoped_guard;" Then "a const reference initialized with a temporary value makes that temporary value live for the lifetime of the reference itself". Is this fine? Jon

1 0

Re: [Boost-Users] ScopeGuard Implementation
by Jon Wang 04 Jul '02

04 Jul '02

>Looks fine to me. To rein in the compile times a little bit, you can pull in >just the 0-argument version of function, e.g., > #include <boost/function/function0.hpp> // (not <boost/function.hpp>) >and use boost::function0<void> instead of boost::function<void>. Under MSVC, >you might even get fewer senseless ICEs :) Oh, yes, function0 is enough. Thanks very much, Doug. Well, could the copy constructing from a boost.bind result be avoided? How about the following solution? Thanks. #include <boost/function/function0.hpp> #include <boost/bind.hpp> #include <boost/utility.hpp> #define ON_BLOCK_EXIT(x) scoped_guard guard##__LINE__ = make_guard(::boost::bind##x);guard##__LINE__; class scoped_guard_impl: ::boost::noncopyable { private: typedef const ::boost::function0<void>& f_type; bool dismissed_; f_type f_; public: scoped_guard_impl(f_type v): f_(v), dismissed_(false) {} ~scoped_guard_impl() throw() { if(!dismissed_) try {f_();} catch(...) {} } void dismiss() throw() { dismissed_ = true; } }; typedef scoped_guard_impl& scoped_guard; typedef scoped_guard_impl make_guard; #include <stdio.h> int main() { FILE* fp = fopen("hello.txt", "r"); ON_BLOCK_EXIT((fclose, fp)); //scoped_guard guard = make_guard(boost::bind(fclose, fp)); return 0; } Jon

1 0

Re: [Boost-Users] ScopeGuard Implementation
by Douglas Paul Gregor 04 Jul '02

04 Jul '02

On Thu, 4 Jul 2002, Jon Wang wrote: > Oh, yes, function0 is enough. Thanks very much, Doug. > Well, could the copy constructing from a boost.bind result be avoided? > How about the following solution? Thanks. This solution won't work, because you are storing a reference to a temporary object, which will cease to exist after the constructor call. Then the destructor is accessing memory that has already been destructed and probably reused. Doug

1 0

Re: [Boost-Users] ScopeGuard Implementation
by Douglas Gregor 03 Jul '02

03 Jul '02

On Wednesday 03 July 2002 12:30 am, Jon Wang wrote: > Hi, > > Recently I've tried to implement Andrei's ScopeGuard (see > http://www.cuj.com/experts/1812/alexandr.htm?topic=experts for details) > with boost.function and boost.bind. Is there anything wrong with it? Thanks > for reviewing. Looks fine to me. To rein in the compile times a little bit, you can pull in just the 0-argument version of function, e.g., #include <boost/function/function0.hpp> // (not <boost/function.hpp>) and use boost::function0<void> instead of boost::function<void>. Under MSVC, you might even get fewer senseless ICEs :) Doug

1 0

ScopeGuard Implementation
by Jon Wang 03 Jul '02

03 Jul '02

Hi, Recently I've tried to implement Andrei's ScopeGuard (see http://www.cuj.com/experts/1812/alexandr.htm?topic=experts for details) with boost.function and boost.bind. Is there anything wrong with it? Thanks for reviewing. #include <boost/function.hpp> #include <boost/bind.hpp> #include <boost/utility.hpp> #define ON_BLOCK_EXIT(x) scoped_guard guard##__LINE__(::boost::bind##x) class scoped_guard: ::boost::noncopyable { private: typedef const ::boost::function<void> f_type; // reference might cause crash bool dismissed_; f_type f_; public: scoped_guard(f_type& v): f_(v), dismissed_(false) {} ~scoped_guard() throw() { if(!dismissed_) try {f_();} catch(...) {} } void dismiss() throw() { dismissed_ = true; } }; With the macro ON_BLOCK_EXIT, we can easily use it like this: // ... #include <stdio.h> int main() { FILE* fp = fopen("hello.txt", "r"); ON_BLOCK_EXIT((fclose, fp)); //scoped_guard guard(boost::bind(fclose, fp)); return 0; }　　　　　　　　　　　　　　　　Jon Wang babysloth(a)c-view.org 　　　　　　　　　　　　2002-07-03

1 0

regex with double byte character sets
by bthiesfield 03 Jul '02

03 Jul '02

Hi all, I am currently trying to use the boost regex library with Japanese language strings. It appears like DBCS is not supported. For example, using the following code (with compile definition of BOOST_REGEX_USE_C_LOCALE) I get the output strings as 0 = "。" 1 = "English" Instead of the expected: 0 = "やゆよわをー。" 1 = "English" This is due to the fact that the Japanese (SJIS encoding) for one of these characters uses the [ character as one of the characters in the encoding. setlocale( LC_COLLATE, "Japanese" ); setlocale( LC_CTYPE, "Japanese" ); char * pszText = "やゆよわをー。 [english]", char * pszRule ="([^\\[]*)\\[([[:word:]]*)\\]"; // split the string into it's components std::vector<std::string> vPart; boost::regex eParseExpr( pszRule, boost::regbase::normal | boost::regbase::icase ); boost::regex_split( std::back_inserter(vPart), std::string(pszText), eParseExpr ); Is there some what to modify the library to enable DBCS? For example, can the char_traits be modified to enable DBCS processing? (Keeping in mind that the biggest problem with DBCS is that a single character may consist of 2 bytes which tends to blow out all assumptions about the size of characters). Brodie.

4 4

RE: [Boost-Users] Re: Regex boost_1_28_0 incorrect build / run-t ime problem
by Eric Reaburn 02 Jul '02

02 Jul '02

I found this solution with much hair-pulling, doc-reading, and, eventually, header file comparing! :^) -----Original Message----- From: Hofi [mailto:yg-boost-users@m.gmane.org] Sent: Tuesday, 2 July 2002 5:41 PM To: boost-users(a)yahoogroups.com Subject: [Boost-Users] Re: Regex boost_1_28_0 incorrect build / run-time problem "Eric Reaburn" <ereaburn(a)data.com.au> wrote in message news:4473AF479EE7D41198510004AC1D1C738707EC@GRACE... > This looks like a similar problem I had. I'm also using C++ Builder 5 with > patch 1. > > I was using regex from Boost 1.25.0 but when I upgraded to 1.28.0 I > got run-time errors (specifically bad_alloc). I had no problems > compiling and > running the test and example programs. > > Eventually I discovered that I had to uncomment the following two > macros (in > user.hpp in boost/regex) and recompile the regex libraries: > > // define this if no template instances are to be placed in // the > library rather than users object files: #define > BOOST_REGEX_NO_EXTERNAL_TEMPLATES > > // define this if the forward declarations in regex_fwd.hpp // cause > more problems than they are worth: #define BOOST_REGEX_NO_FWD > > Now everything's just dandy! Eric you are a life saver!!! I had the same problem, earlier version worked perfectly, the newest built fine but caused run time error. Did you find this solution with probing or do you have knowledge of something? Thank you for your help. By(t)e Hofi 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/

1 0

RE: [Boost-Users] Regex boost_1_28_0 incorrect build / run-time problem
by Eric Reaburn 02 Jul '02

02 Jul '02

This looks like a similar problem I had. I'm also using C++ Builder 5 with patch 1. I was using regex from Boost 1.25.0 but when I upgraded to 1.28.0 I got run-time errors (specifically bad_alloc). I had no problems compiling and running the test and example programs. Eventually I discovered that I had to uncomment the following two macros (in user.hpp in boost/regex) and recompile the regex libraries: // define this if no template instances are to be placed in // the library rather than users object files: #define BOOST_REGEX_NO_EXTERNAL_TEMPLATES // define this if the forward declarations in regex_fwd.hpp // cause more problems than they are worth: #define BOOST_REGEX_NO_FWD Now everything's just dandy! -----Original Message----- From: David Beres [mailto:dberes@advpubtech.com] Sent: Friday, 21 June 2002 9:02 AM To: Boost-Users(a)yahoogroups.com Cc: John Maddock Subject: [Boost-Users] Regex boost_1_28_0 incorrect build / run-time problem Hello, I am new to Boost since version 1.27. I apparently have a problem building Regex from Boost 1.28 as I encounter a runtime error that causes all the examples to hang. I was successfully able to run all of the Regex examples except 'partial match' under boost 1.27 using Borland BCB5 patch 1. My procedure for building Regex for both versions 1.27 and 1.28 was to run Make.exe -fbcb5.mak install clean The dlls and libs are then correctly placed in the Builder 5 root directory, and the examples build OK. However, whereas they ran successfully for Boost 1.27, they do not run under Boost 1.28. I also tried BJam, but the problem remains. If possible, please let me know what was my mistake in building the libs. Thank you, David Beres[dberes(a)advpubtech.com] 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/

2 1

Bruno Voigt/IC3S is out of the office.
by Bruno.Voigt＠ic3s.de 01 Jul '02

01 Jul '02

I will be out of the office starting 01.07.2002 and will not return until 22.07.2002. I will respond to your message when I return. Im back at 22.7.02. Call IC3S at +49.4106.655.0.

1 0

Regex boost_1_28_0 incorrect build / run-time problem
by David Beres 01 Jul '02

01 Jul '02

Hello, I am new to Boost since version 1.27. I apparently have a problem building Regex from Boost 1.28 as I encounter a runtime error that causes all the examples to hang. I was successfully able to run all of the Regex examples except 'partial match' under boost 1.27 using Borland BCB5 patch 1. My procedure for building Regex for both versions 1.27 and 1.28 was to run Make.exe -fbcb5.mak install clean The dlls and libs are then correctly placed in the Builder 5 root directory, and the examples build OK. However, whereas they ran successfully for Boost 1.27, they do not run under Boost 1.28. I also tried BJam, but the problem remains. If possible, please let me know what was my mistake in building the libs. Thank you, David Beres[dberes(a)advpubtech.com]

2 1

Problems getting subexpressions in regex_search
by soleani 30 Jun '02

30 Jun '02

Hi all, This is the test program: #include <boost/regex.hpp> #include <iostream> #include <string> int main() { static const boost::regex regexRedirectedSection( "\\[(.+?) \\s*=\\s*<(.+?):(.+?)>\\]", boost::regbase::perl ); std::string input = "[MY_SECTION = <FILE:SECTION>]"; boost::cmatch what; if ( boost::regex_search( input, what, regexRedirectedSection, boost::regbase::perl ) ) { cerr << "Matched new style section redirection!!!! Input is: " << input << endl; cerr << "0 gives: --" << what[0].first << "-- and second: " << what[0].second << endl; cerr << "1 gives: --" << what[1].first << "-- and second: " << what[1].second << endl; cerr << "2 gives: --" << what[2].first << "-- and second: " << what[2].second << endl; cerr << "3 gives: --" << what[3].first << "-- and second: " << what[3].second << endl; } return 0; } This is the output: [anibal@anibal ControlFile]$ ./match Matched new style section redirection!!!! Input is: [MY_SECTION = <FILE:SECTION>] 0 gives: --[MY_SECTION = <FILE:SECTION>]-- and second: 1 gives: --MY_SECTION = <FILE:SECTION>]-- and second: = <FILE:SECTION>] 2 gives: --FILE:SECTION>]-- and second: :SECTION>] 3 gives: --SECTION>]-- and second: >] I don't understand why $1 is not giving my MY_SECTION only. It looks like the non-greedy operator is not working as I expect it. This same expression works in Perl and jakarta's regex engine in Java. I basically need to extract MY_SECTION, FILE, and SECTION from the input string. Any pointers as to what's going on will be greatly appreciated. -Anibal

2 1

RE: [Boost-Users] Win2k / NT Spell Check Wrapper
by Jim.Hyslop 29 Jun '02

29 Jun '02

Jer (yg-boost-users(a)gmane.org) wrote: > Hi all, > > My first time posting or visiting here. Please note that this list is for discussion of the Boost library, not for general programming discussions. In general, it is considered good etiquette to research what is considered "on topic" for a newsgroup or mail list, before you post to it. Please read the information at http://groups.yahoo.com/group/Boost-Users/ Thank you. -- Jim Hyslop moderator, boost-users(a)yahoogroups.com

2 1

Win2k / NT Spell Check Wrapper
by Jer 28 Jun '02

28 Jun '02

Hi all, My first time posting or visiting here. I'm trying to find out if anyone has ever worked with the spell checker .dll and .dic files that come with Win 2k / NT. I'm desiring to wrap / call this via VB or Lotus Script for a web application. I'm a newbie c++ programmer, but I'm learning fairly quickly. Any help or useful suggestions would be greatly appreciated. Kind regards, Jer -- "Proceed with wisdom, humility and honesty."

2 1

Re: [Boost-Users] Re: boost::polymorphic_upcast suggestion
by Sam Partington 28 Jun '02

28 Jun '02

Sorry, don't know what happened then, I'll continue... class A {}; class B {}; class C : public A, public B {}; int main(int argc, char* argv[]) { C c; C* pc = &c; //B* pb = boost::polymorphic_downcast<B*>( pc ); // this cast is unnecessary, the compiler <knows> that C isa B at compile time, // so it can go ahead and upcast it without asking you or the runtime type info: B* pb = pc; // C* pc2 = polymorphic_upcast<C*>( pb); // this is precisely where the boost::polymorphic_downcast is intended to be used, // ie Cast a Base (ptr or ref) to a Derived (ptr or ref) // the compiler doesn't know that a B object is definately a valid C, so it requires you to // qualify it, using some kind of cast. C* pc2 = boost::polymorphic_downcast<C*>(pb); return 0; } So thats downcasting and upcasting, there is no need for a polymorphic_upcast, as it is implicity done and can be tested for at compile time. The only other cast not covered here is cross casting, which is what boost::polymorphic_cast is designed for, but I find that almost everytime I come across a use of a cross cast it is due to a design flaw. (the same could also be said to a lesser extent about downcasting) Hope this clears things up a bit. Sam > > -----Original Message----- > > From: news [mailto:news@main.gmane.org]On Behalf Of Jean Llorca > > Sent: 27 June 2002 15:31 > > To: boost-users(a)yahoogroups.com > > Subject: [Boost-Users] Re: boost::polymorphic_upcast suggestion > > > > > > "Darin Adler" <darin(a)bentspoon.com> a écrit dans le message de news: > > B586F909-89D7-11D6-9349-0003935B80A2(a)bentspoon.com... > > > > > > On Thursday, June 27, 2002, at 06:38 AM, Jean Llorca wrote: > > > > > > > Here upcasting means casting a base class to a derived class, I know > > > > it may seem strange, bust boost offers a downcast > > > > which does the static_cast the language does implicitly > already (check > > > > <boost/cast.hpp>). > > > > > > I think you've got it backwards. Downcasting, in Boost at least, means > > > casting a pointer to a base class part of an object to a pointer to a > > > derived class part of the same object. The polymorphic_downcast is > > > *not* doing a static_cast for a conversion the language already does > > > implicitly. > > > > template <class Target, class Source> > > inline Target polymorphic_downcast(Source* x > > BOOST_EXPLICIT_DEFAULT_TARGET) > > { > > assert( dynamic_cast<Target>(x) == x ); // detect logic error > > return static_cast<Target>(x); > > } > > > > Sorry about it, but it's here in the code. This is in the last > version of > > the CVS. It does a static_cast. The compiler does static_cast > > implicitly in > > some cases. > > For instance a C++ compiler replaces the assert line with: > > assert( dynamic_cast<Target>(x) == static_cast<Target>(x) ); > > > > > > > > Could you give a specific complete example (a file that would compile, > > > with all the declarations) of how one would use what you're proposing > > > to help make this clearer? > > > > I enclosed two files to this reply. Don't scream about chosen > class names > > and stuff in the example ;)

3 3

boost::bind for member functions
by Bill Dozier 27 Jun '02

27 Jun '02

Hi, I'd like to be able to bind an object to to a member function argument, like the example below. NB: if I make not_ok()'s first argument an int and pass an int variable to bind, gcc will buy it. I've tried this every way that makes any sense to me and I have not been able to get it to work. I'm using gcc 2.95.3. Thanks, Bill #include <boost/bind.hpp> #include <boost/function.hpp> class D { private: int _d; public: D() :_d(0) {} int d() const { return _d; } void d(int i) { _d = i; } }; typedef boost::function<int, int> Foo; class A { private: Foo _f; public: A(Foo f) :_f(f) {} int doit(int i) { return _f(i); } }; class B { public: int not_ok(const D *d, int j) { return d->d() + j; } }; class C { public: int ok(int i) { return i * i; } }; int fooBar(int j); static Foo g = fooBar; int fooBar(int j) { B *b = new B; C *c = new C; Foo f1 = boost::bind(&C::ok, c, _1); A a1(f1); int i = 5; D *d = new D; d->d(3); Foo f2 = boost::bind(&B::not_ok, b, _1, d); //<----- A a2(f2); return a1.doit(i) + a2.doit(2); } /usr/local/devl/src/incl/boost/bind.hpp: In method `int boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> >::operator ()<int, boost::_mfi::mf2<int,B,const D *,int>, boost::_bi::list1<int &> >(boost::_bi::type<int>, boost::_mfi::mf2<int,B,const D *,int>, boost::_bi::list1<int &> &) const': /usr/local/devl/src/incl/boost/bind/bind_template.hpp:33: instantiated from `boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >::operator ()<int>(int &)' /usr/local/devl/src/incl/boost/function/function_template.hpp:110: instantiated from `boost::detail::function::function_obj_invoker1<boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >,int,int>::invoke(boost::detail::function::any_pointer, int)' /usr/local/devl/src/incl/boost/function/function_template.hpp:437: instantiated from `boost::function1<int,int,boost::empty_function_policy,boost::empty_function_mixin,allocator<boost::function_base> >::assign_to<boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > > >(boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >, boost::detail::function::function_obj_tag)' /usr/local/devl/src/incl/boost/function/function_template.hpp:388: instantiated from `boost::function1<int,int,boost::empty_function_policy,boost::empty_function_mixin,allocator<boost::function_base> >::assign_to<boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > > >(boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >)' /usr/local/devl/src/incl/boost/function/function_template.hpp:274: instantiated from `boost::function1<int,int,boost::empty_function_policy,boost::empty_function_mixin,allocator<boost::function_base> >::function1<boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > > >(boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >)' /usr/local/devl/src/incl/boost/function.hpp:459: instantiated from `boost::function<int,int,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable,boost::detail::function::unusable>::function<boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > > >(boost::_bi::bind_t<int,boost::_mfi::mf2<int,B,const D *,int>,boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> > >)' testBoost.C:61: instantiated from here /usr/local/devl/src/incl/boost/bind.hpp:263: no match for call to `(boost::_mfi::mf2<int,B,const D *,int>) (B *const &, int &, D *const &)' /usr/local/devl/src/incl/boost/bind/mem_fn_template.hpp:212: candidates are: int boost::_mfi::mf2<int,B,const D *,int>::operator ()(B *, const D *, int) const /usr/local/devl/src/incl/boost/bind/mem_fn_template.hpp:217: int boost::_mfi::mf2<int,B,const D *,int>::operator ()<B *const>(B *const &, const D *, int) const /usr/local/devl/src/incl/boost/bind/mem_fn_template.hpp:222: int boost::_mfi::mf2<int,B,const D *,int>::operator ()(B &, const D *, int) const /usr/local/devl/src/incl/boost/bind.hpp:263: warning: control reaches end of non-void function `boost::_bi::list3<boost::_bi::value<B *>,boost::arg<1>,boost::_bi::value<D *> >::operator ()<int, boost::_mfi::mf2<int,B,const D *,int>, boost::_bi::list1<int &> >(boost::_bi::type<int>, boost::_mfi::mf2<int,B,const D *,int>, boost::_bi::list1<int &> &) const'

2 3

RE: [Boost-Users] boost::polymorphic_upcast suggestion
by Jim.Hyslop 27 Jun '02

27 Jun '02

Jean Llorca (yg-boost-users(a)gmane.org) wrote: > I would like to propose, in the spirit of Bjarne Stroustrup book, > an upcast (where target inherits source). Upcasting is already directly supported by the language. Given classes Base and Derived, with the public inheritance implied by their names, then: Derived d; Base * b=&d; Base & br = d; will work without any casting whatsoever. When the compiler compiles this code, it has the definitions of classes Base and Derived available, so all the work can be performed at compile time. > template <class Target, class Source> > inline Target polymorphic_upcast(Source* x > BOOST_EXPLICIT_DEFAULT_TARGET) > { > > typedef unsigned int uint; > > > uint offset = reinterpret_cast<uint>( static_cast<Source*>( > reinterpret_cast<Target>(1) ) ) - 1; > Target res = reinterpret_cast<Target>( > reinterpret_cast<uint>( x ) - > offset ); > > assert( res == dynamic_cast<Target>(x) ); > > return res; > } I don't understand this - how is casting a Target to an unsigned int going to help? Did you perhaps mean Target * in the above example, or have I missed something? -- Jim

4 4

boost::polymorphic_upcast suggestion
by Jean Llorca 27 Jun '02

27 Jun '02

Hi, I would like to propose, in the spirit of Bjarne Stroustrup book, an upcast (where target inherits source). template <class Target, class Source> inline Target polymorphic_upcast(Source* x BOOST_EXPLICIT_DEFAULT_TARGET) { typedef unsigned int uint; uint offset = reinterpret_cast<uint>( static_cast<Source*>( reinterpret_cast<Target>(1) ) ) - 1; Target res = reinterpret_cast<Target>( reinterpret_cast<uint>( x ) - offset ); assert( res == dynamic_cast<Target>(x) ); return res; } It would be faster to use the polymorphic_upcast, since it doesn't use dynamic_cast in NDEBUG. Regards, Jean Llorca.

1 0

RegEx++ and vc7 heap/memory error
by john_p_osborn 26 Jun '02

26 Jun '02

When executing the following code I get an _CrtIsValidHeapPointer error in dbgheap.c: boost::RegEx r; std:string sTmp; std:string sExp = "\\bContent-Type:":\\s*([^; ]{1,16})""; r.SetExpression(sExp, true); if (!r.Search((LPCTSTR)(pInputBytes))) { ... error } else { sTmp = r2[1]; } If I change sExp to specify {1,15} it works. Anybody know what's going on? I'm using 1_28_0 with Visual Studio .NET

1 0

Regex problems with HP aCC
by dufr0017 26 Jun '02

26 Jun '02

I am trying to build the Regex library for hp_ux 11.0 using aCC version 3.33. I have tried both the current CVS version and version 1.28 of Boost. With either one, I get the same errors. Below is the full text of my error message. I have been able to build successfully on many other platforms. I found a message in the archives, accessible at http://lists.boost.org/MailArchives/boost/msg29179.php, where another user has experienced a similar problem. Has anyone solved this problem, or could any offer a possible fix? Is anyone using Regex on HP_UX? If so, any tips on configuration, etc, would be greatly appreciated. I am stumped by this one. Thanks in advance for your help, Mark Dufresne Here is the error: aCC -o hp_ux/boost_regex/cregex.o -c -I../../../ +Z -AA -mt +DAportable -g0 +W749 ../src/cregex.cpp Error 619: "../../../boost/regex/detail/regex_match.hpp", line 1781 # The definition of template iterator_traits<boost::detail::allocator_adapter<char,boost::detail::s imple_alloc> > contains typename qualification '_Iterator::iterator_category', yet generation of specialization struct iterator_traits<boost::detail::allocator_adapter<char,boost::detail::s imple_alloc> > implies that '_Iterator' is 'class allocator_adapter<char,boost::detail::simple_alloc>', which does not contain a type named 'iterator_category'. return re_detail::reg_grep(re_detail::grep_search_predicate<iterator, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Error 618: Exact position unknown; near ["../../../boost/regex/detail/regex_match.hpp", line 1781]. # The definition of template iterator_traits<template#0> contains typename qualification '_Iterator::value_type', yet generation of specialization struct iterator_traits<template#0> implies that '_Iterator' is 'tentative class template#0', which is incomplete. Error 445: "../../../boost/regex/detail/regex_match.hpp", line 1781 # Cannot recover from earlier errors. return re_detail::reg_grep(re_detail::grep_search_predicate<iterator, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** Error exit code 2

1 0

boost.python and g++ 3.1 - Help needed
by jfo60540 26 Jun '02

26 Jun '02

Hi - I am trying to recompile code that compiles cleanly with g++ 3.0.4 with g++ 3.1. I get the following error messages, which, I am affraid, I cannot decipher. Any hints would be greatly appreciated. -Francois g++ -c -g -fPIC -DBOOST -I/usr/local/ap/include/python2.2 -I/usr/local/ap/PLplot/include -I/usr/local/ap/galib/include -o pymathlib.o pymathlib.cc/usr/local/ap/include/boost/python/cross_module.hpp: In instantiation of `SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<SuperCode::Vector<Real>&>, bool)': /usr/local/ap/include/boost/python/caller.hpp:1093: instantiated from `static PyObject* boost::python::caller<void>::call(void (*)(A1, A2, A3), PyObject*, PyObject*) [with A1 = SuperCode::Vector<Real>&, A2 = const SuperCode::Vector<Real>&, A3 = const SuperCode::Vector<Real>&]' /usr/local/ap/include/boost/python/detail/functions.hpp:73: instantiated from `PyObject* boost::python::detail::wrapped_function_pointer<R, F>::do_call(PyObject*, PyObject*) const [with R = Void, F = Void (*)(SuperCode::Vector<Real>&, const SuperCode::Vector<Real>&, const SuperCode::Vector<Real>&)]' /usr/local/ap/include/boost/function/function_base.hpp:153: instantiated from here /usr/local/ap/include/boost/python/cross_module.hpp:91: default argument given for parameter 3 of `SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<SuperCode::Vector<Real>&>, bool = false)' /usr/local/ap/include/boost/python/cross_module.hpp:91: after previous specification in `SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<SuperCode::Vector<Real>&>, bool = false)' /usr/local/ap/include/boost/python/cross_module.hpp: In instantiation of `const SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<const SuperCode::Vector<Real>&>, bool)': /usr/local/ap/include/boost/python/caller.hpp:1093: instantiated from `static PyObject* boost::python::caller<void>::call(void (*)(A1, A2, A3), PyObject*, PyObject*) [with A1 = SuperCode::Vector<Real>&, A2 = const SuperCode::Vector<Real>&, A3 = const SuperCode::Vector<Real>&]' /usr/local/ap/include/boost/python/detail/functions.hpp:73: instantiated from `PyObject* boost::python::detail::wrapped_function_pointer<R, F>::do_call(PyObject*, PyObject*) const [with R = Void, F = Void (*)(SuperCode::Vector<Real>&, const SuperCode::Vector<Real>&, const SuperCode::Vector<Real>&)]' /usr/local/ap/include/boost/function/function_base.hpp:153: instantiated from here /usr/local/ap/include/boost/python/cross_module.hpp:94: default argument given for parameter 3 of `const SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<const SuperCode::Vector<Real>&>, bool = false)' /usr/local/ap/include/boost/python/cross_module.hpp:94: after previous specification in `const SuperCode::Vector<Real>& boost::python::from_python(PyObject*, boost::python::type<const SuperCode::Vector<Real>&>, bool = false)'

2 1

not enough space for thread data
by Andreas Olsson 26 Jun '02

26 Jun '02

Hi As you can see in the subject this is a newbie problem. I tried the example code "Simple usage of boost::thread" (http://www.boost.org/libs/thread/doc/thread.html) with MSVC 6.0 and ended up with an error message: R6016 - not enough space for thread data Are there any settings that must be set before this code will work? Regards Andreas

1 0

compilation problem on solaris-gcc with stlport
by Virginia Volk 25 Jun '02

25 Jun '02

Does anyone know why I am seeing problems? I am trying to compile boost on a SunOS 5.6 with gcc 2.95.3, using stlport 4.5.3. I use the following cmd: bjam_solaris -a "-sTOOLS=gcc-stlport" "-sBuild= debug release <stlport-iostream>on" "-sBUILD=debug release <runtime-link>static/dynamic" "-sSTLPORT_ROOT=/core/elements/cots/stlport-4.5.3" And I get errors such as: In file included from /core/elements/cots/stlport-4.5.3/stlport/stl/_iterator_base.h:38, from /core/elements/cots/stlport-4.5.3/stlport/stl/_algobase.h:55, from /core/elements/cots/stlport-4.5.3/stlport/stl/_list.h:34, from /core/elements/cots/stlport-4.5.3/stlport/list:35, from libs/regex/build/../src/c_regex_traits.cpp:27: /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h: At top level: /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h:68: template with C linkage /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h:80: template with C linkage /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h:91: template with C linkage /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h:92: template with C linkage /core/elements/cots/stlport-4.5.3/stlport/stl/type_traits.h:213: template with C linkage ...failed gcc-C++-action libs/regex/build/bin/libboost_regex.a/gcc-stlport/release/runtime-link-d ynamic/regex.o... gcc-C++-action gcc-C++libs/regex/build/bin/libboost_regex.a/gcc-stlport/release/runtime gcc-C++-link-dynamic/regex_debug.o In file included from /core/elements/cots/stlport-4.5.3/stlport/stl/_alloc.h:64, from /core/elements/cots/stlport-4.5.3/stlport/memory:28, from /core/elements/cots/stlport-4.5.3/stlport/stl/_string.h:23, from /core/elements/cots/stlport-4.5.3/stlport/string:42, from /core/elements/cots/boost-1.28.0/boost/regex/config.hpp:86, from libs/regex/build/../src/regex_debug.cpp:26: /core/elements/cots/stlport-4.5.3/stlport/stl/_threads.h:207: template with C linkage /core/elements/cots/stlport-4.5.3/stlport/stl/_threads.h:406: parse error before `&' /core/elements/cots/stlport-4.5.3/stlport/stl/_threads.h:407: parse error before `&' /core/elements/cots/stlport-4.5.3/stlport/stl/_threads.h:407: `_STL::_STLP_mutex::operator =(...)' must take exactly one argum /core/elements/cots/stlport-4.5.3/stlport/stl/_threads.h:408: confused by earlier errors, bailing out Thank you, Virginia

4 7

[BGL] Newbie problems with property_map interface
by Erik Arner 24 Jun '02

24 Jun '02

Hi, I'm just starting to learn how to use BGL, and have a few questions. Help would be much appreciated. I'm currently trying to understand the add_vertex function where properties can be assigned to the vertices as the graph is constructed. The only info I've managed to find on the website is this: --------- vertex_descriptor add_vertex(const VertexProperties& p, adjacency_list& g) Adds a vertex to the graph with the specified properties. Returns the vertex descriptor for the new vertex. --------- Does anybody have any examples on how to use this? More specifically, consider the following. I want to construct a graph dynamically, i.e. the graph will grow and shrink during runtime. Let's say I have a Node class with one member (which I want to represent as an "internal property") as follows: class Node { public: std::string name; }; And an Edge class, again with internal properties: class Edge { public: int weight1; double weight2; }; Then my graph object would look something like this, right? typedef adjacency_list < vecS, vecS, directedS, property < vertex_name_t, std::string >, property <edge_weight_t, int, property <edge_weight2_t, double> > > Graph; Where do I go from here? That is, if I have a Node or Edge object in my hand, with members as specified above, how do I add it to the structure (provided that additional info is available regarding which Nodes to connect with the Edge)? I would be very grateful for any help on this. Also, pointers to good (online) tutorials and documented examples of using the BGL, aside from the ones on boost.org, would be appreciated. Thanks, Erik

2 1

VC7 + STLPort (and other assorted questions)
by juxtaposenj 24 Jun '02

24 Jun '02

Is there any way to force boost to build using VC7 and STLPort? I tried the obvious (settings TOOLS=msvc-stlport, and setting MSVC_DIR=<path to VC7>), but I got a ton of compiler errors that way. I ask because VC6 + STLPort 4.5.3 has some serious issues with the the VC6 compiler, causing internal compiler errors (very bad :P). Also, I keep hearing mention of a way to build the boost libs from inside the VC IDE (and the ability to build them for static linking), but I can't find project files, or a Jam option to build static. What am I missing? This is all Boost 1.28.0. Matt Holmes

3 2

regex, stringbuf and MSVC++ 6
by the_d.geo 24 Jun '02

24 Jun '02

What follow is the descriptions of a possible bug. Unfortunately I'm using MSVC++ and ran into some unexpected behavior using boost::regex_format and a stringbuf. I compiled 1.27.0 without the /Oa flag as suggested in the installation notes. In summary, this works: stringbuf line; ... string tmp = line.str(); if (regex_match(tmp, matchInfo, linerx)) { string name = regex_format(matchInfo, "$1"); } but this doesn't: stringbuf line; ... if (regex_match(line.str(), matchInfo, linerx)) { string name = regex_format(matchInfo, "$1"); } By "doesn't work" I mean that 'name' has spurious characteres. If this might be a bug, let me know and I'll track it down to a small, compilable example.

4 4