From owner-freebsd-current Thu Nov 7 13:59:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25E7C37B401 for ; Thu, 7 Nov 2002 13:59:31 -0800 (PST) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B42B43E3B for ; Thu, 7 Nov 2002 13:59:30 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id gA7LxQx00232; Thu, 7 Nov 2002 13:59:26 -0800 (PST) (envelope-from jdp@vashon.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.12.5/8.12.5/Submit) id gA7LxPE9065991; Thu, 7 Nov 2002 13:59:25 -0800 (PST) (envelope-from jdp) Date: Thu, 7 Nov 2002 13:59:25 -0800 (PST) Message-Id: <200211072159.gA7LxPE9065991@vashon.polstra.com> To: current@freebsd.org From: John Polstra Cc: imp@bsdimp.com Subject: Re: [PATCH] note the __sF change in src/UPDATING In-Reply-To: <20021107.145225.104187142.imp@bsdimp.com> References: <200211071640.gA7GeWJk065460@vashon.polstra.com> <20021107.104251.110765870.imp@bsdimp.com> <200211071926.gA7JQ5i3065752@vashon.polstra.com> <20021107.145225.104187142.imp@bsdimp.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20021107.145225.104187142.imp@bsdimp.com>, M. Warner Losh wrote: > In message: <200211071926.gA7JQ5i3065752@vashon.polstra.com> > John Polstra writes: > : > : 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. I'm kind of on the fence about it. The point of hiding __sF is to remove all dependencies on the size of the FILE structure from applications, and that's a very worthwhile thing to do. Modula-3 is a special case (and a pathological one), and it shouldn't influence the decision too much. I don't think there's a way to fix it entirely in the OS without re-establishing the dependency on the size of FILE. We are lucky that ezm3 just happens to work. The PM3 port can be fixed with a 5.0-specific patch or two, but ... not today. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message