From owner-freebsd-standards@FreeBSD.ORG Wed Jun 8 16:41:49 2005 Return-Path: X-Original-To: standards@freebsd.org Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23B0216A41C for ; Wed, 8 Jun 2005 16:41:49 +0000 (GMT) (envelope-from stefan@fafoe.narf.at) Received: from fafoe.narf.at (chello213047085026.6.14.vie.surfer.at [213.47.85.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B737243D48 for ; Wed, 8 Jun 2005 16:41:48 +0000 (GMT) (envelope-from stefan@fafoe.narf.at) Received: from wombat.fafoe.narf.at (wombat.fafoe.narf.at [192.168.1.42]) by fafoe.narf.at (Postfix) with ESMTP id 86E483FA7; Wed, 8 Jun 2005 18:41:41 +0200 (CEST) Received: by wombat.fafoe.narf.at (Postfix, from userid 1001) id D9ECD2DD; Wed, 8 Jun 2005 18:41:38 +0200 (CEST) Date: Wed, 8 Jun 2005 18:41:38 +0200 From: Stefan Farfeleder To: Michael Reifenberger Message-ID: <20050608164134.GC17962@wombat.fafoe.narf.at> Mail-Followup-To: Michael Reifenberger , standards@freebsd.org References: <20050608094851.D29843@fw.reifenberger.com> <20050608103045.GC16848@wombat.fafoe.narf.at> <20050608124306.X30581@fw.reifenberger.com> <20050608125416.GA17962@wombat.fafoe.narf.at> <20050608152614.H31265@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050608152614.H31265@fw.reifenberger.com> User-Agent: Mutt/1.5.9i Cc: standards@freebsd.org Subject: Re: libstand functions not ansi-c compiliant X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 16:41:49 -0000 On Wed, Jun 08, 2005 at 03:32:09PM +0200, Michael Reifenberger wrote: > On Wed, 8 Jun 2005, Stefan Farfeleder wrote: > > > >On Wed, Jun 08, 2005 at 12:52:42PM +0200, Michael Reifenberger wrote: > >> > >>The advantage would be (thats how I got to this issue at all) that > >>you don't get compiling errors when including too. > >>(I had to do this to get the definition of FILE for the work > >>on upgrading sys/boot/ficl to ficl4) > > > >I'd consider including from sys/boot/ficl a bug. > > > > Maybe. Thats debatable. > But by default ficl.h (coming with ficl4)does inslude > and ficl4 says about itself: ...Ficl is written in strict ANSI C... > Unfortunately is part of ANSI-C... > So one cant blame ficl4 for that. No, but a boot loader is not a hosted implementation. Ficl needs to be patched to use our I/O functions. Stefan