Date: Fri, 29 May 1998 21:22:43 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: joelh@gnu.org Cc: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Message-ID: <199805292122.OAA15162@usr04.primenet.com> In-Reply-To: <199805282024.PAA01692@detlev.UUCP> from "Joel Ray Holveck" at May 28, 98 03:24:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm not discussing what should be, I'm discussing what is. We have a > good percentage of software from the Linux camps, and many of their > software authors wouldn't know a non-portable construct if it walked > up and introduced itself in assembly code. If the plan is to "make it work anyway", how do you propose the common Linux programming error where they fail to zero sockarr_in contents before partially filling in values and using them? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805292122.OAA15162>