Date: Thu, 07 Nov 2002 14:52:25 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: jdp@polstra.com Cc: current@freebsd.org Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021107.145225.104187142.imp@bsdimp.com> In-Reply-To: <200211071926.gA7JQ5i3065752@vashon.polstra.com> References: <200211071640.gA7GeWJk065460@vashon.polstra.com> <20021107.104251.110765870.imp@bsdimp.com> <200211071926.gA7JQ5i3065752@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200211071926.gA7JQ5i3065752@vashon.polstra.com>
John Polstra <jdp@polstra.com> writes:
: In article <20021107.104251.110765870.imp@bsdimp.com>,
: M. Warner Losh <imp@bsdimp.com> wrote:
: > In message: <200211071640.gA7GeWJk065460@vashon.polstra.com>
: > John Polstra <jdp@polstra.com> writes:
: >
: > : FWIW, the only OS fix that will make stock ezm3/pm3/CVSup buildable on
: > : -current is to make __sF global again and arrange for:
: > :
: > : stdin == &__sF[0]
: > : stdout == &__sF[1]
: > : stderr == &__sF[2]
: >
: > Why does cvsup need this to be the case? Now you have me curious.
:
: It's not CVSup, it's Modula-3. It thinks it knows that stdin,
: stdout, and stderr are defined as above, but they're not any more.
: Because Modula-3 isn't C and doesn't use C header files, it cannot
: automatically track such changes like C programs do.
Gotcha. I'm thinking very seriously about keeping __sF support (but
creating no new binaries with it in it) and the freeze on sizeof(FILE)
through the 5.x series of releases because we botched the
compatibility stuff so badly to give people a chance to catch their
breaths before that reorg can happen.
Warner
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?20021107.145225.104187142.imp>