In article <[EMAIL PROTECTED]> you wrote:
> [EMAIL PROTECTED] wrote:
>
>[...]
> So, whatever we call the next one, the string version must come after
> "0.9.2b" (intuitively) and the hex version must be > 0x0922.
EXACTLY! Or we can forget any existing pre-processor checks...
> So, whatever we call the next one, the string version must come after
> "0.9.2b" (intuitively) and the hex version must be > 0x0922.
Name the next "major" release 1.0 with hex code 0x01, then go on
with 1.1 == 0x010100, etc., and all of a sudden the problem is vanished.
Right?
Ulf Möller wrote:
>
> >OpenSSL version 0.9.2b released
>
> May I ask, why "b"?
Because the development versions were all called 0.9.2. If this were
Apache, we'd've called them 0.9.2-dev, and the release 0.9.2. But
OpenSSL doesn't have a granular enough versioning system to permit that.
Che
>OpenSSL version 0.9.2b released
May I ask, why "b"?
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager
