Date: Wed, 27 May 1998 13:34:17 -0700 From: Mike Smith <mike@smith.net.au> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Subject: Re: Argh! errno spam! Message-ID: <199805272034.NAA01753@dingo.cdrom.com> In-Reply-To: Your message of "Wed, 27 May 1998 17:29:53 EDT." <199805272129.RAA00108@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> <<On Wed, 27 May 1998 11:27:46 -0700, Mike Smith <mike@smith.net.au> said: > > > Just a grumble; the 'new' errno macro is a real pain for non-libc > > consumers, as well as anything that has a structure member called > > 'errno'. 8( > > 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.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199805272034.NAA01753>