Date: Mon, 2 Jun 1997 08:34:38 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: bcc vs cc/gcc (float) Message-ID: <19970602083438.EW54555@uriah.heep.sax.de> In-Reply-To: <199706020036.UAA18558@lakes.water.net>; from Thomas David Rivers on Jun 1, 1997 20:36:41 -0400 References: <199706020036.UAA18558@lakes.water.net>
next in thread | previous in thread | raw e-mail | index | archive | help
As Thomas David Rivers wrote: > > > I don't see a declaration for environ in our /usr/include/ files. > > > Shouldn't it be there? > > > > Posix doesn't specify any (which I think was a mistake), but it would > > be nice to have it as an extension. > I don't think you can do this; because it would violate the user's > name space. You can bracket it in #ifndef _POSIX_SOURCE etc. As it stands now, we do already provide every binary with `environ', so it would be a mistake for a user program to reuse this name as a global. With the proper declaration in unistd.h, you at least give the innocent programmer a hint that this name actually _is_ already in use. It's not that it would get into use by just declaring it, it's always there since crt0 defines it. I don't even think it's a weak symbol, but i might be mistaken in this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970602083438.EW54555>