Date: Sat, 17 May 2003 14:39:04 +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: <3EC63B78.6010203@witchspace.com> In-Reply-To: <20030517130549.GA44928@falcon.midgard.homeip.net> References: <3EC53C6C.1040904@witchspace.com> <20030517121908.GA67369@rot13.obsecurity.org> <3EC62CC2.6090209@witchspace.com> <20030517130549.GA44928@falcon.midgard.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Erik Trulsson wrote: > That part of the structure is not the problem. The next part of this > structure is the problem. > > gchar stdout[GTK_MPLAYER_BUF_SIZE]; > gint stdout_size; > gchar stderr[GTK_MPLAYER_BUF_SIZE]; > gint stderr_size; True. > Not legitimate. The C standard itself says that stdin/stdout/stderr are > supposed to be macros and therefore this behaviour is expected Interesting...do you have a reference for this? Section 7.9.1 of the ANSI C spec says that stdin/stdout/stderr are expressions of type 'pointer to FILE', I can't see anything that says they're supposed to be macros. > The bug is in the application, not in FreeBSD, so, unfair or not, it > isn't FreeBSD that should be changed. I don't remember anyone stating that FreeBSD should be changed... --Jon http://www.witchspace.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EC63B78.6010203>