From owner-freebsd-current@FreeBSD.ORG Sun May 4 12:24:50 2003 Return-Path: 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 130F337B401 for ; Sun, 4 May 2003 12:24:50 -0700 (PDT) Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9999D43FA3 for ; Sun, 4 May 2003 12:24:49 -0700 (PDT) (envelope-from mike@espresso.bsdmike.org) Received: by espresso.bsdmike.org (Postfix, from userid 1002) id 038389C84; Sun, 4 May 2003 15:09:41 -0400 (EDT) Date: Sun, 4 May 2003 15:09:41 -0400 From: Mike Barcroft To: Alexander Kabaev Message-ID: <20030504150940.D55150@espresso.bsdmike.org> References: <1052068880.617.9.camel@pav.oook.cz> <20030504145210.74ea557d.kabaev@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030504145210.74ea557d.kabaev@mail.ru>; from kabaev@mail.ru on Sun, May 04, 2003 at 02:52:10PM -0400 Organization: The FreeBSD Project cc: freebsd-current@freebsd.org cc: Pav Lucistnik Subject: Re: same define in two header files X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2003 19:24:50 -0000 Alexander Kabaev writes: > On 04 May 2003 19:21:21 +0200 > Pav Lucistnik wrote: > > Maybe there are stalled header files in /usr/include, how can I found > > which one? I can't rely on timestamps like with binaries. > > > No, this was a pollution I incorrectly propagated from non-i386 > platforms. I will commit a fix shortly. I guess this means you're going to remove DBL_* and FLT_*? If so, I agree there's no reason why we should define duplicate constants in a non-standard location. Also, the namespace check for LONG_BIT and WORD_BIT is very dated and forgets about any standards written in the last decade or so. A more appropriate check would be #ifndef __BSD_VISIBLE (after including ). Best regards, Mike Barcroft