- Boost-users - lists.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