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.unix.questions
Subject: Re: s5last No Longer Dumps Core!
Message-ID: <16590@smoke.brl.mil>
Date: 30 Jun 91 12:55:44 GMT
References: <1991Jun28.005902.13061@mccc.edu> <16578@smoke.brl.mil> <1991Jun30.010604.8185@mccc.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 17

In article <1991Jun30.010604.8185@mccc.edu> pjh@mccc.edu (Pete Holsberg) writes:
>I don't understand how legitimate C code doesn't behave under this compiler
>or that unless the compilers are buggy.

Obviously not.

Only a perfectly portable program could be used to test compilers like this.
There are VERY few perfectly portable programs, even among those that were
intended to be.  The number of things that could go wrong are legion, but
since you asked for an example, here's just one on the thousands that I've
seen:

	int test(arg) int arg; {int ok; if(arg < 0) ok = 0; else ok = 1;}

This function works on some systems using some compilers but not others.
I leave it to you to figure out why (for both situations).  Please don't
post your guesses here!