[comp.lang.c] does the ansi spec say anything about cc

rosenkra@hall.cray.com (Bill Rosenkranz) (08/30/89)

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).

-bill
rosenkra@boston.cray.com

gwyn@smoke.BRL.MIL (Doug Gwyn) (09/01/89)

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.

henry@utzoo.uucp (Henry Spencer) (09/06/89)

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"...

There may well be C implementations on machines like the Mac, designed for
illiterates, in which there is no notion of a "command line" or a "file
name" at all.
-- 
V7 /bin/mail source: 554 lines.|     Henry Spencer at U of Toronto Zoology
1989 X.400 specs: 2200+ pages. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu

bill@twwells.com (T. William Wells) (09/08/89)

In article <1989Sep5.225807.1486@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
: 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"...
:
: There may well be C implementations on machines like the Mac, designed for
: illiterates, in which there is no notion of a "command line" or a "file
: name" at all.

Not "may well be". Are. And this caused us real headaches since our
normal way of shipping code had our customers configure it by using
-D.... or the equivalent.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill@twwells.com