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

dijkstra_shortest_paths and vertex_index
by Steve Buchko 16 Oct '04

16 Oct '04

I understand that when using listS to define vertices for a graph, I must also assign values to vertex_index before attempting to make use of dijkstra_shortest_paths. My question is, do the values assigned to vertex_index need to be sequential (i.e. 0 to n where n is the number of vertices in the graph), or can I assign any "random" integer to each vertex_index, as long as the values assigned are unique for each node? Does dijkstra_shortest_paths simply use the vertex_index as a unique identifier for the vertex, or is it using those indices to build an internal data structure such as an array or vector ... in which case using relatively large (or non-sequential) integers for vertex_index might be prohibitive from a memory or performance viewpoint? Thanks, steve

3 2

RE: [Boost-users] boost::bind, MSVC7.1 and volatile-qualification
by Schalk_Cronje＠McAfee.com 15 Oct '04

15 Oct '04

> I wonder why gcc is able to compile it. :-) Well considering that the following also yields different results on MSVC7.1 and gcc 3.2/3.3 I would wonder if there is a problem with one of the compilers #include <iostream> #include <boost/bind.hpp> struct X { void f() {std::cout << "None" << std::endl;} void f() const {std::cout << "const" << std::endl;} }; template <typename T> void run( void (T::*f_)(), T& t_) {(t_.*f_)();} template <typename T> void run( void (T::*f_)() const, T const& t_) {(t_.*f_)();} int main() { X x; run(&X::f,x); boost::bind(&X::f,_1)(x); } >Do you really have a volatile member function somewhere? I thought that they >were "officially" worthless. Well, that is a different matter. If one might want to follow Andrei's suggestion of using volatile to encapsulate synchronisation then they are still worthwhile. (CUJ February 2001).

2 2

RE: [Boost-users] Spirit
by Foster, Gareth 15 Oct '04

15 Oct '04

Thanks Ron, Joel, What i was after was the link Joel actually posted, but thats for the tip anyway Ron. Much appreiated both. Now i just have to get boost working with cygwin :) Regards, Gaz -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Ronald Garcia Sent: 14 October 2004 17:21 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Spirit Are you referring to code that translates C++ into an xml-ish parse tree, or code that makes c++ code look pretty as html? I am aware of an html pretty-printing program for c++ sources written using boost.regex, if that's what you seek. Cheers, Ron On Oct 14, 2004, at 8:24 AM, Foster, Gareth wrote: Hello all, I am trying to find some source code that uses spirit to parse C++ and convert it to HTML, i found some on google, but i misplaced it and i can't find it again. It looked like it could have been an example provided with the library, but i can't see it listed in the documentation. On a side note, anyone know the best way to use boost with cygwin? From source? Is there even another way? Thanks for any help! Gaz _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

for_each on container of any
by Frank Birbacher 15 Oct '04

15 Oct '04

Hello! I like the idea of containers (e.g. std::vector) of boost::any. But I'd like to execute some operation on each item of the sequence. Unfortenuately I would need to know the set of types in the container and check every one of them if I was going to use the std::for_each with a void(*)(boost::any&). That's not good at all. I'd like to pass a function object like: struct MyOperation { template<typename T> void operator() (T&) const; }; How can I do so? Is there any algorithm for doing so provided by boost? Frank

2 1

max_element matrix
by Vicente Palazón González 15 Oct '04

15 Oct '04

Hello, sorry, I'm a beginner with uBLAS, and I think these are simple questions, is there a simple way to obtain the maximum element of an uBLAS matrix? is there an special iterator for ubLAS matrices to use with std::max_element? Vicente Palazón.

1 0

BOOST_STATIC_ASSERT with intel compiler at class scope
by Thomas S. Urban 15 Oct '04

15 Oct '04

The BOOST_STATIC_ASSERT documentation indicates I can use it at template class scope (private recommended) - the assert shouldn't get triggered unless the class is instantiated. This seems to work ok with gcc-3.* but not with the intel compiler (8.1). // begin example program #include "boost/static_assert.hpp" template<class T> struct foo { foo (int) { } private: BOOST_STATIC_ASSERT (false); }; template <> struct foo<int> { foo (int i) { } }; int main () { foo<int> f (7); } // end example program I get the following error: foo.cpp(8): error: incomplete type is not allowed BOOST_STATIC_ASSERT (false); ^ compilation aborted for foo.cpp (code 2) Whether I provide the specialization for int or not, or whether I ever use struct foo in main or not. Is this a know issue? Do I have a build problem? I'm using boost version 1.30.2. Thanks Scott

3 3

Spirit
by Foster, Gareth 14 Oct '04

14 Oct '04

Hello all, I am trying to find some source code that uses spirit to parse C++ and convert it to HTML, i found some on google, but i misplaced it and i can't find it again. It looked like it could have been an example provided with the library, but i can't see it listed in the documentation. On a side note, anyone know the best way to use boost with cygwin? From source? Is there even another way? Thanks for any help! Gaz

3 2

boost::bind, MSVC7.1 and volatile-qualification
by Schalk_Cronje＠McAfee.com 14 Oct '04

14 Oct '04

Is there a known problem with boost::bind, volatile-qualified member functions and MSVC7.1? The following snippet of code happily compiles with various incantations of gcc, but fails with MSVC7.1. The same applies for 'const volatile'. #include <boost/function.hpp> #include <boost/bind.hpp> struct TEST { void gv0() volatile; void gvc0() volatile const; int gv2(int,int) volatile; int gvc2(int,int) volatile const; }; void instantiate() { TEST T; boost::function< void() > gv0 =boost::bind(&TEST::gv0,&T); // boost::function< int(int,int) > gv2 =boost::bind(&TEST::gv2,&T,_1,_2); // boost::function< void() > gcv0=boost::bind(&TEST::gvc0,&T); // boost::function< int(int,int) > gcv2=boost::bind(&TEST::gvc2,&T,_1,_2); } cl -c -TP -GS -GF -GR -vmv -vmg -EHsc -Zc:forScope -Zc:wchar_t -Op -Gm- -D_DEBUG -Od -Zi -Yd -MDd msvc71bind.cpp (Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86) ******\boost\mem_fn.hpp(256) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\bind\bind_template.hpp(156) : see reference to class template instantiation 'boost::_mfi::dm<R,T>' being compiled with [ R=void (void) volatile, T=TEST ] msvc71bind.cpp(21) : see reference to class template instantiation 'boost::_bi::bind_t<R,F,L>' being compiled with [ R=void (__thiscall &)(void) volatile, F=boost::_mfi::dm<void (void) volatile,TEST>, L=boost::_bi::list_av_1<TEST *>::type ] ******\boost\mem_fn.hpp(264) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\mem_fn.hpp(274) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\mem_fn.hpp(288) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\mem_fn.hpp(293) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\mem_fn.hpp(307) : warning C4180: qualifier applied to function type has no meaning; ignored ******\boost\bind.hpp(1572) : warning C4180: qualifier applied to function type has no meaning; ignored msvc71bind.cpp(21) : see reference to function template instantiation 'boost::_bi::bind_t<R,F,L> boost::bind<void(void) volatile,TEST,TEST*>(void (__thiscall TEST::* ),A1)' being compiled with [ R=void (__thiscall &)(void) volatile, F=boost::_mfi::dm<void (void) volatile,TEST>, L=boost::_bi::list_av_1<TEST *>::type, A1=TEST * ] ******\boost\mem_fn.hpp(286) : error C4716: 'boost::_mfi::dm<void __thiscall TEST::(void)volatile ,TEST>::operator()' : must return a value

2 1

Re: Extending the boost::thread class
by arno.schaefer＠sqs.de 14 Oct '04

14 Oct '04

> For what it's worth, William Kempf began an implementation of thread > priorities and an exception-based thread cancellation scheme on the > thread_dev branch before he stopped working on Boost.Threads. If it's > completed enough (I haven't examined it closely enough yet to tell), > I hope to move it into the a Boost release after the upcoming 1.32. > That won't help you right now, however. I feel sorry about that, but perhaps it is possible to get a look to the actual state? Arno

2 1

Boost & VC2005 (Whidbey)
by S.I.M. van Keulen 14 Oct '04

14 Oct '04

Hi all, recently I started 'porting' some projects to 64 bit Windows (AMD) using Visual Studio 2005. I noticed that the Compiler had trouble with Boost. Searching the net didn't provide much helpfull information. I wondered if any of you had tried anything with Boost and VC2005/Whidbey compilers. Or if any of you could direct me to some information source on the net. Thank you! Serge van Keulen

3 3

Re: "smart list" container?
by David Jones 13 Oct '04

13 Oct '04

"Caleb Epstein" <caleb.epstein(a)gmail.com> wrote in message news:<989aceac041012063240b6aa3(a)mail.gmail.com>... > On Mon, 11 Oct 2004 10:19:54 -0600, David M. Jones <djones(a)keymark.com> wrote: > > - The container itself would act more or less identically to std::list; > > - The iterators on the container would act like boost::weak_ptr in that they > > would know that they are invalid when the list element that they point to is > > removed. > > Can't you just do this with a std::list<boost::shared_ptr>? You can > convert the *iterators to weak_ptrs as needed. Or am I missing > something? There are a couple of reasons that std::list<boost::shared_ptr> is less than ideal. First, using the algorithms becomes cumbersome/annoying. Instead of being able to write std::list<boost::shared_ptr<int> > lst; // ... Populate the list int i; // ... Set the value of i std::list<boost::shared_ptr<int> >::iterator = std::find(lst.begin(), lst.end(), i); I instead need to create a function object to represent a boost::shared_ptr<int> having the desired value and then use find_if(). Second, I would lose the ability to store iterators and then check them later for validity. Suppose that I have a std::list<boost::shared_ptr<int> > named lst and I have two std::list<boost::shared_ptr<int> >::iterator objects it1 and it2 that happen to reference the same node in the list. If I call lst.erase(it1) then it2 also becomes invalid. If I call boost::weak_ptr<int>(*it2) I get an error because I cannot dereference the iterator because it is already invalid. This is how std::list objects are supposed to work but what I want to be able to do is now call something like it2.expired() to determine that the node being refered to by it2 is not invalid/expired/removed. One way to get around this is to store boost::weak_ptr objects derived from std::list<boost::shared_ptr>::iterator objects instead of storing it1 and it2 directly. But then I lose the advantage of having stored iterators: I cannot (after checking for expiration and being at the end of the list) call operator++() to move the iterator forward. Fundamentally, I don't want to be storing a "list of nodes of shared pointers of objects" but a "list of nodes of objects whose pointers to each other are shared pointers". And I want the iterators to be weak pointers to the nodes. Potentially a way to do this would be to write a custom allocator my_alloc that declares typedef boost::shared_ptr pointer; and then create a std::list<T, my_alloc<T> > This works because std::list uses the allocator rebinding mechanism to call my_alloc<node<T> > rather than my_alloc<T>. (In fact, my_alloc<T> is never used to allocate anything in std::list<T>!) However, there is a problem because the interface (concept a la Austern) of boost::shared_ptr is different than that of a regular pointer. So when the std::list code tries to call _Myhead = 0; I get a compiler error. (I am using MSVC 7.1: although this particular error may be STL implementation dependent, I do believe that the problem I am describing will occur with any STL implementation.) But I digress... The question of why the boost::shared_ptr interface/concept does not conform to that of a normal pointer is probably a topic for a separate posting.

2 1

RE: [Boost-users] Extending the boost::thread class
by Foster, Gareth 13 Oct '04

13 Oct '04

Could you make it something like "enum { eLow, eNormal, eHight }; myThread.priority(eHigh);"? Maybe something non specific would be do-able, and it might still be useful to those who aren't after lots of control? Not that I am well clued up, just a thought. Cheers! Gaz -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Ben Hutchings Sent: 13 October 2004 17:45 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Extending the boost::thread class arno.schaefer(a)sqs.de wrote: > Hi all, > I want to use the boost thread library as a base for my multiplatform > thread class. After I have studied the documentation I recognize that > there are not all things available at the moment what I need, so I try > to find out what is the best way to start my implementation. What I > need, is to implement the following additional methods: suspend, resume, > stop (or terminate), set_priority, get_priority, get_state and I want to > have the possibility to create threads in a suspend mode. <snip> Why do you think you want suspend, resume and terminate? There are very few safe uses for these operations, and programs that use them tend to suffer from data corruption and/or deadlocks. It would be fairly easy to add support for priority settings to Boost.Thread, but since priority values are only meaningful in the context of a scheduling policy and policies vary between operating systems it would be hard to provide a genuinely portable priority system. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Extending the boost::thread class
by arno.schaefer＠sqs.de 13 Oct '04

13 Oct '04

Hi all, I want to use the boost thread library as a base for my multiplatform thread class. After I have studied the documentation I recognize that there are not all things available at the moment what I need, so I try to find out what is the best way to start my implementation. What I need, is to implement the following additional methods: suspend, resume, stop (or terminate), set_priority, get_priority, get_state and I want to have the possibility to create threads in a suspend mode. I want to use the boost thread as is and extend the needed features in my own class, but it seems so that their is at the moment no legal way to get the internal thread resource from a created thread, so that I can implement the missing and perhaps not portable features by my own? So what is the prefered way to extend the thread class? Is their a reasonable way to do it or should I build my own class from scratch? many thanks for any input and guess, regards Arno

3 2

about boost graph library -- subgraph
by qyang＠cs.ucr.edu 12 Oct '04

12 Oct '04

Hi, I am new here. I recently downloaded the boost library from www.boost.org. I need to use the "subgraph" function in the library. I tried to run the example file "subgraph.cpp", but the running result was different from what was given in the file. Below is my running result and sample output: //my result: G0: 0 --> 1 1 --> 2 3 2 --> 5 3 --> 4 --> 1 5 5 --> 3 0(0,1) 1(1,2) 2(1,3) 6(2,5) 3(4,1) 4(4,5) 5(5,3) G1: 0 --> 2 1 --> 2 2 --> 6(0,2) 4(1,2) G2: 0 --> 1 1 --> 0(0,1) //sample output G0: 0 --> 1 1 --> 2 3 2 --> 5 3 --> 4 --> 1 5 5 --> 3 0(0,1) 1(1,2) 2(1,3) 6(2,5) 3(4,1) 4(4,5) 5(5,3) G1: 2 --> 5 4 --> 5 5 --> 6(2,5) 4(4,5) G2: 0 --> 1 1 --> 0(0,1) //====================================================== Basically what happened was that the vertex indices of the subgraph G1 in my output are child's local indices, however, the vertex indices of the subgraph G1 in the sample output is parent's global indices. Can somebody explain this? Is it a bug in the boost code? Thanks very much, Qiaofeng

2 1

Thread library Win32 static linking for MSVC 2003 release?
by Emilio Schapira 12 Oct '04

12 Oct '04

Does anybody know when will be the next release of Boost that has the threads library fixed such that it is possible to link statically in win32 platforms compiling with MSVC++ 2003? I have read that it will be fixed for the next release. Also, how stable is the current version of the library in the CVS repository? I was browsing through it and it seems to have been fixed. Anybody has experiences with it? Thanks, Emilio.

2 2

"Compiler threading support not turned on" error
by Glen Simmons 12 Oct '04

12 Oct '04

I'm attempting to use Boost.threads on Mac OS X 10.3 and am getting the error "Compiler threading support is not turned on" when trying to compile. I'm using Xcode, which is Apple's IDE, so I'm not sure what to do when the error text helpfully suggests I set the correct command line option. As far as I know, there's nothing extra that you have to do to enable threading support in the compiler. I've written multi-threaded apps using pthreads and never had to deal with command line options. Any suggestions? Thanks, Glen Simmons

4 9

"smart list" container?
by David M. Jones 12 Oct '04

12 Oct '04

Hello, I have run into a situation where the following std::list-like container would be useful. - The container itself would act more or less identically to std::list; - The iterators on the container would act like boost::weak_ptr in that they would know that they are invalid when the list element that they point to is removed. Does anyone know of such a container in any of the boost libraries, in another library or a way to accomplish the task using other means (such as iterator adaptors)? I looked at the newly proposed "smart containers" library, but it seems to be solving a different problem despite the similarity with the name I am using to describe what I want. Thanks in advance, David M. Jones

2 1

two boost.threads taking much longer than one
by Andrew Chapman 11 Oct '04

11 Oct '04

Hi everyone, I've got an operation which takes 14 seconds on a single thread, but is taking up to 45 seconds when running via two boost.threads on a dual proc machine (2x 3ghz Xeons, Fedora Core 1). The thread functor objects are being passed a lot of references (about 20) to some very large std::vectors. One thread always reads/writes from the start of the vectors to their midpoint, and the second thread from (midpoint+1) to the end of the vectors. The only thing I can think of is that the threads are taking a long time to fork and get running, perhaps moving a lot of stack data around or something? When I look at the output of 'top' with threads displayed, I see the two threads appear, but they only use about 50-60% CPU utilization each. The system monitor shows mostly red (Kernel) as opposed to blue (User). Any ideas? -- Andrew Chapman Senior Technical Director - Framestore CFC

3 3

Re: Re: [Boost-users] function_traits inheritance
by Victor Morilla 11 Oct '04

11 Oct '04

Peter Dimov wrote: >Victor Morilla wrote: >> >> template <typename FnType, FnType* fn> >> struct Translator<FnType, fn, 0> : >> function_traits<FnType> >> { >> typedef result_type type; > typedef typename function_traits<FnType>::result_type type; >> }; The question is, why result_type type definition is not inherited from function_traits ? ______________________________________________ Renovamos el Correo Yahoo!: ¡100 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

2 1

function_traits inheritance
by Victor Morilla 11 Oct '04

11 Oct '04

Guess someone why this code fails ? (g++3.3) ---- begin ----------------------- #include <boost/type_traits.hpp> #include <iostream> using namespace std; using namespace boost; int foo() { return 10; } template <typename FnType, FnType* fn, int Arity = function_traits<FnType>::arity> struct Translator; template <typename FnType, FnType* fn> struct Translator<FnType, fn, 0> : function_traits<FnType> { typedef result_type type; }; int main(int argc, char** argv) { Translator<int (), &foo>::type x; } ------------------- end code ------------------ error: ISO C++ forbids declaration of `result_type' with no type --------------------- end error ------------------- And another question: is there a portable equivalent to: Translator<typeof(foo), &foo> Thanks ______________________________________________ Renovamos el Correo Yahoo!: ¡100 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es

3 2

Problems in compilation with Boost
by Debayan Chaudhuri 11 Oct '04

11 Oct '04

Hi, I am evaluating Boost for use in our project. The platform OS is FreeBSD 4.9; which comes with gcc-2.95.3. I downloaded boost_1.30.0 and compiled the thread library on the FreeBSD box. When I try to compile a small test program using Boost threads; I encounter hundreds of compiler errors; mostly in the Boost header files. Is there a workaround to this ? Which version of Boost works with gcc-2.95.3 and what are the compiler options that will make it compile properly? regards, Debayan.

2 2

RE: [Boost-users] Problems with compiling Filesystem library on Solaris
by Barak Simon 11 Oct '04

11 Oct '04

By now I had time to check your suggestion, but I'm afraid I still get the same error when building boost libs: "/db/pub/eq/build/src/boost_1_31_0/boost/iterator/iterator_facade.hpp", line 622: Error: Could not find a match for boost::iterator_core_access::equal<boost::iterator_core_access::Facade1, boost::iterator_core_access::Facade2>(const boost::filesystem::directory_iterator, const boost::filesystem::directory_iterator, boost::is_convertible<boost::filesystem::directory_iterator, boost::filesystem::directory_iterator>). "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../src/operations_posix_windows.cpp", line 176: Where: While instantiating "boost::operator==<boost::filesystem::directory_iterator, boost::filesystem::path, boost::single_pass_traversal_tag, boost::filesystem::path&, int, boost::filesystem::directory_iterator, boost::filesystem::path, boost::single_pass_traversal_tag, boost::filesystem::path&, int>(const boost::iterator_facade<boost::filesystem::directory_iterator, boost::filesystem::path, boost::single_pass_traversal_tag, boost::filesystem::path&, int>&, const boost::iterator_facade<boost::filesystem::directory_iterator, boost::filesystem::path, boost::single_pass_traversal_tag, boost::filesystem::path&, int>&)". "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../src/operations_posix_windows.cpp", line 176: Where: Instantiated from non-template code. Are you sure that is the only line I need to comment out? Thanks, Barak ________________________ Barak Simon GED IT Core Platform 190 George St. Sydney, 2000 Phone +61 2 925 85070 Fax +61 2 925 95050 barak.simon+external@db. com To: boost-users(a)lists.boost.org Sent by: cc: boost-users-bounces@list Subject: RE: [Boost-users] Problems with compiling Filesystem library on Solaris s.boost.org 11/10/2004 11:45 Please respond to boost-users Thanks for the swift reply! In the interim I commented out the 2-3 problematic methods (which I am not using anyway) in the filesystem lib, but I like your solution better. A question on that though: On your solution, what exactly am I commenting out, that is, can the workaround break some other boost library or a significant assumption? Thanks, Barak Tomas.Puverle@morganstan ley.com To: boost-users(a)lists.boost.org Sent by: cc: boost-users-bounces@list Subject: RE: [Boost-users] Problems with compiling Filesystem library on Solaris s.boost.org 08/10/2004 18:47 Please respond to boost-users > Hi, > I get the following error from the Filesystem library when > building boost 1_31 on Solaris with sunpro compiler: > > "/db/pub/eq/build/src/boost_1_31_0/boost/iterator/iterator_fac > ade.hpp", line 622: Error: Could not find a match for > boost::iterator_core_access::equal<boost::iterator_core_access > ::Facade1, boost::iterator_core_access::Facade2>(const > boost::filesystem::directory_iterator, const > boost::filesystem::directory_iterator, > boost::is_convertible<boost::filesystem::directory_iterator, > boost::filesystem::directory_iterator>). > > "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../sr c/operations_posix_windows.cpp", line 176: Where: While instantiating > "boost::operator==<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int, > boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>(const > boost::iterator_facade<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>&, const > boost::iterator_facade<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>&)". > > "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../sr c/operations_posix_windows.cpp", line 176: Where: Instantiated from non-template code. > > > > It looks suspiciously similar to bug "[ 976241 ] Compiler > error for tokenizer on Solaris" from 2004-06-20, with the > difference that I am using version 5.3 of sunpro rather than 5.5. I have submitted a similar problem and the proposed fix recently. I am just waiting on our developers to confirm that it works before submitting it to boost, but it seems to fix the tokenizer problem, too. For a quick workaround (before the patch is applied) do this: At the top of boost/type_traits/detail/bool_trait_def.hpp you will see something like this: #if defined(__SUNPRO_CC) # define BOOST_TT_AUX_BOOL_TRAIT_VALUE_DECL(C) \ typedef mpl::bool_< C > type; \ enum { value = type::value }; \ /**/ # define BOOST_TT_AUX_BOOL_C_BASE(C) //1 Comment out the line marked with //1. That seems to have fixed my problems with both 5.3 and 5.5. HTH, Tom -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

Function type transformation and manipulation traits?
by Aaron W. LaFramboise 11 Oct '04

11 Oct '04

Are there any Boost support for manipulating function types? Operations I have in mind include: setting return type, setting argument type, changing number of arguments, et cetera. If not, is there some generally accepted way to accomplish this, and is any work being done to add this feature to Boost? Aaron W. LaFramboise

2 3

RE: [Boost-users] Problems with compiling Filesystem library on Solaris
by Barak Simon 11 Oct '04

11 Oct '04

Thanks for the swift reply! In the interim I commented out the 2-3 problematic methods (which I am not using anyway) in the filesystem lib, but I like your solution better. A question on that though: On your solution, what exactly am I commenting out, that is, can the workaround break some other boost library or a significant assumption? Thanks, Barak Tomas.Puverle@morganstan ley.com To: boost-users(a)lists.boost.org Sent by: cc: boost-users-bounces@list Subject: RE: [Boost-users] Problems with compiling Filesystem library on Solaris s.boost.org 08/10/2004 18:47 Please respond to boost-users > Hi, > I get the following error from the Filesystem library when > building boost 1_31 on Solaris with sunpro compiler: > > "/db/pub/eq/build/src/boost_1_31_0/boost/iterator/iterator_fac > ade.hpp", line 622: Error: Could not find a match for > boost::iterator_core_access::equal<boost::iterator_core_access > ::Facade1, boost::iterator_core_access::Facade2>(const > boost::filesystem::directory_iterator, const > boost::filesystem::directory_iterator, > boost::is_convertible<boost::filesystem::directory_iterator, > boost::filesystem::directory_iterator>). > > "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../sr c/operations_posix_windows.cpp", line 176: Where: While instantiating > "boost::operator==<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int, > boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>(const > boost::iterator_facade<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>&, const > boost::iterator_facade<boost::filesystem::directory_iterator, > boost::filesystem::path, boost::single_pass_traversal_tag, > boost::filesystem::path&, int>&)". > > "/db/pub/eq/build/src/boost_1_31_0/libs/filesystem/build/../sr c/operations_posix_windows.cpp", line 176: Where: Instantiated from non-template code. > > > > It looks suspiciously similar to bug "[ 976241 ] Compiler > error for tokenizer on Solaris" from 2004-06-20, with the > difference that I am using version 5.3 of sunpro rather than 5.5. I have submitted a similar problem and the proposed fix recently. I am just waiting on our developers to confirm that it works before submitting it to boost, but it seems to fix the tokenizer problem, too. For a quick workaround (before the patch is applied) do this: At the top of boost/type_traits/detail/bool_trait_def.hpp you will see something like this: #if defined(__SUNPRO_CC) # define BOOST_TT_AUX_BOOL_TRAIT_VALUE_DECL(C) \ typedef mpl::bool_< C > type; \ enum { value = type::value }; \ /**/ # define BOOST_TT_AUX_BOOL_C_BASE(C) //1 Comment out the line marked with //1. That seems to have fixed my problems with both 5.3 and 5.5. HTH, Tom -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

Help ... BOOST::thread 's certain constuctor methods fails with STLPort
by Raj 09 Oct '04

09 Oct '04

Hi I have build boost libraries for a) regular gcc b) gcc-STLPort the following code works perfectly for "gcc" and throws up the following errors for "gcc-STLPort". // this is my function object that // takes in input parameters as part of its constructor. func_obj instance(data,m_regMap); boost::shared_ptr<thread> pThread(new boost::thread(instance)); ERROR: mystuff.cpp:101: undefined reference to `boost::thread::thread[in-charge] (boost::function0<void, _STL::allocator<boost::funct ion_base> > const&)' If I assume that the boost runtime library has not been linked, that is not the case.(ldd tells me that i have) whereever I use 'xtime','lock' or 'condition' it doesn't complain. WHAT IS STRANGE IS THE FOLLOWING COMPILES boost::thread thrd; boost::thread thrd(func_obj); // it is the actual fo not an instance. Any help would be greatly appreciated. This happens on Linux/with STLPort 4.6.2/gcc 3.2.3

1 0