Subject: Re: exit() undefined in bootloader build
To: None <M.Drochner@fz-juelich.de>
From: Gary Thorpe <gat7634@hotmail.com>
List: tech-kern
Date: 06/01/2002 16:06:21
>From: Matthias Drochner <M.Drochner@fz-juelich.de>
>Reply-To: M.Drochner@fz-juelich.de
>To: Jun-ichiro itojun Hagino <itojun@iijlab.net>
>CC: port-i386@netbsd.org, tech-kern@netbsd.org
>Subject: Re: exit() undefined in bootloader build
>Date: Sat, 01 Jun 2002 14:00:05 +0200
>
>itojun@iijlab.net said:
> > or, is it more proper? (exit() with no arg)
> > anyways, arch/i386/stand uses exit() inconsistently.
>
>It depends on the environment - a normal bootloader has
>nothing to report status to, as opposed to the DOS loader
>where the exit code makes sense.
>After all, we also have a "void main(void)" in some bootloaders,
>so I don't see a necessity to be dogmatic here.
>
>best regards
>Matthias
I am surprised the ANSI/ISO standard bearers on the lists did not die of
rage when this was posted. Could some of those holding copies of the
standard and so willing to quote it please comment on "void main(void)"???
As far as I know, main is ALWAYS required to return int in ANSI C. Has this
changed with the latest drafts of the ISO and/or ANSI standards?
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.