- Boost-users - lists.boost.org

Base Pointer member functions failure
by Mark Loew 26 Sep '03

26 Sep '03

Okay, Call me stupid but I can't get this to work class Base { virtual const bool CheckFunc(const value& val ) const { return true; } } class Derived1: public Base { } class Derived2: public Base { } // some where else in code Derived1 dev1; Derived2 dev2; vector<Base *> vecBase; vecBase.push_back( &dev1 ); vecBase.push_back( &dev2 ); value aVal; vec<Base *> std::find_if( vecBase.begin(), vecBase.end(), boost::bind( Base::CheckFunc, aVal ) ); I have tried a gazillion things a thought would work using mem_fun_ref and such. This ones get's me the closest I believe but I get a bunch of qualifier to funcation type has no meaning warnings. As well I get a condiation expression of type 'overloaded-function is illegal. I am using VS.Net 2003. Any ideas on what I am missing. As well can I get my cake and eat it to by making the CheckFunc virtual and have it resolve to the derived form? TIA Mark Loew, MCSD, MCSE Application Development Consultant Sagestone Consulting www.sagestone.com <http://www.sagestone.com/> Grand Rapids, MI 616-954-9556 x149 Microsoft Gold Certified Partner mloew(a)sagestone.com

3 2

boost regex and match_partial
by Angus Leeming 26 Sep '03

26 Sep '03

I'm afraid I haven't got the hang of match_partial. Below is a little code with two functions that I think should produce identical results, but don't. In strip_commas_try1 I use: boost::regex const front("^( *[[],*)(.*)$"); regex_match(it, end, what, front); In strip_commas_try2 I use: boost::regex const front("^( *[[],*)"); regex_match(it, end, what, front, boost::match_partial); Why does this second case not result in what[0].matched ? Many thanks, Angus (This is with BOOST_VERSION 103002 and g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)). #include<iostream> #include<string> #include <boost/regex.hpp> using std::string; string const strip_commas_try1(string const & input) { string::const_iterator it = input.begin(); string::const_iterator end = input.end(); // Strip any commas that follow immediately after the '['. // "[,,,,foo..." -> "foo..." boost::regex const front("^( *[[],*)(.*)$"); boost::smatch what; regex_match(it, end, what, front); if (!what[0].matched) { std::cout << "Try 1 failed" << std::endl; return string(); } it = what[1].second; string const result = string(it, end); std::cout << "Try 1: " << result << std::endl; return result; } string const strip_commas_try2(string const & input) { string::const_iterator it = input.begin(); string::const_iterator end = input.end(); // Strip any commas that follow immediately after the '['. // "[,,,,foo..." -> "foo..." boost::regex const front("^( *[[],*)"); boost::smatch what; regex_match(it, end, what, front, boost::match_partial); if (!what[0].matched) { std::cout << "Try 2 failed" << '\n'; return string(); } it = what[1].second; string const result = string(it, end); std::cout << "Try 1: " << result << std::endl; return result; } int main() { string const input = "[,,,foo,,,,bar,,,gaz,,]"; std::cout << "Input: " << input << std::endl; strip_commas_try1(input); strip_commas_try2(input); return 0; }

1 0

indirect_iterator_generator and std::distance ambiguity
by Jeff Flinn 24 Sep '03

24 Sep '03

I'm having problems compiling the code below with boost_1_30_2 and VC71 complaining about: ...\Microsoft Visual Studio .NET 2003\Vc7\include\xutility(489) : error C2665: 'std::_Distance2' : none of the 4 overloads can convert parameter 4 from type 'std::iterator_traits<_Iter>::iterator_category' with [ _Iter=CDictionary::tVarConstItr ] ... Replacing with std::distance( lBeg.base(), lItr.base() ) does compile and work properly. Am I missing something in the typedef of tVarConstItr that would allow direct usage? ---------------------------------------------------------- class CDictionary { ... class VarSpec { ... typedef boost::shared_ptr<VarSpec> tPtr; }; typedef VarSpec tVar; typedef tVar::tPtr tVarPtr; typedef std::vector<tVarPtr> tVars; typedef boost::indirect_iterator_generator < tVars::const_iterator , tVar , tVar& , tVar* , std::iterator_traits<tVars::const_iterator> ::iterator_category >::type tVarConstItr; typedef boost::indirect_iterator_generator < tVars::iterator , tVar , tVar& , tVar* , std::iterator_traits<tVars::iterator> ::iterator_category >::type tVarItr; tGroups Groups()const{ return mGroups; } tVarItr VarBegin() { return tVarItr ( mVars.begin() ); } tVarItr VarEnd () { return tVarItr ( mVars.end () ); } tVarConstItr VarBegin()const{ return tVarConstItr( mVars.begin() ); } tVarConstItr VarEnd ()const{ return tVarConstItr( mVars.end () ); } }; usage: ------ int CDictionaryEditorView::Idx( const TCHAR* aChrPtr, bool aExact )const { boost::function1<bool,const CDictionary::VarSpec&> lFindFnc; if( aExact ) { lFindFnc = boost::bind( std::equal_to<std::string>() , std::string(aChrPtr) , boost::bind( &CDictionary::VarSpec::Name, _1 ) ); } else { //... } CDictionary::tVarConstItr lBeg = mDctPtr->VarBegin(); CDictionary::tVarConstItr lEnd = mDctPtr->VarEnd (); CDictionary::tVarConstItr lItr = std::find_if( lBeg, lEnd, lFindFnc ); return (lItr!=lEnd)? std::distance( lBeg, lItr ) : -1; } -- Jeff Flinn Applied Dynamics, International

2 3

[bgl] how to reverse a graphvizDigraph?
by Jeremie Leguay 24 Sep '03

24 Sep '03

Hi! I would like to reverse all the edges of a graphviz graph but the structure of this kind of graph doesn't seems to fit with the one use by the reverse_graph functionalities. Am I true or did I forget something? Here is the code that doesnt work: GraphvizDigraph g; read_graphviz("datas",g); typedef reverse_graph<GraphvizDigraph> ReverseGraphType; ReverseGraphType gr(g); print_graph(gr, get(vertex_index, gr)); //if I remove this line, it works! More generally, I would like to inverse the graph with keeping the same indexes on the vertices. Do you have ideas? best regards /Jeremie Leguay

1 0

regex problem
by Scott McCaskill 24 Sep '03

24 Sep '03

I seem to be having some trouble with the regex library: #include <boost/regex.hpp> #include <cassert> #include <iostream> int main(int argc, char* argv[]) { using namespace boost; cmatch what; assert(regex_match("foo: bar", what, regex("([\\w]+):[\\s]*(.*)"))); assert(what.size() == 3); assert(what[1].matched); assert(what[2].matched); assert(std::string("foo") == std::string(what[1])); std::cout << std::string(what[2]) << "\n"; assert(std::string("bar") == std::string(what[2])); // fails return 0; } The last assert always fails, because regex::match insists on including the space after the ":" in the second match result, which seems wrong to me. I've tried giving various different combinations of flags to the regex ctor, although from what I can tell from the documentation the default flags should work. This is with VC7 and boost 1.30.2. For comparison, perl (5.6.1) does not seem to have this problem, as the following script illustrates: #!/usr/bin/perl print "matches: <$1> <$2>\n" if ('foo: bar' =~ /([\w]+):[\s]*(.*)/); Is there any way to get the behavior I want? Thanks, Scott McCaskill

1 0

Regex and stream processing
by Yaroslav Govorunov 23 Sep '03

23 Sep '03

Hello everybody and especially Dr John Maddock :) ! First of all I wish to thank all developers for this amazing product. I come here to get an advice and here is my problem: We have a stream of text data (actually it is a chunked response of a webserver, but it might be a file or something...) The data size may be very large and we need to do some find/replace in this stream using regular expressions. It is not possible to load entire stream into the memory. I'm not even hope that Regex++ could work with such kind of streams, but maybe someone can suggest me a solution to this problem? With best regards, Yaroslav Govorunov, E-mail: slov(a)rsdn.ru http://www.rsdn.ru http://www.isapirewrite.com

1 0

Preprocessor Library question
by Eric Robert 23 Sep '03

23 Sep '03

Hi, Maybe somebody can help me here. I'm just trying to understand what's going on with the FOR code. It goes something like this (I expanded the general include and stripped some code for clarity) : # define BOOST_PP_FOR BOOST_PP_CAT(BOOST_PP_FOR_, BOOST_PP_AUTO_REC(BOOST_PP_FOR_P, 256)) # # define BOOST_PP_FOR_P(n) BOOST_PP_CAT(BOOST_PP_FOR_CHECK_, BOOST_PP_FOR_ ## n(1, BOOST_PP_FOR_SR_P, BOOST_PP_FOR_SR_O, BOOST_PP_FOR_SR_M)) # # define BOOST_PP_FOR_SR_P(r, s) s # define BOOST_PP_FOR_SR_O(r, s) 0 # define BOOST_PP_FOR_SR_M(r, s) BOOST_PP_NIL # # define BOOST_PP_FOR_1(s, p, o, m) BOOST_PP_FOR_1_C(BOOST_PP_BOOL(p(2, s)), s, p, o, m) # define BOOST_PP_FOR_2(s, p, o, m) BOOST_PP_FOR_2_C(BOOST_PP_BOOL(p(3, s)), s, p, o, m) # define BOOST_PP_FOR_3(s, p, o, m) BOOST_PP_FOR_3_C(BOOST_PP_BOOL(p(4, s)), s, p, o, m) # define BOOST_PP_FOR_4(s, p, o, m) BOOST_PP_FOR_4_C(BOOST_PP_BOOL(p(5, s)), s, p, o, m) # define BOOST_PP_FOR_5(s, p, o, m) BOOST_PP_FOR_5_C(BOOST_PP_BOOL(p(6, s)), s, p, o, m) # # // # // EXTENDED include <boost/preprocessor/repetition/detail/for.hpp> # # define BOOST_PP_FOR_1(s, p, o, m) BOOST_PP_FOR_1_C(BOOST_PP_BOOL(p(2, s)), s, p, o, m) # define BOOST_PP_FOR_2(s, p, o, m) BOOST_PP_FOR_2_C(BOOST_PP_BOOL(p(3, s)), s, p, o, m) # define BOOST_PP_FOR_3(s, p, o, m) BOOST_PP_FOR_3_C(BOOST_PP_BOOL(p(4, s)), s, p, o, m) # define BOOST_PP_FOR_4(s, p, o, m) BOOST_PP_FOR_4_C(BOOST_PP_BOOL(p(5, s)), s, p, o, m) # define BOOST_PP_FOR_5(s, p, o, m) BOOST_PP_FOR_5_C(BOOST_PP_BOOL(p(6, s)), s, p, o, m) # # define BOOST_PP_FOR_1_C(c, s, p, o, m) BOOST_PP_IIF(c, m, BOOST_PP_TUPLE_EAT_2)(2, s) BOOST_PP_IIF(c, BOOST_PP_FOR_2, BOOST_PP_TUPLE_EAT_4)(BOOST_PP_EXPR_IIF(c, o)(2, s), p, o, m) # define BOOST_PP_FOR_2_C(c, s, p, o, m) BOOST_PP_IIF(c, m, BOOST_PP_TUPLE_EAT_2)(3, s) BOOST_PP_IIF(c, BOOST_PP_FOR_3, BOOST_PP_TUPLE_EAT_4)(BOOST_PP_EXPR_IIF(c, o)(3, s), p, o, m) # define BOOST_PP_FOR_3_C(c, s, p, o, m) BOOST_PP_IIF(c, m, BOOST_PP_TUPLE_EAT_2)(4, s) BOOST_PP_IIF(c, BOOST_PP_FOR_4, BOOST_PP_TUPLE_EAT_4)(BOOST_PP_EXPR_IIF(c, o)(4, s), p, o, m) # define BOOST_PP_FOR_4_C(c, s, p, o, m) BOOST_PP_IIF(c, m, BOOST_PP_TUPLE_EAT_2)(5, s) BOOST_PP_IIF(c, BOOST_PP_FOR_5, BOOST_PP_TUPLE_EAT_4)(BOOST_PP_EXPR_IIF(c, o)(5, s), p, o, m) # define BOOST_PP_FOR_5_C(c, s, p, o, m) BOOST_PP_IIF(c, m, BOOST_PP_TUPLE_EAT_2)(6, s) BOOST_PP_IIF(c, BOOST_PP_FOR_6, BOOST_PP_TUPLE_EAT_4)(BOOST_PP_EXPR_IIF(c, o)(6, s), p, o, m) # # define BOOST_PP_FOR_257(s, p, o, m) BOOST_PP_ERROR(0x0002) # # define BOOST_PP_FOR_CHECK_BOOST_PP_NIL 1 # # define BOOST_PP_FOR_CHECK_BOOST_PP_FOR_1(s, p, o, m) 0 # define BOOST_PP_FOR_CHECK_BOOST_PP_FOR_2(s, p, o, m) 0 # define BOOST_PP_FOR_CHECK_BOOST_PP_FOR_3(s, p, o, m) 0 # define BOOST_PP_FOR_CHECK_BOOST_PP_FOR_4(s, p, o, m) 0 # define BOOST_PP_FOR_CHECK_BOOST_PP_FOR_5(s, p, o, m) 0 Now, I'm trying to understand how it works. I don't understand why FOR isn't a shortcut for FOR_1. The only reason I see is the FOR_CHECK test but I can't seems to understand how it works. Anyone ? Eric Robert

1 0

regex compile problem with vc6 and stlport
by Sven Olsen 23 Sep '03

23 Sep '03

I am using MSVC6 (sp5) with STLport v4.5.3 and attempting to compile boost::regex v3.31, as far as I know these are the latest versions/updates. I dutifully followed the installation instructions, but `nmake -fvc6-stlport.mak` died with the error: ../src/cpp_regex_traits.cpp(662) : error C2660: 'isspace' function does not take 2 parameters By building the files in the IDE, I was able to figure out why the isspace error happens: there is a global scope isspace() defined in ctype.h. The isspace problem can be fixed by defining BOOST_REGEX_STD to be std:: (in other words, getting rid of the old STLport isspace workaround). But with that done, I now get a number of linking errors when I try to build the library using nmake (though I have been able to compile .dlls via the IDE). By manually adding stlport_vc6.lib to the list of linked libraries, I can get rid of all reported linking errors, but the dll's are still failing to compile. Has anyone else using STLport v4.5.3 and regex 3.31 (boost dist 1.30.2) gotten the library to compile under MSVC6? At this point I may try compiling the dlls by hand through the IDE, but it seems like there ought to be a way to get nmake working... Thanks, Sven PS- I should probably admit that this is my first time trying to compile regex using STLport, so it's quite possible that there is some silly little thing that I am doing wrong... I have tried setting the include and lib paths both manually and using the STLPORT_PATH environment variable (C:\STLport-4.5.3 in my case), and I get the same results either way.

3 4

Icompatibility between MS cl preprocessor and boost macro constructs
by m.doppler＠icoserve.com 22 Sep '03

22 Sep '03

Hi, the header files boost/iterator_adaptors.hpp and boost/regex/v3/instances.hpp contain macro constructs that are icompatible with the Microsoft compiler cl when using them in a source file, preprocessing the source to a another source file and afterwards compiling the preprocessed source file. For iterator_adaptors.hpp, cl version 13.00 is affected, for instances.hpp cl 13.00 and 13.10. The problem can be reproduced by compiling the following simple source file (test.cpp) in the base boost directory (boost-1.30.2): #include "boost/iterator_adaptors.hpp" #include "boost/regex.hpp" int main(void) { return 0; } The commandline to preprocess the file is: cl /TP /GX /EHsc /Zc:wchar_t /Zc:forScope /c /I. /P test.cpp The commandline to compile the previously preprocessed file is: cl /TP /GX /EHsc /Zc:wchar_t /Zc:forScope /c /I. test.i Note that when directly compiling the same test program using the following commandline the problem disappears: cl /TP /GX /EHsc /Zc:wchar_t /Zc:forScope /c /I. test.cpp One might expect that the last command line should produce the same result as the first two, but unfortunately this is not the case. I have attached a patch file that solves the icompatibility with the preprocessor by incorporating the following changes: - In instances.hpp the patch adds single spaces between the BOOST_DEFAULT_ALLOCATOR and the end of some template declarations. - In iterator_adaptors.hpp the conditional BOOST_WORKAROUND macros are refactored from inside the template declarations of indirect_iterator_generator and indirect_iterator_pair_generator to the front of them by duplicating the template struct definitions minus the BOOST_WORKAROUND code in the else branch of the conditional macro. In case you wonder why we need to preprocess the source file into a seperate file before compiling it: This is required to use distcc (http://distcc.samba.org) with Microsofts cl. Is there a chance this patch gets accepted for the next boost version? Michael --- michael doppler ----------------------------------- developer icoserve it gmbh innrain 98, 6020 innsbruck tel: +43 - 512 - 567622 - 250 fax: +43 - 512 - 567622 - 111 web: www.icoserve.com email: m.doppler(a)icoserve.com ---------------------------------------------------------------

2 1

boost::TokenizerFunction
by Zenaan Harkness 21 Sep '03

21 Sep '03

TokenizerFunction "Expression Semantics" table (documentation - eg. on debian: /usr/share/doc/libboost-doc/HTML/libs/tokenizer/index.htm), states that "tok is constructed", as part of "Precondition". However I note two things: 1: on looking at the source code for the provided example functions, each constructs a Token as it's first (or second) line of code in the call to operator(). 2: the "Semantics" says "The return value [bool] indicates whether a new token was found in the sequence". If there is no token available (eg. we are already at end of stream(/string) and will return false) why waste effort constructing storage for a token? Why does the doco say that the token must be constructed as a precondition? Is the code wrong, or the doco - ie. should my custom function construct a new (empty) token, or follow doco and have user construct one? It would seem potentially more efficient for the user to construct one, as they may be reused. I am trying to use (my own custom) function directly, in a for loop. Why would I use tokenizer class to wrap it? There is no example on using a function directly, thus these string of questions which I would like some answers on. The documentation for TokenizerFunction doesn't seem to have a proper doxygen-like api description - at least not on my local debian installation. So I have to revert to the source. As I'm a newbie, it is requiring quite a bit of going back and forth to try and figure it all out - eg., should I use a tokenizer (container), token_iterator, or just for-loop on a specific (custom) tokenizer function?? Finally, as I've been trying to figure out how to write my own TokenizerFunction. Delving into the code for the example TFs has eventually led me there, but a simpler example in the documentation would be very useful for other newbies, I'm sure. - I know, I should post the code. Well, I'm not done yet, and I'm implementing a function I need specifically, as opposed to just for learning or doco, but perhaps later in the week I can send something along if no one beats me to it. Once I understand it all a bit better. Simple one-hit functions can be a good way to learn how to code what you need (ie. not templatized). A progression from a one-hit to a templatized version would be ideal for learning. TIA Zen -- Mr Zenaan Harkness Phone +61 (0)412 166 990 Please respect the confidentiality of this email.

1 0