This is a discussion on Re: OpenSSL breaks with gcc 4.2 - Openssl ; Dr. Stephen Henson wrote: > On Wed, Nov 08, 2006, Ben Laurie wrote: > >> But it gets cast back to the correct type before it is called. These >> casts are done the way they are to get type-safety. ...
Dr. Stephen Henson wrote:
> On Wed, Nov 08, 2006, Ben Laurie wrote:
>> But it gets cast back to the correct type before it is called. These
>> casts are done the way they are to get type-safety. Removing that option
>> strikes me as a bad thing.
> Yes and that happened to be a way that worked on all the compilers OpenSSL
> used at the time.
> The main purpose of the casting it to provide type safe checking at compile
> time and have no runtime overhead.
> If there is an alternative to achieve the same result (inline calls perhaps?)
> then we can have that as a compilation option.
Sure, I have no objection to replacing the kludge. So long as we don't
lose compile-time type-safety.
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff
OpenSSL Project http://www.openssl.org
Development Mailing List firstname.lastname@example.org
Automated List Manager email@example.com