Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!paperboy!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Must main return a value?
Message-ID: <16588@smoke.brl.mil>
Date: 30 Jun 91 12:41:43 GMT
References: <12049.Jun2922.08.1391@kramden.acf.nyu.edu> <16587@smoke.brl.mil> <16020.Jun3004.44.3491@kramden.acf.nyu.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 7

In article <16020.Jun3004.44.3491@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>Hold on. You're saying something about the real world here, and the real
>world doesn't distinguish between ``implementation-defined'' and
>``undefined'' until a standard comes along and forces the issue.

Sure it does.  If it core dumps, it's undefined, and if it's documented
in the long shelf of vendor literature, it's implementation-defined.