Paul Sheer, 2008-01-29: > "it's own data"?? - well this is exactly why I asked on this > list :-) I wanted to get a better I idea about what "it's own > data" actually means. I am growing toward a complete list > of "it's own data" that does not appear to have any chance > of races. > > The fact that yee-all aren't sure what "it's own data" precisely > means makes me a bit worried!!! :-)
Why worry about this? The fact that I'm not sure (sic) about my own claim won't change *anything* about your lousy implementation. It's still relying on undocumented behavior. I think I've already made my point. I've been in a similar position before, studied a similar problem, and proposed the fix that went committed, not including at least an additional bug introduced by a MySQL employee. If you want to hear advice from someone who's been in your shoes, then please do spend some time and figure out whether your high energy approach would make any difference to your app. > > IMHO, your approach is clearly wrong: your app's fate > > is relying on undocumented behavior. It could "work" with > > a few OpenSSL library versions; but internal, sentitive > > behavior could change in future versions. Hence, I don't > > consider this a good engineering practice. > > My approach is certainly wrong by definition. > > It practice, for the OpenSSL source tree I am using, > it is 100% working. Yes, you are right - future versions > could break everything. Good to hear this. Leandro ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
