From owner-freebsd-hackers@FreeBSD.ORG Fri May 30 22:38:48 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 051E937B401 for ; Fri, 30 May 2003 22:38:48 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C1643F93 for ; Fri, 30 May 2003 22:38:47 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4V5cPkA080926; Fri, 30 May 2003 23:38:26 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 30 May 2003 23:38:14 -0600 (MDT) Message-Id: <20030530.233814.39156877.imp@bsdimp.com> To: des@ofug.org From: "M. Warner Losh" In-Reply-To: References: <200305301727.06623.wes@softweyr.com> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: julian@elischer.org Subject: Re: gcc bug? Openoffice port impossibel to compile on 4.8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2003 05:38:48 -0000 In message: Dag-Erling Smorgrav writes: : Wes Peters writes: : > On Thursday 29 May 2003 00:12, Dag-Erling Smorgrav wrote: : > > May I remind you that K&R-style declarations have been deprecated for : > > the last 14 years? : > Funny, the last time I looked at a C language specification they were : > still supported. : : 6.11.5 Function definitions : : [#1] The use of function definitions with separate parameter : identifier and declaration lists (not prototype-format : parameter type and identifier declarators) is an obsolescent : feature. : : and "obsolescent feature" is defined as follows in the introduction: : : [#2] Certain features are obsolescent, which means that they : may be considered for withdrawal in future revisions of this : International Standard. They are retained because of their : widespread use, but their use in new implementations (for : implementation features) or new programs (for language : [6.11] or library features [7.26]) is discouraged. Deprecated doesn't mean they are no longer part of the standard. Just that next standard they could go away. Warner