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

request for solaris/forte toolset jamfile
by Dr Bruce Lowery <bruce_lowery＠yahoo.com> 10 Jan '03

10 Jan '03

If anyone has a somewhat working jamfile for solaris/forte, could you post a copy of it? --bruce

4 3

Installing boost regex
by Alisdair Meredith 10 Jan '03

10 Jan '03

We're (still!) in the process up upgrading our software to the latest borland compiler, BCB6 I am now at the stage of trying to get the boost libraries integrated into our builds. After running bjam I get some libboost_regex libs, but these don't seem to be used. Reading the separate install procedure under the regex library, I find another install procedure that produces a set of libraries targetted at BCB that do solve my problems. Is this the correct procedure? Is there any way to integrate this with the jam scripts in the future? If not, should we add a link under installing boost to the separate procedure for the regex libraries? -- AlisdairM Team Thai Kingdom

2 2

stop a thread
by hlh771 <hlh771＠yahoo.com.cn> 10 Jan '03

10 Jan '03

How to stop(or cancel) a thread? Suppose I have a main thread and a worker thread, the worker thread does something looply,and when the main thread get a message indicating the process should exit, I want stop the worker thread,how to do that?I have read other thread library,their thread class supply a method called stop or cancel which stops the thread. Their Implementation is:the thread class has a data member indicating whether the thread should stop,and the thread function looply check the data member whether the thread should stop.Generally the data member's type is a bool or Event. Is it the best way to stop the thread? How the boost to deal with this? Thanks in advance.

1 0

Starting to use unit tests
by Scott Nesbitt 10 Jan '03

10 Jan '03

I am in to process of adding the boost test framework to our project, and am looking for advice or samples for how best to do this. Specifically, we have multiple executables sharing several libraries. I was thinking about having a different test suite for each library, but don't see much documentation on using multiple test suites. Any advice or pointers? Thanks, Scott Nesbitt scott.nesbitt(a)yahoo.com __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 1

bind() and argument_type?
by Duane Murphy 09 Jan '03

09 Jan '03

I am trying to use bind() with std::not1() (I think this is what I want to do :-). But std::not1() gets a compiler error because bind doesnt have an argument_type typedef. bool is_something( int x, int y ) { return something( x, y ); } { ... if ( std::not1( boost::bind( is_something, 3, _1 ) ) ) { // not something } } Am I approaching this incorrectly? Does bind support argument_type? Thanks for the advice, ...Duane

2 1

RE: [Boost-Users] Problem with BOOST_STATIC_ASSERT
by Randy Bowen 09 Jan '03

09 Jan '03

Thanks to John and Richard Cox for investigating this. > You will be pleased to know that it works correctly with VC7.1. > > John Maddock.

1 0

RE: [Boost-Users] Problem with BOOST_STATIC_ASSERT
by Randy Bowen 09 Jan '03

09 Jan '03

Thanks for investigating this, John. I don't have access to the beta VC7.1 compiler. Do you (or does anyone else) know if this will still be a problem with the forthcoming version of the Microsoft compiler? Randy Bowen -----Original Message----- From: John Maddock [mailto:john_maddock@compuserve.com] Sent: Wednesday, January 08, 2003 4:17 AM To: Boost-Users(a)yahoogroups.com Subject: Re: [Boost-Users] Problem with BOOST_STATIC_ASSERT > Some further follow-up on this. I've created a minimal program that > exhibits the new problem behavior: > > /******************************************/ > #include <boost/type_traits.hpp> > #include <boost/static_assert.hpp> > > template < typename ValueType > > struct A > { > BOOST_STATIC_ASSERT(boost::is_integral<ValueType>::value); > }; > > extern "C" int main(int argc, char* argv[]) > { > return 0; > } > /******************************************/ > > The fact that this assertion fails is counter-intuitive to me, since > there is no instantiation to compile. Note that this behavior seems > limited to the use of "is_integral" as the type predicate. Constructing > a similar program using "is_POD" behaves as expected: I can reproduce that with both VC6 and VC7, all the other compilers I have access to are OK with it. It's clearly a compiler bug, because the assert is triggered even though no instance of the template class is ever created. Unfortunately I don't have any kind of workaround :-( John Maddock http://ourworld.compuserve.com/homepages/john_maddock/index.htm Yahoo! Groups Sponsor ADVERTISEMENT 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 the Yahoo! Terms of Service.

2 1

RE: [Boost-Users] Problem with BOOST_STATIC_ASSERT
by richard_cox＠dell.com 09 Jan '03

09 Jan '03

On Wednesday, January 08, 2003 5:29 PM, Randy Bowen [mailto:rbowen@stamps.com] wrote: > -----Original Message----- > From: > Sent: > To: Boost-Users(a)yahoogroups.com > Subject: RE: [Boost-Users] Problem with BOOST_STATIC_ASSERT > > > Thanks for investigating this, John. I don't have access to > the beta VC7.1 compiler. Do you (or does anyone else) know > if this will still be a problem with the forthcoming version > of the Microsoft compiler? > > Randy Bowen > > > > -----Original Message----- > From: John Maddock [mailto:john_maddock@compuserve.com] > Sent: Wednesday, January 08, 2003 4:17 AM > To: Boost-Users(a)yahoogroups.com > Subject: Re: [Boost-Users] Problem with BOOST_STATIC_ASSERT > > > > Some further follow-up on this. I've created a minimal > program that > > exhibits the new problem behavior: > > > > /******************************************/ > > #include <boost/type_traits.hpp> > > #include <boost/static_assert.hpp> > > > > template < typename ValueType > > > struct A > > { > > BOOST_STATIC_ASSERT(boost::is_integral<ValueType>::value); > > }; > > > > extern "C" int main(int argc, char* argv[]) > > { > > return 0; > > } > > /******************************************/ > > > > The fact that this assertion fails is counter-intuitive to > me, since > > there is no instantiation to compile. Note that this > behavior seems > > limited to the use of "is_integral" as the type predicate. > Constructing > > a similar program using "is_POD" behaves as expected: > > I can reproduce that with both VC6 and VC7, all the other > compilers I have access to are OK with it. It's clearly a > compiler bug, because the assert is triggered even though no > instance of the template class is ever created. Unfortunately > I don't have any kind of workaround :-( > > John Maddock > http://ourworld.compuserve.com/homepages/john_maddock/index.ht m The code as quoted built without error OK on VC++7.1 RC2 (Final Beta) here... using snapshot of boost taken last weekend. Richard Cox Senior Software Developer Dell Technology Online All opinions and statements mine and do not in any way (unless expressly stated) imply anything at all on behalf of my employer

1 0

Re: [Boost-Users] Re: Re: Slight Alteration to Boost Directory Structure
by William E. Kempf 09 Jan '03

09 Jan '03

> From: "Simon Bailey <conic(a)bigpond.com>" <conic(a)bigpond.com> > --- In Boost-Users(a)yahoogroups.com, "Paul Mensonides" <yg-boost- > users@m...> wrote: > > "William E. Kempf" <wekempf@c...> wrote in message > > > > > That still misses the point. Boost currently won't help you to > install > > the library, but installation certainly wouldn't entail copying the > entire > > $BOOST_ROOT tree to the $INCLUDE directory on your system. You'd > only copy > > the $BOOST_ROOT/boost tree there. > > > > Yes, and this is why I said that it hasn't been a problem for me. > However, > > I see where the OP is coming from as well. > > > > Paul Mensonides > > Paul understands me correctly. I confused the issue by making two > requests at once. > > Mainly, I want to include other libraries alongside boost and provide > a single include path. That is the first wish. Bill has pointed out > that I could move BOOST_ROOT/boost into my INCLUDE directory. I > didn't know that - I thought it might break things. > > The second thing I was suggesting (and this is quite minor) was that > we make the change to include smart_ptr.hpp (etc.) and thread.hpp > (etc.) at the same directory level. I thought that the > subdirectories (like /thread) were the way of the future. I didn't > realise that the plan was to move all the headers into > BOOST_ROOT/boost. > > So it seems my first wish is not needed and my second wish is already > on the drawing board. :-) No, it's never been planned to move all headers into $BOOST_ROOT/boost. That would be problematic at best. The headers are in subdirectories to avoid name clashes, and that's how it should be for large libraries and/or libraries that use common names. What many of these libraries do, and what Boost.Threads will do with the next release, however, is to have a *single* include header in $BOOST_ROOT/boost that includes all the other headers from the specific sub-library. This (mostly) avoids the dangers of name clashes, gives a simple single include file for many uses, yet retains the ability for users to include only what they need to in order to reduce compilation time, etc. For example, both of the following would be legal: #include <boost/thread/thread.hpp> #include <boost/thread/mutex.hpp> #include <boost/thread/condition.hpp> // ... code using boost::thread, boost::mutex and // boost condition - or - #include <boost/thread.hpp> // ... code using boost::thread, boost::mutex and // boost condition William E. Kempf wekempf(a)cox.net

1 0

Re: [Boost-Users] Re: Re: Slight Alteration to Boost Directory Structure
by William E. Kempf 09 Jan '03

09 Jan '03

> From: "Simon Bailey <conic(a)bigpond.com>" <conic(a)bigpond.com> > Suddenly I remember why I wanted the directory structure change... > > I could achieve what I want by moving BOOST_ROOT/boost into my > INCLUDE directory. But the disadvantage with that is that I need to > perform a move operation. > > *** In my current development environment, my source control > directory structure mirrors my release directory structure exactly. > *** > > So, in source control I have: > > /include > --/BOOST_ROOT > ----/boost <- headers are here > --/my_lib <- headers are here > > But, in my release I want to have: > /include > ----/boost <- headers are here > ----/my_lib <- headers are here > > I was suggesting the change so that source control and relase could > be the same. This would necessitate that documentation and source > for boost would have to be within the boost (include) directory. > Some might find that a worse alternative I suppose. I think most would. I know I do. William E. Kempf wekempf(a)cox.net

1 0

which boost lib to use for generic list sort by member function ?
by Philippe Guglielmetti 09 Jan '03

09 Jan '03

I try to define a "sortby" method that would sort a list using any member function that fits some constraints (taking no parms, returning a result that can be compared using the > operator and being const) I wrote this: template <class T> class mylist:public std::list<T> { // ... template <typename T2, typename R, R (T2::*F)() const> struct cmp: public std::binary_function<T,T,bool> { bool operator()(const T& f1, const T& f2) {return (f1.F)() > (f2.F)();}; }; template <typename T2, typename R> bool sortby(R (T2::*F)() const) { sort(cmp<T,R,F>()); return true; }; }; // class mylist using VC6 (I know...) I get these 3 errors: algos.h(356) : error C2440: 'specialization' : cannot convert from 'double (__thiscall cadoo::cadFace::*)(void) const' to 'double (__thiscall cadoo::cadFace::*)(void)' algos.h(356) : error C2975: 'cmp' : invalid template argument for 'F', constant expression expected algos.h(356) : error C2514: 'dyl::List<class cadoo::cadFace>::cmp<class cadoo::cadFace,double,0>' : class has no constructors any idea ? I also checked boost.org for help on functors, lambda ... but could not figure out how to use them simply for my application. thanks! Philippe Guglielmetti

1 0

Boost::python + vc + sgistl problem
by yg-boost-users＠m.gmane.org 09 Jan '03

09 Jan '03

I use Boost::Python module with VC and SGI stl. But I got some compile errors like mix\max redefine.... Who know how to solve this problem??? -- CNews 0.4

1 0

HELP: Command line sample.
by Lichun Bao 09 Jan '03

09 Jan '03

Hi, Can someone please provide a sample single command line compile using g++ that generates the final executable binary for a test example? For example, in the unpacked BOOST directory, how to do something like: g++ <options> libs/graph/example/bfs-example.cpp -o \ /tmp/bfs-example for the final executable? Thanks, Lichun

1 0

Re: [Boost-Users] Boostifying GluCat
by William E. Kempf 08 Jan '03

08 Jan '03

Sorry folks, this posting never should have made the list. As one of the moderators, I hit the wrong button here. Sorry for any inconvenience. William E. Kempf wekempf(a)cox.net

1 0

Boostifying GluCat
by Paul C. Leopardi 08 Jan '03

08 Jan '03

Bjorn, GluCat is a new numeric template class library, hopefully destined for promotion to Boost. I would like to know where there is some documentation on how to: 1. Add concepts. Is there such a thing as a non-commutative algebra concept? How do I check concepts? 2. Add numeric limits. Limits of eg. framed_multi<T> would default to limits of T. 3. Add numeric promotion_traits. What are promotion_traits ? There is currently a discussion on ublas-dev mailing list about promotion_traits within uBLAS. 3. Add numeric type_traits. Thanks On Thu, 9 Jan 2003 00:18, you wrote: > Paul, > unfortunately this post is off topic for Boost-Users, and is thus > rejected. While it may well be of interest to some of our subscribers, > and the usage of uBLAS is a nice success story, we do not allow > announcement postings - only topics related to usage of Boost libraries. > > Regards, > Bjorn Karlsson > Moderator

1 0

Re: [Boost-Users] Re: Re: Slight Alteration to Boost Directory Structure
by William E. Kempf 08 Jan '03

08 Jan '03

> From: "Paul Mensonides" <yg-boost-users(a)m.gmane.org> > "William E. Kempf" <wekempf(a)cox.net> wrote in message > news:20030108172855.VIMZ4411.lakemtao01.cox.net@smtp.east.cox.net... > > > > I believe that he is talking about the root Boost directory which is the > > > parent directory of the Boost headers. If, for instance, I have a > directory > > > "include" that I want to put all my library headers in and have a single > > > environment variable to specify the header search paths. This cannot be > > > done with Boost because the Boost headers are located at > > > "boost/boost/*.hpp", not "boost/*.hpp". Furthermore, you can't even put > > > Boost in the same directory as other includes, because you might get a > > > conflict between "include/boost" and "include/boost/boost". It doesn't > > > bother me personally, but I see the point that he is getting at. > > > > If that's the point (which doesn't seem to be, since he talks about "new > boost libraries" doing the right thing), I can't agree. Moving Boost > headers out of a boost subdirectory and into the top-level include directory > (so <boost/shared_ptr.hpp> becomes <shared_ptr.hpp>) would only result in > name clashes with other headers. > > That is not what he (or I) means. He is suggesting that the path to > "shared_ptr.hpp" should be "$INCLUDE/boost/shared_ptr.hpp" rather than > "$INCLUDE/boost/boost/shared_ptr.hpp", which is the way it is now. > Everything would still be the same for including headers except that only a > single search path is necessary to setup with the compiler. That's the way it is now *only* if you set your include directories incorrectly. When they are properly set to $BOOST_ROOT then it's only <boost/shared_ptr.hpp>, not <boost/boost/shared_ptr.hpp>. William E. Kempf wekempf(a)cox.net

2 1

Re: [Boost-Users] Re: Slight Alteration to Boost Directory Structure
by William E. Kempf 08 Jan '03

08 Jan '03

> From: "Paul Mensonides" <yg-boost-users(a)m.gmane.org> > Date: 2003/01/08 Wed PM 12:18:35 EST > To: boost-users(a)yahoogroups.com > Subject: [Boost-Users] Re: Slight Alteration to Boost Directory Structure > > "William E. Kempf" <wekempf(a)cox.net> wrote in message > > > > 2. Each library bundled with boost means another #include search > > > path needs to be added. > > > > No, there's only one path added for all Boost libraries, > $BOOST_ROOT/boost. > > Here I think he is talking about libraries other than Boost. How can anything we do to the Boost directory structure effect this? I don't really think that's what he meant. > > > Proposed solution: > > > 1. Create a single boost include directory instead of having the two > > > nested ones that there are now. > > > > What two nested ones? > > I believe that he is talking about the root Boost directory which is the > parent directory of the Boost headers. If, for instance, I have a directory > "include" that I want to put all my library headers in and have a single > environment variable to specify the header search paths. This cannot be > done with Boost because the Boost headers are located at > "boost/boost/*.hpp", not "boost/*.hpp". Furthermore, you can't even put > Boost in the same directory as other includes, because you might get a > conflict between "include/boost" and "include/boost/boost". It doesn't > bother me personally, but I see the point that he is getting at. If that's the point (which doesn't seem to be, since he talks about "new boost libraries" doing the right thing), I can't agree. Moving Boost headers out of a boost subdirectory and into the top-level include directory (so <boost/shared_ptr.hpp> becomes <shared_ptr.hpp>) would only result in name clashes with other headers. William E. Kempf wekempf(a)cox.net

2 1

Re: [Boost-Users] Slight Alteration to Boost Directory Structure
by William E. Kempf 08 Jan '03

08 Jan '03

> From: "Simon Bailey <conic(a)bigpond.com>" <conic(a)bigpond.com> > > I've been using boost for about a year now. I upgraded from 27 to > 28 and appreciated the backwards compatability. But I'm wondering > if a slight modification to the directory structure is in order? > > I have written a cross-platform class library. The library provides > high-level business objects and comes bundled with boost 1.28.0 to > provide support for threads, CRC, shared_ptr, and function (or > whatever else the end user might want). > > Currently, users need to add two directories to their #include > search path: > include/boost > include/sb_library > > Then, in their source code: > #include <boost/shared_ptr.hpp> > #include <boost/thread/thread.hpp> > #include <sb_library/business_facet/business_object.h> > > Two problems (albeit very minor ones!) > 1. Boost has two levels of includes (due to it's history of course). Two levels? There's only one, $BOOST_ROOT/boost. To avoid name clashes, many libraries are located in library specific directories off of this, as you see with <boost/thread/thread.hpp>. Something that many libraries do (and Boost.Threads will be updated to do shortly) is to have a single header in the root include directory that includes all of the headers from the library directory, thus for Boost.Threads you'd include only <boost/thread.hpp> instead of <boost/thread/thread.hpp>, <boost/thread/mutex.hpp> etc. > 2. Each library bundled with boost means another #include search > path needs to be added. No, there's only one path added for all Boost libraries, $BOOST_ROOT/boost. > Proposed solution: > 1. Create a single boost include directory instead of having the two > nested ones that there are now. What two nested ones? > 2. Put all boost headers into a sub-directory of boost > eg <boost/ptr/shared_ptr.hpp>, <boost/thread/thread.hpp>. (It's a > small change for existing users to change their includes). This is mostly how it is now... though many headers don't live in library specific subdirectories (which is probably how it should be). > 3. Place all src, documentation etc. into a directory within boost > called "private" or something. > > Suggested directory structure: > > --include // This is the only directory needed to be specified in > the #include search path > ----other_library1 > ----other_library2 > ----boost > -------ptr > -------thread > -------private > ----------documentation > ----------src > ----------thread > > In other words, you will have <boost/ptr/...> and <boost/thread/...> > but never <boost/private/...>. This is just a variation on what's currently done, and I can't see how it buys you anything, and actually is a more confusing layout IMHO. > I think it's worth breaking the backwards compatability a little in > order to bring the older boost headers in line with the directory > structure of the newer ones like thread. I also think enabling a > single include path for multiple libraries is useful. Boost.Threads followed existing directory guidelines (as do all libraries). There's no difference between it and "older" libraries (note that Boost.Threads is not that new). William E. Kempf wekempf(a)cox.net

2 1

is_convertible and array size question
by globeordi＠free.fr 08 Jan '03

08 Jan '03

Hello all, Just perhaps a silly question but who knows ? I have a small class that encapsulates a char[] type such as: template <const unsigned int n> struct C_Array { enum { size = n }; typedef char (&Array)[size]; typedef const char (&ConstArray)[size]; C_Array() { memset(&v[0], 0, 30); v[0] = '6'; v[1] = '7'; v[2] = '8'; v[3] = '9'; } char v[n]; int toto; char & operator[](const unsigned int i) { return v[i]; } const char & operator[](const unsigned int i) const { return v[i]; } operator Array () { return v; } operator ConstArray () const { return v; } }; Thanks to the operator Array, the objects of this class can be converted to references to arrays and the following pseudo-code works fine as expected: C_Array<30> obj; cout << boost::is_convertible<obj, char[]>::value << endl; But what I want to get is the actual size of the converted array. In the example the size is 30. It is not very important (workaround exists), just curious to see how it can be done without telling to compiler more information. Best regards Joseph Canedo

1 0

RE: [Boost-Users] Problem with BOOST_STATIC_ASSERT
by Randy Bowen 08 Jan '03

08 Jan '03

Some further follow-up on this. I've created a minimal program that exhibits the new problem behavior: /******************************************/ #include <boost/type_traits.hpp> #include <boost/static_assert.hpp> template < typename ValueType > struct A { BOOST_STATIC_ASSERT(boost::is_integral<ValueType>::value); }; extern "C" int main(int argc, char* argv[]) { return 0; } /******************************************/ The fact that this assertion fails is counter-intuitive to me, since there is no instantiation to compile. Note that this behavior seems limited to the use of "is_integral" as the type predicate. Constructing a similar program using "is_POD" behaves as expected: /******************************************/ #include <boost/type_traits.hpp> #include <boost/static_assert.hpp> template < typename ValueType > struct B { BOOST_STATIC_ASSERT(boost::is_POD<ValueType>::value); }; struct C {}; extern "C" int main(int argc, char* argv[]) { // B<int> Bint; /* OK to add */ // B<C> BC; /* causes error */ return 0; } /******************************************/ Here, no error occurs until there is an attempt to instantiate B<C>. Randy Bowen -----Original Message----- From: Randy Bowen Sent: Tuesday, January 07, 2003 1:40 PM To: Boost-Users(a)yahoogroups.com Subject: [Boost-Users] Problem with BOOST_STATIC_ASSERT I'm in the process of updating some applications from use of Boost 1.28.0 to 1.29.0, using MSVC7. I've noticed that a number of static assertions that used to compile now generate errors. The assertions all use is_integral to perform a type validation - e.g.: BOOST_STATIC_ASSERT(::boost::is_integral<value_type>::value); This produces an error of the form: c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(145) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(143) : see reference to class template instantiation 'sme::StringSerializer<_StringType,>::StringWriter<<template parameter>>' being compiled c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(169) : see reference to class template instantiation 'sme::StringSerializer<_StringType,>' being compiled I believe that the data type is integral, and is complete at compile time. Any known reason why this would happen? Randy Bowen

2 1

Severe bugs in lambda/algorithm.cpp
by Markus Werle 08 Jan '03

08 Jan '03

Hi! I wonder whether this file ever was included by anyone else but me and which compiler did let this pass without complaint. Besides the #include <utilities> which never ever happens we have 2 errors in struct count struct count { template <class Args> struct sig { typename ::std::iterator_traits< // **************************************************** // ERROR: typedef is not allowed here typedef typename boost::remove_const< typename boost::tuples::element<1, Args>::type >::type >::difference_type type // ERROR: semicolon missing }; Same errors in count_if beginning at line 172. ----------------------------------------------------- In line 613: a duplicate parameter name c operator()(A a, B b, C c, D c) const Same on line 681 best regards, Markus

1 0

lambda/algorithm.hpp: #include <utilities>?
by Markus Werle 08 Jan '03

08 Jan '03

Hi! Line 23 in lambda/algorithm.hpp reads #include <utilities> // for std::pair IMHO (and that of intel's C++ and SGI's documentation) this line should be #include <utility> // for std::pair right? best regards, Markus

1 0

Slight Alteration to Boost Directory Structure
by Simon Bailey <conic＠bigpond.com> 07 Jan '03

07 Jan '03

I've been using boost for about a year now. I upgraded from 27 to 28 and appreciated the backwards compatability. But I'm wondering if a slight modification to the directory structure is in order? I have written a cross-platform class library. The library provides high-level business objects and comes bundled with boost 1.28.0 to provide support for threads, CRC, shared_ptr, and function (or whatever else the end user might want). Currently, users need to add two directories to their #include search path: include/boost include/sb_library Then, in their source code: #include <boost/shared_ptr.hpp> #include <boost/thread/thread.hpp> #include <sb_library/business_facet/business_object.h> Two problems (albeit very minor ones!) 1. Boost has two levels of includes (due to it's history of course). 2. Each library bundled with boost means another #include search path needs to be added. Proposed solution: 1. Create a single boost include directory instead of having the two nested ones that there are now. 2. Put all boost headers into a sub-directory of boost eg <boost/ptr/shared_ptr.hpp>, <boost/thread/thread.hpp>. (It's a small change for existing users to change their includes). 3. Place all src, documentation etc. into a directory within boost called "private" or something. Suggested directory structure: --include // This is the only directory needed to be specified in the #include search path ----other_library1 ----other_library2 ----boost -------ptr -------thread -------private ----------documentation ----------src ----------thread In other words, you will have <boost/ptr/...> and <boost/thread/...> but never <boost/private/...>. I think it's worth breaking the backwards compatability a little in order to bring the older boost headers in line with the directory structure of the newer ones like thread. I also think enabling a single include path for multiple libraries is useful. Cheers Simon

1 0

Problem with BOOST_STATIC_ASSERT
by Randy Bowen 07 Jan '03

07 Jan '03

I'm in the process of updating some applications from use of Boost 1.28.0 to 1.29.0, using MSVC7. I've noticed that a number of static assertions that used to compile now generate errors. The assertions all use is_integral to perform a type validation - e.g.: BOOST_STATIC_ASSERT(::boost::is_integral<value_type>::value); This produces an error of the form: c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(145) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' with [ x=false ] c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(143) : see reference to class template instantiation 'sme::StringSerializer<_StringType,>::StringWriter<<template parameter>>' being compiled c:\Perforce\Development\Web\cppinclude\domestic\Application Framework\State Machine Engine\StringSerializer.h(169) : see reference to class template instantiation 'sme::StringSerializer<_StringType,>' being compiled I believe that the data type is integral, and is complete at compile time. Any known reason why this would happen? Randy Bowen

1 0

uBLAS - Calculation of Inverse and/or Least Squares
by jonny5cents <jon_nichols95＠hotmail.com> 07 Jan '03

07 Jan '03

Hello All, Can anyone suggest the best way to use uBLAS to calculate the inverse of a matrix?? One of the reasons I want to do this is to solve a linear least squares problem, which I know can be done without explicitly solving for the inverse. Does anyone know if this is possible?? thanks, jon

3 2