Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: Strange lint mumblings
Message-ID: <225800103@uxe.cso.uiuc.edu>
Date: 30 Dec 88 15:31:00 GMT
References: <416@marob.MASA.COM>
Lines: 19
Nf-ID: #R:marob.MASA.COM:416:uxe.cso.uiuc.edu:225800103:000:832
Nf-From: uxe.cso.uiuc.edu!mcdonald    Dec 30 09:31:00 1988



>In what the dpANS calls a hosted environment---that is, in all the
>interesting cases; in freestanding environments like a Unix kernel,
>one generally cannot exit at all---return(expr) from main and
>exit(expr) have identical effects.  

There are, in the PC world, cases of non-hosted environments that are
relatively common - programs run under Microsoft Windows and the
OS/2 presentation manager are non-hosted environments. They don't
have main() at all. No argv and argc. And many of the standard library
routines don't work (getc and putc are missing, for example). I think
that they are certainly "interesting". Sickening, but interesting.

Doug McDonald

P.S. Inside a MS Windows program, it would be possible to write the
various subroutines and call a "main" in the usual way. For some
odd reason they haven't done it.