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

Re: problem with c_regex_traits.cpp
by René Gutschmidt 06 Jun '02

06 Jun '02

>> i have problems with the file c_regex_traits.cpp. I work under CodeWarrior >> 6/7 with a Macintosh. >> These problem ist with boost 1.25.1,1.26. >> >> template <class charT> >> unsigned int BOOST_REGEX_CALL re_get_message(charT* buf, unsigned int >> len, unsigned int id) >> { >> unsigned int size = _re_get_message((char*)0, 0, id); >> if(len < size) >> return size; >> boost::scoped_array<char> cb(new char[size]); >> _re_get_message(cb.get(), size, id); >> size = boost::c_regex_traits<wchar_t>::strwiden(buf, len, cb.get()); >> return size; >> } >> >> inline unsigned int BOOST_REGEX_CALL re_get_message(char* buf, unsigned >> int len, unsigned int id) >> { >> return _re_get_message(buf, len, id); >> } >> >> Is that a known problem? Do you know a workaround? >> (Renaming one of the 're_get_message()' functions does >> the job, but I'm not sure about the implications.) > > I've had a chance to experiment a little with this - if BOOST_NO_WREGEX is > defined (i.e. wide character support is disabled), then removing the > template version of re_get_message is harmless (and may therefore be the fix > that you are looking for). If BOOST_NO_WREGEX is not defined, then > obviously this won't work - so that being the case, what happens if you > surround the definition of > > template <class charT> > unsigned int BOOST_REGEX_CALL re_get_message(charT* buf, unsigned int len, > unsigned int id) > > with > > #ifndef BOOST_NO_WREGEX > ... > #endif > > regards, > > John Maddock Sorry, but I haven't had a chance to answer. Ok it's works. But I need 'wide character support' much later. best regards, Rene Gutschmidt

2 4

RE: [Boost-Users] Re: boost::noncopyable usage question
by Michael Davis 06 Jun '02

06 Jun '02

Thank you for the clarification. :) -----Original Message----- From: Darin Adler To: Boost-Users(a)yahoogroups.com Sent: 6/6/2002 12:57 AM Subject: Re: [Boost-Users] Re: boost::noncopyable usage question On Wednesday, June 5, 2002, at 03:14 PM, Michael Davis wrote: > According to the C++ Standard, 12.8/10, the assignment operator cannot > be > inherited because if it is not provided, the compiler will provide one > implicitly. Or at least, that is my understanding of it. > > Given this, how can boost::noncopyable work? The assignment operator provided by the compiler for the class derived from noncopyable has to copy the part of the object that's inherited from noncopyable. To do that, it has to use the assignment operator from the noncopyable class; but if it's inaccessible, like the private one in noncopyable, it has to report an error. This rule is mentioned in 12.8/14. -- Darin 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

type_traits::is_POD<> problem
by s9801758 06 Jun '02

06 Jun '02

Hello, I'm using MSVC6.0 with service-pack 6.0 installed. But I'm getting some weird problems. Consider the following simple program: ---------------------------------------------------- struct q { int x; }; int main() { int t; t = boost::is_POD< int >::value; // Ok, t = true; t = boost::is_POD< void >::value; // Ok?, t = true (is 'void' considered a POD?); t = boost::is_POD< q >::value; // Error, t = false } ---------------------------------------------------- Unless my definition of a POD type is incorrect, I think that q is considered POD, right? Am I doing something wrong here, or is the combination boost and msvc fatal once again? Just to be complete, I have the following defines in my main header: #define BOOST_NO_FUNCTION_PTR_TEMPLATE_PARAMETERS #define BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION Thanks in advance, Jaap Suter

2 1

Boost regex and MacOS X.
by Mystical Catty Tananeka 06 Jun '02

06 Jun '02

I've been trying to make MacOS X compile the example snippets from boost_1_28_0/libs/regex/example/snippets/ and I keep getting these messy link errors. It looks like /usr/bin/c++ is having trouble linking to libboost_regex.a here's an example: localhost% c++ -o regex_grep_example_1 regex_grep_example_1.cpp -lboost_regex /usr/bin/ld: Undefined symbols: __._Q25boostt14reg_expression3ZcZQ25boostt12regex_traits1ZcZt9allocator1Zc ___Q25boostt14reg_expression3ZcZQ25boostt12regex_traits1ZcZt9allocator1ZcPCc UiRCB2 ___Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1ZcRCB1 _allocator__CQ25boostt14reg_expression3ZcZQ25boostt12regex_traits1ZcZt9alloc ator1Zc _allocator__CQ35boost9re_detailt18match_results_base2ZPCcZt9allocator1Zc _cow__Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1Zc _m_free__Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1Zc _set_first__Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1ZcPCc _set_first__Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1ZcPCcUl _set_size__Q35boost9re_detailt18match_results_base2ZPCcZt9allocator1ZcUlPCcn 1 localhost% I haven't enough experience with boost to know how to fix this, or even what it means, exactly. If its informative, c++ -v returns: Apple Computer, Inc. version gcc-934.3, based on gcc version 2.95.2 19991024 (release)

2 1

BGL: subgraph<..> Problems
by Matthias Kronenberger 06 Jun '02

06 Jun '02

1. How to create a subgraph from a given simple boost graph type? 2. Why are modell subgraph not the same concept as the underlying graph type? Why are not all non-member function defined for the only graph modell adjacence_list<> also available for subgraph? 3. I've defined something like class NG { public: typedef boost::property<boost::vertex_all_t, SomeIterator, Vertex_Property > vertex_SPIterator_Prop; // GridSP_type::iterator typedef Default::Graph<vertex_SPIterator_Prop, Edge_Property>::Subgraph::Undirected Graph; ... }; where struct Default { ..... template<class VertexProperties=boost::no_property, class EdgeProperties=boost::no_property, class GraphProperties=boost::no_property, class EdgeList=boost::hash_setS, class VertexList=boost::listS > struct Graph { ........ struct Subgraph { typedef typename boost::subgraph < boost::adjacency_list<EdgeList, VertexList, boost::undirectedS, boost::property<boost::vertex_index_t,int, VertexProperties>, boost::property<boost::edge_index_t, int, EdgeProperties > ,GraphProperties> > Undirected; }; .... }; and then i'm doing somewhere else { vertex_descriptor v=boost::add_vertex( theGraph); IteratorMap[Prop ] =v; boost::put( boost::vertex_all_t() , theGraph, v, Prop); return v; } I get a nice error with MSVC 6.5 d:\matthias\programmieren\boost\boost\graph\subgraph.hpp(751): error C2679: Binaerer Operator '=': Kein Operator definiert, der einen rechtsseitigen Operator vom Typ 'const _Ht_iter<pair<int const,surrect::PNSurfel<vectorD<float,3>>>,_Nonconst_trait............ (no operator= defined for the type conversion used in put pmap[k] = val;) But using a simple adjacence_list<..> instead of the subgraph< adjacence_list<...> this mess compiles fine. What am i doing wrong? Are there better ways to create a property map containing (const) iterators, that don't modell STL::RandomAccesIterator? Matthias

1 0

RE: [Boost-Users] Re: boost::noncopyable usage question
by Michael Davis 06 Jun '02

06 Jun '02

According to the C++ Standard, 12.8/10, the assignment operator cannot be inherited because if it is not provided, the compiler will provide one implicitly. Or at least, that is my understanding of it. Given this, how can boost::noncopyable work?

2 1

RE: [Boost-Users] boost::noncopyable usage question
by Mark Storer 05 Jun '02

05 Jun '02

This is more of a C++ question than a boost one (which is why I can answer it;). Your deletes are fine. The only way this would cause a problem is to delete through a boost::noncopyable pointer (in which case everything derived from it would leak). I'm guessing the author, Dave Abrahams, didn't think anyone was going to declare a noncopyable*, so decided to pass on that little bit of extra overhead involved in declaring a destructor virtual. Or it could be a mistake. Dave has posted to this list at least once... So tell us, did you mean to leave it non-virtual? --Mark Storer Software Engineer Cardiff Software #include <disclaimer> typedef std::disclaimer<Cardiff> Discard; -----Original Message----- From: Bobby Thomale [mailto:bthomale@mac.com] Sent: Wednesday, June 05, 2002 9:30 AM To: Boost Users List Subject: [Boost-Users] boost::noncopyable usage question I have a simple question about the usage of boost::noncopyable. I think I know the answer, but I am not sure. The noncopyable class defines a non-virtual destructor. Generally speaking, overriding a non-virtual destructor is considered a "bad thing" but in certain cases (like, I am guessing, this one) it is okay and works like you'd expect. Here's what I am worried about: Let's say I have a base class of an inheritance tree that I want to be non-copyable. So I do this: class MyBase : private boost::noncopyable { public: MyBase (); virtual ~MyBase (); ... }; Then I derive from it class A: class A : public MyBase { public: A (); virtual ~A(); }; and define a destructor for class A, too. Does this do what I would expect, ie whether I delete a MyBase* or an A*, it calls the destructors for both A and MyBase like it is supposed to? I suppose the trivial, empty noncopyable destructor never gets called (which is okay) whether I delete a MyBase* or an A*, correct? (Just curious...) -- Bobby --------------------------------------------------------------------- Bobby Thomale Senior Software Developer Inoveon Corporation http://www.inoveon.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/

4 3

boost::noncopyable usage question
by Bobby Thomale 05 Jun '02

05 Jun '02

I have a simple question about the usage of boost::noncopyable. I think I know the answer, but I am not sure. The noncopyable class defines a non-virtual destructor. Generally speaking, overriding a non-virtual destructor is considered a "bad thing" but in certain cases (like, I am guessing, this one) it is okay and works like you'd expect. Here's what I am worried about: Let's say I have a base class of an inheritance tree that I want to be non-copyable. So I do this: class MyBase : private boost::noncopyable { public: MyBase (); virtual ~MyBase (); ... }; Then I derive from it class A: class A : public MyBase { public: A (); virtual ~A(); }; and define a destructor for class A, too. Does this do what I would expect, ie whether I delete a MyBase* or an A*, it calls the destructors for both A and MyBase like it is supposed to? I suppose the trivial, empty noncopyable destructor never gets called (which is okay) whether I delete a MyBase* or an A*, correct? (Just curious...) -- Bobby --------------------------------------------------------------------- Bobby Thomale Senior Software Developer Inoveon Corporation http://www.inoveon.com/ ---------------------------------------------------------------------

2 2

Tupls browsing...
by Igor Korzinek 04 Jun '02

04 Jun '02

Hi, I did not take a look at the tuple internals, but it seems that there is some head-tail connection probably built in compile time. So can someone from template gurus answer if it makes sense and if it is possible to add some method that will make sequential access possible. Some function that will getNext() or some kind of search within a tuple ? Is it too stupid or just impossible ? Igor

1 0

Is it worth using if I use MSVC
by Igor Korzinek 04 Jun '02

04 Jun '02

Hi, I'm new to boost. The doc I've browsed seems fine and something what I need. I'm focusing on TUPLEs part. So, besides mentioned cref and ref stuff, is there any other issue I can expect with awful (but a must for me) MS VC 6 ? And are there any sample for using this part of boost ? THX, Igor

1 1