Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: does the ansi spec say anything about cc(1)
Keywords: ANSI cc
Message-ID: <10895@smoke.BRL.MIL>
Date: 31 Aug 89 22:43:30 GMT
References: <4544@hall.cray.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <4544@hall.cray.com> rosenkra@hall.UUCP (Bill Rosenkranz) writes:
>like "standard" commandline switches, output file names, etc. seems like
>this could be interpreted as "part of the language"...(it would certainly
>make some Makefiles more portable).

It's nice, I suppose, to find somebody who is convinced that only UNIX
matters.  However, the proposed ANSI standard for programming language
C is not limited to the UNIX environment.  Therefore it logically cannot
talk about "cc", Makefiles, etc.

IEEE 1003.2, on the other hand, IS in a position to try to constrain
UNIX-like environments' use of "cc" etc.  I'm not sure they can say
anything that will really help, though, since different environments
will still require their own special options, and "cc -O -c" etc. are
pretty standard among UNIX environments already.