Date: Fri, 29 May 1998 19:47:14 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: mike@smith.net.au (Mike Smith) Cc: wollman@khavrinen.lcs.mit.edu, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Argh! errno spam! Message-ID: <199805291947.MAA29647@usr07.primenet.com> In-Reply-To: <199805272034.NAA01753@dingo.cdrom.com> from "Mike Smith" at May 27, 98 01:34:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > Any C program which has a structure member called `errno' is > > erroneous. > > How so? Structure members have been allowed to be non-unique for a > while now; I don't recall there being constraints on globals vs. > structure members at all. > > There are a few perfectly good reasons to call a structure member errno, > but regardless of the good reasons, I fear for the code in the ports > collection. 8( > > I was bitten by this with the NetBSD-derived bootcode I'm working on, > which doesn't use libc and thus needs its own errno in order to be a > reasonable facsimile therof. (Yes, I have a workaround.) Any code which does not use libc, has a structure member called `errno', and still includes errno.h... is erroneous. 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?199805291947.MAA29647>