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.
That's up to you, but I contend that "some of the development versions"
is meaningless. There is only one development version: the latest.
Testing the way you suggest would mean you couldn't use the feature in a
snapshot, so you couldn't test your code until the release was done.
Which would be counterproductive IMO, but its your prerogative.
> But we're talking about a change that breaks existing code here, not
> about new features.
And I'm talking about a versioning system than handles that so long as
you remember that we don't support code based on development versions.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
