29 Aug
2006
29 Aug
'06
10:48 p.m.
> To return to the original question, how far back
do you have to go
> for unix's cc(1) to require .c on C source files, .o on object files
> (to be linked it), and so on?
Well, cc is usually a wrapper; if you break it down and run the stages
manually, I don't know of any version which enforces any extensions.
Not very far. [...gcc example...]
gcc (a) is a driver wrapper and (b) has options (which you conveniently
didn't mention) to explicitly specify what kind of input and output you
want it to work with, overriding the defaults (which are based on file
names).
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B