Date: Sat, 17 May 2003 15:13:51 +0100 From: Jonathan Belson <jon@witchspace.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: FreeBSD Port: pornview-0.2.0.p.1 Message-ID: <3EC6439F.5020700@witchspace.com> In-Reply-To: <20030517135217.GA88537@falcon.midgard.homeip.net> References: <3EC53C6C.1040904@witchspace.com> <20030517121908.GA67369@rot13.obsecurity.org> <3EC62CC2.6090209@witchspace.com> <20030517130549.GA44928@falcon.midgard.homeip.net> <3EC63B78.6010203@witchspace.com> <20030517135217.GA88537@falcon.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Erik Trulsson wrote: >>From (a draft version of) the C99 standard: <snip> Aha, I didn't realise you were talking about ISO C - I still think in ANSI most of the time (being old enough to have studied K&R at university). > Besides, the only way I can think of to have stdin/stdout/stderr > available as expressions but not #define them is to have them as just > plain variables, and if that was the only option available I am sure > the standards committee would have written that. So even with the wording > you give they *could* be macros, but might not necessarily have been. Presumably they usually were in ANSI C, but not in ISO C (as required). > Not explicitly no, but if the pornview code was OK there wouldn't have > been many other options left. Apart from my lovely #undef solution :-) I'll contact the author and explain the situation, someone else can look at/commit the patch you posted. --Jon http://www.witchspace.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EC6439F.5020700>