Ulf M�ller wrote:
>
> > release without change if they track all the way to the end. We don't
> > support distinguishing an arbitrary snapshot of a development version,
> > though; only the latest. So, if you have support for a feature in 0.9.4,
> > then you test like this:
> >
> > #if OPENSSL_VERSION >= 0x00904000
>
> In that case I would just test for the release version number
> OPENSSL_VERSION >= 0x000904100, ignoring that the feature already is
> present in some of the development versions.
>
> But we're talking about a change that breaks existing code here, not
> about new features.
I don't want to infer what was done in the past is necessarily right but
just about every version change major or minor has broken *some*
existing code.
The typesafe stack stuff in the current release for example breaks some
stuff I have (not just a warning actual compiler choking).
Thats probably just an indication that I tend to do weirder stuff in my
code though :-)
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
