Date: Sat, 17 May 2003 17:39:18 +0100 From: Jonathan Belson <jon@witchspace.com> To: Erik Trulsson <ertr1013@student.uu.se> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: pornview-0.2.0.p.1 Message-ID: <3EC665B6.5040102@witchspace.com> In-Reply-To: <20030517155457.GA94423@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> <3EC6439F.5020700@witchspace.com> <20030517155457.GA94423@falcon.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
rik Trulsson wrote: > With that definition of stdin/stdout/stderr the code in pornview > happens to work. I suspect that code wasn't tested on anything except > Linux. Not uncommon, unfortunately. > A bit of Googling leads me to believe that they were required to be > macros in C89 as well, even though many implementations didn't define > them that way. > Unfortunately I don't have a copy of the original ANSI C standard so I > can't check what it says there. I couldn't see any reference to stdin/stdout/stderr other than the one I quoted you. > I don't think "lovely" is a word I will ever use to describe anything > involving #undef. "Ugly" is the word that comes to mind when thinking > about any situation that would require the use of #undef. Um, I was being sarcastic. >>I'll contact the author and explain the situation, someone else can >>look at/commit the patch you posted. Done. --Jon http://www.witchspace.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EC665B6.5040102>