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

Regex++ regression test failed
by bustamam98 31 May '02

31 May '02

I've compiled boost 1.28 and tried the regex++ regression testing on test1252.txt. It looks like it's failing on some of the input lines. I'm running Linux RH72. Have anyone have any success with this file? Thanks Bustamam Error in line 10 of file test1252.txt Expression: [[:lower:]]+ Search text: Þßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ÷ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 11 of file test1252.txt Expression: [[:upper:]]+ Search text: ¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞß Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 12 of file test1252.txt Expression: [[:punct:]]+ Search text: ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿À Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 13 of file test1252.txt Expression: [[:print:]]+ Search text: ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêë= ìíîïðñòóôõö÷øùúûüýþ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 14 of file test1252.txt Expression: [[:graph:]]+ Search text: ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêë= ìíîïðñòóôõö÷øùúûüýþ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 15 of file test1252.txt Expression: [a-z]+ Search text: ßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 16 of file test1252.txt Expression: [a-z]+ Search text: ¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 17 of file test1252.txt Expression: [[:word:]]+ Search text: ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API Error in line 19 of file test1252.txt Expression: [[=a=]]+ Search text: aAàáâãäåÀÁÂÃÄÅ Flags: REG_EXTENDED | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended regex++ API result mismatch in sub-expression 0, found (0,1) expected (0,14) regex++ API result mismatch in regex_match(iterator, iterator, match_results&, const reg_expression&, int) regex++ API result mismatch in regex_match(const std::string&, match_results&, const reg_expression&, int) regex++ API result mismatch in regex_match(const char_t*, match_results&, const reg_expression&, int) regex++ API result mismatch in sub-expression 0, found (0,1) expected (0,14) regex++ API result mismatch in regex_match(iterator, iterator, match_results&, const reg_expression&, int) regex++ API result mismatch in regex_match(const std::string&, match_results&, const reg_expression&, int) regex++ API result mismatch in regex_match(const char_t*, match_results&, const reg_expression&, int) regex++ API result mismatch in sub-expression 0, found (0,1) expected (0,14) POSIX API result mismatch in sub-expression 0, found (0,1) expected (0,14) Error in line 25 of file test1252.txt Expression: ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝ Search text: ßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ Flags: REG_EXTENDED | REG_ICASE | REG_PERL | REG_AWK | REG_EGREP | basic | char_classes | intervals | bk_refs | normal | basic | extended Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using regex++ API Match expected but not found using POSIX API 35 lines, 10 tests completed in file test1252.txt **** returning with error code 10 ********** errors detected; see stdout for details ***********

2 3

RE: [Boost-Users] shared_ptr and lazy copy
by Michael Davis 30 May '02

30 May '02

There is an implementation of the method you described (const and non-const versions of operator-> and operator*) at the following website: http://ootips.org/yonat/4dev/ Perhaps this guy might be talked into submitting it. -----Original Message----- From: Mark Storer To: 'Boost-Users(a)yahoogroups.com' Sent: 5/30/2002 1:35 PM Subject: [Boost-Users] shared_ptr and lazy copy Is there an easier way to use shared_ptr as a lazy copy method? It seems to me that the only way to do it would be by testing unique() (or use_count()) every time the pointed-to object was to be changed: boost::shared_ptr<foo> bar(new foo); boost::shared_ptr<foo> baz = bar; if(!baz->unique()) ... // make a deep copy baz->ChangeAFoo(); I can't think of a good way to alter shared_ptr either. The only thing I came up with would be const and non-const versions of operator-> and operator* where the non-const versions checked unique() and made a deep copy. This would seem to fall into that last question in the FAQ anyway... "Why doesn't shared_ptr provide (your pet feature here)". I'd think this could easily lead to unnecessary deep copies unless the programmer took explicit steps (lots of const_cast's) to avoid it. Am I missing anything? --Mark Storer Software Engineer Cardiff Software #include <disclaimer> typedef std::disclaimer<Cardiff> Discard; 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

shared_ptr and lazy copy
by Mark Storer 30 May '02

30 May '02

Is there an easier way to use shared_ptr as a lazy copy method? It seems to me that the only way to do it would be by testing unique() (or use_count()) every time the pointed-to object was to be changed: boost::shared_ptr<foo> bar(new foo); boost::shared_ptr<foo> baz = bar; if(!baz->unique()) ... // make a deep copy baz->ChangeAFoo(); I can't think of a good way to alter shared_ptr either. The only thing I came up with would be const and non-const versions of operator-> and operator* where the non-const versions checked unique() and made a deep copy. This would seem to fall into that last question in the FAQ anyway... "Why doesn't shared_ptr provide (your pet feature here)". I'd think this could easily lead to unnecessary deep copies unless the programmer took explicit steps (lots of const_cast's) to avoid it. Am I missing anything? --Mark Storer Software Engineer Cardiff Software #include <disclaimer> typedef std::disclaimer<Cardiff> Discard;

1 0

Problem with Boost.Thread and HP aCC
by raulh39 29 May '02

29 May '02

We are trying to compile Boost.Thread with HP aCC (with -AA option). In boost/function/function_base.hpp the compiler give us this error: Error 20: "function_base.hpp", line 37 # '<type name>' expected before '>'. template<bool> struct truth {}; We are using Boost 1.28.0. The line 37 in function_base.hpp has: template<bool> struct truth {}; We have found two ways to make it work: 1.- Comment out the line !! 2.- Replace with: template<bool a> struct truth {}; We think that the compiler is wrong but, is ok to comment this line? In earlier versions of this file this line doesn't exists, and it is never used, so it is necesary? Regards, Raúl.

2 1

RE: [Boost-Users] Problem with Boost.Thread and HP aCC
by Tom Matelich 29 May '02

29 May '02

When I first started trying to support aCC with Boost that was a common issue. Most of them were ferreted out. I don't think anybody is actively looking at that compiler, perhaps Jens Maurer still is. Anyway, the proper solution is to name the template parameter, your option 2. I've cc'ed Bill Kempf in case he doesn't follow this list. Tom Matelich -----Original Message----- From: raulh39 [mailto:rhuertas@tcpsi.es] Sent: Wednesday, May 29, 2002 10:15 AM To: Boost-Users(a)yahoogroups.com Subject: [Boost-Users] Problem with Boost.Thread and HP aCC We are trying to compile Boost.Thread with HP aCC (with -AA option). In boost/function/function_base.hpp the compiler give us this error: Error 20: "function_base.hpp", line 37 # '<type name>' expected before '>'. template<bool> struct truth {}; We are using Boost 1.28.0. The line 37 in function_base.hpp has: template<bool> struct truth {}; We have found two ways to make it work: 1.- Comment out the line !! 2.- Replace with: template<bool a> struct truth {}; We think that the compiler is wrong but, is ok to comment this line? In earlier versions of this file this line doesn't exists, and it is never used, so it is necesary? Regards, Raúl. 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

VC7, threads, and threads starting other threads
by Bill Eidson 28 May '02

28 May '02

Hi all, I am using boost 1.28 and the threads library on windows with VC7.Net. I am creating threads in a threadgroup use function objects. Inside of these threads, I am creating other threads again using function objects. The problem is at run time the debug environment is informing me of a call type collision indicating the return address/stack is set up incorrectly. The debug message: "The value of ESP was not properly saved across afunction call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention." this is in the declaration template<typename Functor> void assign_to(Functor f) { this->assign_to(f,tag()); } The error is at the end of the function First, is it legal in boost::thread to start one thread in another Second, If it is, what is going on with the function_template.hpp code here Thanks bille

1 0

problem with c_regex_traits.cpp
by René Gutschmidt 28 May '02

28 May '02

Hi, 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.) Regards, Rene

2 2

any_ptr
by cl_corba_at 27 May '02

27 May '02

Hi all! any_ptr was a typo in an older documentation, but this leads me to this question: any stores the type values in the template class holder, which is derived from placeholder to provide an uniform interface. This approach works fine for new classes where the data representation is done inside the any class, but for legacy code I would also like to have an any_ptr, which uses a holder that POINTS to a variable rather than containing it. With this I could extend existing classes with algorithms depending on any. Has any_ptr considered in the past and if yes, what have been the reasons to decide against it? Thanks in advance, CL

1 0

BGL, 6 degrees of Kevin Bacon and MSVC 6 compile error
by a_schweitzer 25 May '02

25 May '02

Hello, I am trying to build the "6 degrees of kevin bacon" example of the BGL in MSVC 6. When I do I get an "internal compile error". Does anyone know a fix/work-around? The compilation gets to this line (about #73): typedef adjacency_list < vecS, vecS, undirectedS, property<vertex_name_t,std::string >, property < edge_name_t,std::string > > Graph; Graph g; If Graph g is declared I get the following ugly error: d:\program files\microsoft visual studio\vc98\include\xmemory(59) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Note that if I change the std::string in vertex_name property to an int the compilation proceeds. Thanks for any help Andy Schweitzer

3 3

RE: [Boost-Users] boost::lexical_cast string to string problem - New proposition available
by Terje Slettebø 25 May '02

25 May '02

>--- In Boost-Users@y..., Tom Matelich <tmatelich@z...> wrote: > I and many others have requested fixes for this for a very long time. > Basically, it involves creating class templates to do the actual conversion. > It's not the most complicated system, just nobody has done it yet. If you > search the boost list archives, you'll see a lot of mail about this. There > is no quick solution to your problem though. I've searched the archive, now, and see that there's been quite a few propositions for changes, but apparently none of them have ended up in the lexical_cast implementation. There's also a couple of propositions, here (http://groups.yahoo.com/group/boost/files/lexical_cast_propositions/) Some of the proposed changes are: - wlexical_cast - A version that can use wide characters - basic_lexical_cast - A version that takes the interpreter (stringstream) as a parameter, to support things like changing locale - Being able to set number base (dec, oct or hex). This would be implicitly possible using basic_lexical_cast - Being able to set precision for numerical conversions. This may also be done with basic_lexical_cast - Checking for change of sign, when using unsigned numbers. This is addressed using an integer adapter, in the above lexical_cast_propositions One problem with doing these changes, after having talked with Kevlin Henney a while ago (without knowing it had been already proposed, I proposed an extra parameter, for setting the number base). is that he prefers to not have extra parameters in the interface, as it then will no longer look like a cast, and it may be less generic, depending on the way it's done. For example, a base-setting argument wouldn't make much sense if you converted from floating point to string. In any case, I have actually just now made a version of lexical_cast, that fixes the problem pointed out by OP, here, and I've made it available in the Boost files section (http://groups.yahoo.com/group/boost/files/lexical_cast_proposition/) I've also put a unit test for it, there. Feedback is welcome. It doesn't change the interface in any way, so it should be ok. The new version supports conversion between string and char, including char containing whitespace, and when the string is empty, or containing only whitespace. If the source or destination (or both) is basic_string or char/wchar_t, it will set the interpreter to use the char type used, so it implicitely supports wide characters. Wide character support requires partial specialisation if one of the operands is not either basic_string or char/wchar_t. In the case where the source is basic_string, it also uses pass by const reference, for efficiency. It's tested on Intel C++ 6.0, MSVC 6.0 and BCC 5.6. Regards, Terje

2 4

boost::shared_ptr and atomic_count_linux.hpp
by Jerry Napoli 24 May '02

24 May '02

Hi, I'm using boost version 1.27.0 on an x86 linux platform and have just upgraded my kernel to 2.4.18. After the upgrade, boost::shared_ptr fails to compile because functions such as "atomic_inc_and_test", "atomic_dec_and_test", etc.. which were previously defined in "atomic.h" are no longer defined there. I can get around the problem by using an older "atomic.h" or by using pthreads, but I was wondering why those functions were removed from the header. Any ideas? Thanks, Jerry jnapoli(a)iteamsolutions.com [Non-text portions of this message have been removed]

3 2

Seeking example of using quaternion class
by yg-boost-users＠m.gmane.org 23 May '02

23 May '02

Hi, I am trying to use the quaternion class for 3d rotation and wonder if anyone has a sample of how to do this. If we have quaterion q1 and want to rotate by q2 the expression, I believe, is result = q2 * q1 * inv( q2 ). Is the correct syntax using ::boost::quaternion operators result = q2 *= q1 /= q2 ?? Do the quats need to be "unit quaternions" before these operations? What is the best way to create an unit quat? thanks john ware

1 0

Re: [boost] boost::lexical_cast string to string problem - New proposition available
by Terje Slettebø 23 May '02

23 May '02

(This posting is also sent to the Boost list) Following a suggestion at the Boost User's list, I've updated the lexical_cast version in the Boost files section (http://groups.yahoo.com/group/boost/files/lexical_cast_proposition/) to use implicit conversion, where possible. This means it uses the fastest and most accurate conversion available, and only resorts to using stringstream when it has to. It uses boost::is_convertible for this. Even if that may not work on all compilers, if it doesn't work, it will just resort to using stringstream. However, this does mean that the semantics is changed slightly. In the cases where an implicit conversion exists, it may give a different result than if not, in the case of char/wchar_t. Without implict conversion, you get 1 -> '1'. With implicit conversion, you get 1 -> 1 (ASCII 1). As far as I can tell, this only affects conversions between char/wchar_t and other types, though. If this is a problem, please let me know, and I can change it to make an exception for char/wchar_t. Another thing is that there's now an option to configure the interpreter stream, as well. This is done _without_ changing the interface of lexical_cast. Instead, it's done in a trait-like fashion, by making the interpreter object available through an associated component, which is used by lexical_cast. The reason this is optional, is that when enabled, it relies on having a static stringstream object. This has two effects (unless implicit conversion is used): - It may well make lexical_cast faster, as it avoids the creation and destruction of a stringstream object, each time it's called. - Unless stringstream is reentrant, which is probably not the case, it means that when the option is enabled, lexical_cast is not thread safe. Therefore, this option is off by default, which gives the usual behaviour - stringstream objects are created at the function call. If the option is used, it lets you configure the stream used, in any way. This way, one can implement all the features of the "wish list" in the previous posting in this thread, such as. - wlexical_cast - A version that can use wide characters - This is already handled by the previous version. - basic_lexical_cast - A version that takes the interpreter (stringstream) as a parameter, to support things like changing locale - Being able to set number base (dec, oct or hex). This would be implicitly possible using basic_lexical_cast - Being able to set precision for numerical conversions. This may also be done with basic_lexical_cast - These are all handled now. - Checking for change of sign, when using unsigned numbers. This is addressed using an integer adapter, in the other lexical_cast_propositions The lack of formatting is what is largely the reason I haven't used lexical_cast much. With control over the formatting, it may be more widely applicable. Since the stream may be different, for different conversions (char, wchar_t or other character type), one need to supply the source and destination types, when configuring the stream. Here's an example of its use. --- Start --- #define BOOST_LEXICAL_CAST_STREAM // Enables stream configuration #include <iostream> #include <iomanip> #include <string> #include "lexical_cast.hpp" int main() { boost::lexical_cast_stream<std::string,double>::stream() << std::setprecision(0); std::cout << boost::lexical_cast<std::string>(1.0/3.0) << '\n'; boost::lexical_cast_stream<std::string,double>::stream() << std::setprecision(10); std::cout << boost::lexical_cast<std::string>(1.0/3.0) << '\n'; boost::lexical_cast_stream<std::string,int>::stream() << std::setbase(16); std::cout << boost::lexical_cast<std::string>(0x1234) << '\n'; } --- End --- This prints. 0.333333 0.3333333333 1234 Any suggestions for changes or additions, including interface changes, is welcome. I realise that the way to change the stream formatting is rather long-winded, but I haven't found a shorter way to do it (the name has to be different from lexical_cast, too). Suggestions for alternative ways are welcome. I've not found a way to make the stream configurable, and yet avoid a static stringstream. If the stringstream is created when lexical_cast is called, it means any configuration information is lost. Even if it copied the state from another stream, that other stream would have to exist, such as being static, so that would only move it. Despite the extra code, to handle implicit conversions, where available, by examining the resulting assembly output (from Intel C++), it's in fact able to optimise _all_ of it away, producing indentical code as if built in conversions were used directly. Here's an example. int n; double d=1.23; int main() { n=boost::lexical_cast<int>(d); } 00401084 fld qword ptr [d (00427db0)] 0040108A fstp qword ptr [esp+8] 0040108E mov esi,dword ptr [esp+8] 00401092 mov edx,dword ptr [esp+0Ch] 00401096 mov ecx,edx 00401098 shr ecx,14h 0040109B and ecx,7FFh 004010A1 cmp ecx,3FEh 004010A7 jle main+52h (004010c6) 004010A9 mov eax,edx 004010AB neg ecx 004010AD add ecx,41Eh 004010B3 shld eax,esi,0Bh 004010B7 or eax,80000000h 004010BC shr eax,cl 004010BE test edx,edx 004010C0 jge main+54h (004010c8) 004010C2 neg eax 004010C4 jmp main+54h (004010c8) 004010C6 xor eax,eax 004010C8 mov [n (0042bef8)],eax int n; double d=1.23; int main() { n=d; } 0041AFF0 fld qword ptr [d (00427db0)] 0041AFF6 fstp qword ptr [esp+8] 0041AFFA mov esi,dword ptr [esp+8] 0041AFFE mov edx,dword ptr [esp+0Ch] 0041B002 mov ecx,edx 0041B004 shr ecx,14h 0041B007 and ecx,7FFh 0041B00D cmp ecx,3FEh 0041B013 jle main+1A022h (0041b032) 0041B015 mov eax,edx 0041B017 neg ecx 0041B019 add ecx,41Eh 0041B01F shld eax,esi,0Bh 0041B023 or eax,80000000h 0041B028 shr eax,cl 0041B02A test edx,edx 0041B02C jge main+1A024h (0041b034) 0041B02E neg eax 0041B030 jmp main+1A024h (0041b034) 0041B032 xor eax,eax 0041B034 mov [n (0042b84c)],eax The code is identical. :) Thus, you get a generic conversion, with the speed and accuracy of built in conversions, where that is possible. It's a good thing I have a unit test, so I could do regression testing, to make sure I haven't broken anything. Regards, Terje

1 0

Problems with read_graphviz()
by Paolo Fosser 23 May '02

23 May '02

Hi to everybody, first of all I beg pardon if my English isn't much good: I'm Italian! I'm working with gcc 3.0.1 on a Linux Mandrake sys with kernel 2.4.8. The problem I'm having is that the second call of read_graphviz() in the same program causes a Segmentation fault. What can I do? Thank you in advance, Paolo PS Advices about the language are welcome too ;)

1 0

Boost thread examples
by imi123_1999 22 May '02

22 May '02

Is there any other site from where we can get the example programs illustrating the usage of boost libraries especially threads. I found the example programs present on boost web site not sufficient to fully understand the concepts. So please tell me from where i can get the further information regarding the usage of boost thread library.

3 2

Thread destruction in boost
by giltayar 21 May '02

21 May '02

>From boost:thread documentation, it is clear that deleting a thread does not kill the thread. I very much approve of this. killing a thread is a very "strong" operation. The problem is that there is now no connection between the system thread and the object itself, which (debatably) kills the idiom in C++ connection the object and the resource (I never remember its name). Was the idea of doing a "join()" in the dtor brought up? I.e., the dtor waiting for the thread to finish? I used it in my library, and it was _very_ effective, as I could _know_ that the thread and the object have parallel lifetimes, and it also helped me because it prevented many "thread-leakage" problems. Gil P.S. The question was - "Was the idea of doing a join() in the dtor ever brought up?"

3 5

RE: [Boost-Users] boost::lexical_cast string to string problem
by Tom Matelich 21 May '02

21 May '02

I and many others have requested fixes for this for a very long time. Basically, it involves creating class templates to do the actual conversion. It's not the most complicated system, just nobody has done it yet. If you search the boost list archives, you'll see a lot of mail about this. There is no quick solution to your problem though. -----Original Message----- From: Jason Fischl [mailto:yg-boost-users@m.gmane.org] Sent: Monday, May 20, 2002 5:21 PM To: boost-users(a)yahoogroups.com Subject: [Boost-Users] boost::lexical_cast string to string problem I'm seeing a problem with lexical_cast. The following code when trying to convert from string to string fails when passed an empty string. The library code that is doing this lexical_cast does not and can not know that the input and output types are the same. I believe that this code should not throw. #include <iostream> #include <boost/lexical_cast.hpp> main() { std::string input(""); try { boost::lexical_cast<std::string>(input); } catch (boost::bad_lexical_cast& e) { std::cout << "Failed" << std::endl; } } 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

random::mersenne_twister ctor and seed() methods
by klapshin 21 May '02

21 May '02

Hello All! I just started using boost/random project, and kind of confused with behavior of random::mersenne_twister constructor and seed method. The thing is that both of them have two flavors -- first accepting DataType, while second is template method accepting Generator. The problem is when I am trying innocent boost::mt19937 rng(999); //and/or rng.seed(999); wrong ctor/seed being invoked and I am getting far from crystal clear error message (term does not evaluate to a function). The problem is quite obvious: 999 is of type int, while DataType by default is unsigned long on my platform, so template version of ctor/seed picks this call, and it is failing since 999 is not a generator. So I have to write something like: boost::mt19937 rng(boost::mt19937::result_type(999)); which is kind of cumbersome. Why generator version of seed is not named differently? Say seed_gen? Don't know what to do with constructor though. PS: I am using boost_1_28_0, and MSVC 6.0. Best regards, Kirill Lapshin.

1 0

boost::lexical_cast string to string problem
by Jason Fischl 21 May '02

21 May '02

I'm seeing a problem with lexical_cast. The following code when trying to convert from string to string fails when passed an empty string. The library code that is doing this lexical_cast does not and can not know that the input and output types are the same. I believe that this code should not throw. #include <iostream> #include <boost/lexical_cast.hpp> main() { std::string input(""); try { boost::lexical_cast<std::string>(input); } catch (boost::bad_lexical_cast& e) { std::cout << "Failed" << std::endl; } }

3 3

BLL trouble
by Persson Jonas 21 May '02

21 May '02

Hello, I've just started playing around with BLL and i have some troubles using it with containers of shared_ptr. I have isolated the problem to: void lambdaTest() { using namespace boost::lambda; boost::shared_ptr<int> x(new int(5)); (*_1)(x); } This does not compile with gcc 3.1 on cygwin. If I use plain pointers it works as expected but not for shared_ptr. What am I doing wrong? / Jonas ---------------------------------------------------------------------------- ---- ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h: In instantiation of `std::iterator_traits<boost::s hared_ptr<int> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 224: instantiated from `boost::lambda::det ail::contentsof_type<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: instantiated from `boost::lambda::detail::IF_type_<b oost::lambda::detail::contentsof_type<boost::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:123: no type named `iterator_category' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:124: no type named `value_type' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:125: no type named `difference_type' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:126: no type named `pointer' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:127: no type named `reference' in `class boost::shared_ptr<int>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: In instantiation of `boost::lambda::detail: :contentsof_type<boost::shared_ptr<int> >': ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: instantiated from `boost::lambda::detail::IF_type_<b oost::lambda::detail::contentsof_type<boost::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 224: no type named `reference' in `struct std::iterator_traits<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp: In instantiation of `boost::lambda::detail::IF_type_<boos t::lambda::detail::contentsof_type<boost::shared_ptr<int> > >': ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: no type named `type' in `struct boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp: In instantiation of `boost::lambda::detail::IF_type<true, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lambda: :detail::unspecified> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: no type named `type' in `struct boost::lambda::detail::IF_type_<boost::lambda::detail::contentsof_type<boost ::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: In instantiation of `boost::lambda::return_ type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>': ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: no type named `type' in `struct boost::lambda::detail::IF_type<true, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lambda::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp: In instantiation of `boost::lambda::return_type_1_pr ot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>': ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: no type named `type' in `struct boost::lambda::return_type_1<boost::lambda::other_action<boost::lambda::cont entsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp: In instantiation of `boost::lambda::detail::u nary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functo r<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost:: tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_typ e, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples::nul l_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::t uples::null_type, boost::tuples::null_type, boost::tuples::null_type> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : no type named `type' in `struct boost::lambda::return_type_1_prot<boost::lambda::other_action<boost::lambda: :contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp: In instantiation of `boost::lambda::lambda_fu nctor_base<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tu ples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >': Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: no type named `type' in `class boost::lambda::detail::unary_rt<boost::lambda::other_action<boost::lambda::c ontentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp: In function `void lambdaTest()': Main.cpp:150: no match for call to `(const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lamb da::other_action<boost::lambda::contentso f_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >) (boost::shared_ptr<int>&)' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_functors.hpp:142: candidates are: T::sig<boost::tuples::null_type>::type boost::lambda::lambda_functor<Base>::operator()() const [with T = boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda ::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]

1 0

RE: [Boost-Users] Graphs: vertex_index vs. edge_index
by Siegel, Matthew 20 May '02

20 May '02

Hi Jeremy, Thanks for the quick response. As you may or may not recall from last week, I am having the issue with MSVC++, where I can not put more than one property per edge or vertex when defining the graph, that limits the size of the template expansion. Because of this, I have to use external property maps that I create myself. Therefore I need an edge index map internal to the graph. Currently my workaround is to keep an unsigned integer in my class, that gets incremented until there's a free "slot" for the edge to go into. This is to allow the increment of the unsigned int to roll at maximum value. Here's the way I think it should work. I understand the space issues that most people would be concerned about, however if a property_map of edge_index_t is explicitly given in the list of edge properties when the graph is defined, then the map should be created automatically for me, and if an index is not provided on the add_edge() function, the index is incremented in the same fashion. If I'm explicitly adding the edge_index map to my graph, then the space is of no concern to me. Just a thought . . .thanks again, Matt -----Original Message----- From: Jeremy Siek [mailto:jsiek@cs.indiana.edu] Sent: Monday, May 20, 2002 12:01 PM To: 'Boost-Users(a)yahoogroups.com' Subject: Re: [Boost-Users] Graphs: vertex_index vs. edge_index Hi Matt, On Mon, 20 May 2002, Siegel, Matthew wrote: > Please correct me if I'm wrong. It seems as if a vertex_index gets > assigned to a vertex as it's added to the graph automatically. > However, this doesn't seem to be the case for the edge_index. > > Is this correct?? That is mostly correct. The vertex_index gets assigned automatically for adjacency_list with VertexList=vecS but not with VertexList=listS. You are right about edge_index. > I forsee the following problem. With the graph implemented using a > std::vector for both the vertex list and the edge list, if a vertex is > removed from the graph the index is corrected for the > vertex_descriptor to the new, appropriate index. However, if an edge Right. All vertices are re-indexed, so that after the removal the remaining indices go from 0 to num_vertices-1 > is removed, the index for the edge_descriptor will not be corrected > with the removal of an element in the vector. Also, this causes > headaches when using an external property map. The edge index is > linked directly to a location in my map. > > Any solutions for these problems?? The reason edge_index is not provided automatically is because it takes up space (whereas the vertex_index is does not), and some users are concerned about space issues. Anyways, one possible solution is to somehow make it possible for you to specify some code to be executed when an edge is added or removed from the graph, and this code would adjust the edge indices, and perhaps the external storage too. But before I get ahead of myself, could you describe how you currently work around this problem, and perhaps how you'd like to see it work? Cheers, Jeremy ---------------------------------------------------------------------- Jeremy Siek http://www.osl.iu.edu/~jsiek/ Ph.D. Student, Indiana Univ. B'ton email: jsiek(a)osl.iu.edu C++ Booster (http://www.boost.org) office phone: (812) 855-3608 ---------------------------------------------------------------------- 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

Graphs: vertex_index vs. edge_index
by Siegel, Matthew 20 May '02

20 May '02

Hi, Please correct me if I'm wrong. It seems as if a vertex_index gets assigned to a vertex as it's added to the graph automatically. However, this doesn't seem to be the case for the edge_index. Is this correct?? I forsee the following problem. With the graph implemented using a std::vector for both the vertex list and the edge list, if a vertex is removed from the graph the index is corrected for the vertex_descriptor to the new, appropriate index. However, if an edge is removed, the index for the edge_descriptor will not be corrected with the removal of an element in the vector. Also, this causes headaches when using an external property map. The edge index is linked directly to a location in my map. Any solutions for these problems?? Thanks, Matt

2 1

newbie question
by the_3_project 20 May '02

20 May '02

How do I compile a program that uses the libregex program? It seems that whenever I do this: $ gcc -o te1 te1.cc -lboost_regex I get: ---- /tmp/cc9r42Gv.o: In function `boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::fail(unsigned int)': /tmp/cc9r42Gv.o(.boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::gnu.linkonce.t.fail(unsigned int)+0x4e): undefined reference to `boost::bad_expression::bad_expression(basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> > const &)' /tmp/cc9r42Gv.o: In function `boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::compile_set_aux(boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, boost::re_detail::jstack<unsigned int, allocator<char> > &, boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, bool, boost::re_detail::_narrow_type const &)': . . . ---- Here is the source to te1.cc ---- #include <iostream> #include <string> #include <boost/regex.hpp> using namespace boost; int main(int argc, char *argv[]) { cmatch what; string str = "XXyX"; regex expression("(\\S\\S){[Ayw]}(\\S)/"); if(regex_match(str,what,expression)) { cout << "what" << endl; } else { cout << "Shit\n"; } return 0; } -------- What am I doing wrong?

3 2

adjacency_list.cpp
by Louis Lavery 20 May '02

20 May '02

Hello, I've bought the book (BGL) and am trying to compile boost_1_27_0/boost/libs/example/adjacency_list.cpp but... ...MSVC6 spits out the dreaded "fatal error C1001: INTERNAL COMPILER ERROR". Intel 5's first (of many) error is e:/boost_1_27_0/boost/detail/iterator.hpp(204) : error: class "std::list<_Ty, _A>::iterator [with _Ty=boost::list_edge<boost::detail::adj_list_gen<boost::adjacency_list<boost ::vecS, boost::listS, boost::undirectedS, boost::property<boost::vertex_ind ex_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>, boost::listS, boost::vecS, boost::undirectedS, boost::property<boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::n o_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>::config::vertex_descriptor={boost::adjacency_list_traits<boost ::vecS, boost::listS, boost::undirectedS>::vertex_descriptor={boost::ct_if_t<boost::adjacency_list _traits<boost::vecS, boost::listS, boost::undirectedS>::is_rand_a ccess={boost::detail::is_random_access<boost::listS>::type={boost::false_typ e}}, size_t={unsigned int}, boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}>::type={boost::adjacency_list_traits<boost::vecS , boost::listS, boost::undirectedS>::vertex_ptr={void *}}}}, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>>, _A=std::allocator<boost::list_edge<bo ost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::listS, boost::undirectedS, boost::property<boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>, boost::listS, boost::vecS, boost::undirectedS, boost::property <boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>::config::vertex_descriptor={boost::adjacency_list_traits<boost ::vecS, boost::listS, boost::undirectedS>::vertex_descriptor={boost::ct_if_t<boost::adjacency_list _traits<boost::vecS, boost::listS, boost::undirectedS>::is_rand_access={boost::detail::is_random_access<boost:: listS>::type={boost::false_type}}, size_t={unsigned int}, boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}>::type={boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}}}}, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits <char>, std::allocator<char>>}, boost::no_property>>>]" has no member "difference_type" typedef typename Iterator::difference_type difference_type; My last hope gcc 2.95.2 comes up with... In file included from e:\boost_1_27_0\boost\detail\numeric_traits.hpp:69, from e:\boost_1_27_0\boost\counting_iterator.hpp:57, from e:\boost_1_27_0\boost\pending\integer_range.hpp:15, from e:\boost_1_27_0\boost\graph\detail\adjacency_list.hpp:34, from e:\boost_1_27_0\boost\graph\adjacency_list.hpp:293, from adjacency_list.cpp:31: e:\boost_1_27_0\boost\cstdint.hpp:163: parse error e:\boost_1_27_0\boost\cstdint.hpp:171: #error defaults not correct; you must hand modify boost/cstdint.hpp I'd like to get it working with MSVC6 or Intel5. Any help much appreciated. Louis.

3 4

BLL for other compilers than GCC and Kai C++
by tslettebo1 19 May '02

19 May '02

Hi all. Have anybody got the Boost Lambda Library to work on other compilers than GCC and Kai C++ (which are mentioned in the documentation)? I have Intel C++ 6.0, which is quite standards compliant, but I get a zillion error messages, just by trying to compile boost/libs/lambda/test/bind_tests_simple.hpp. Trying it with MSVC 6.0 gives an ICE, but that's hardly unexpected. :) Also, are there any plans, on ongoing work, to make it more portable? (I post here, rather than the Boost list, as it's about use of a library) Regards, Terje

1 0