On Tue, Jun 5, 2012 at 4:35 AM, Jakob Bohm <jb-open...@wisemo.com> wrote: > On 6/5/2012 6:19 AM, Zack Weinberg wrote: >> According to http://gcc.gnu.org/ml/gcc-patches/2011-03/msg00376.html the >> last widely-used platform that crashed on free(NULL) was SunOS 4, which >> "stopped being a reasonable portability target around 2007". > Actually, that is not really what it says when read closely. > > What it really says is than some guy named "Jim Meyering" believed > (possibly mistakenly) that the free(NULL) issue existed only on > SunOS 4 (he gave no reason for that belief).
Rather, that it existed on many pre-C89 platforms including SunOS 4, but all of them ceased to be interesting portability targets before SunOS 4 did. > On top of that Jim > Meyering may have referring to some political GNU policy of not > wanting to support SunOS 4 as an official porting target (again, > Jim Meyering gave no reason for why SunOS 4 became irrelevant > in 2007). I'm not aware of any general GNU policy for or against supporting old systems (but I am not necessarily in the loop for such things). However, I trust Jim Meyering not to make such statements lightly. (I would have put SunOS 4's irrelevance date considerably earlier, tbh.) Enough about this, but I do have a related question which is more on-topic for this list: Do the various OBJECT_free() functions *defined by libssl and libcrypto* make the same promise to be a no-op when called on a NULL pointer? zw ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
