Re: [boost] Re: Version #defines?

From: David Abrahams (abrahams_at_[hidden])
Date: 2001-03-11 10:20:03

I agree with Dean on this one. Also, I think it's much less important that
the #define be memnonic for the 3 parts of the version number than that it
march steadily forward. We can always provide a header
boost/release_version.hpp with memnonic constants like:

#define BOOST_VERSION_1_21_0 0x0177

-Dave

----- Original Message -----
From: <deansturtevant_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Sunday, March 11, 2001 9:49 AM
Subject: [boost] Re: Version #defines?

> --- In boost_at_y..., Daryle Walker <darylew_at_m...> wrote:
> > Should we add #defines for the current Boost version?  They
> probably would
> > go in "config.hpp".  They could go something like:
> >
> > //===================================
> > #define BOOST_VERSION_MAJOR   1
> > #define BOOST_VERSION_MINOR  21
> > #define BOOST_VERSION_FIX     0
> > //===================================
> >
> > --
> Based on recent experience looking at code which tests for the minor
> version of the GCC compiler without testing for the major version, I
> think separating out major from minor in #defines is not a good idea.
> How about a single version number?
>
>
>
> List-Unsubscribe: <mailto:boost-unsubscribe_at_[hidden]>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>