In article <[EMAIL PROTECTED]> you wrote:
> Ulf Möller wrote:
>>
>> > Do we? We don't currently have a policy of incrementing version numbers
>> > during development cycles.
>>
>> We don't have the policy to make incompatible changes to the API either,
>> do we?
>
> Yes, I'm afraid we do.
>
>> Using the wrong pointer type is an *error* with g++, for example, so we
>> need a way to detect this.
>
> We can detect this _at the release level_ (or beta). People using
> snapshots just have to keep up, I'm afraid. At least, that's the way its
> been up to now. I'm reluctant to start versioning within development
> cycles, because it is tedious.
Yes, Ben is right: At the release level people can use OPENSSL_VERSION_NUMBER
and that should be enough. When we start at the development level to increase
a number for every API change we get the same chaos as for Apache: it's often
forgotten, people complain about two much such numbers to check for, etc. pp.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
