There are certain commands I've come across that
handles extentions
poorly. Like gunzip:
[spc]lucy:/tmp>mv x-grey.tar.gz x-grey.tar.foo
[spc]lucy:/tmp>gunzip x-grey.tar.foo
gunzip: x-grey.tar.foo: unknown suffix -- ignored
[spc]lucy:/tmp>
Yes. Annoying, but understandable - without the .gz on there, how is
it to know what file to put the result in? Of course, we could get
into the upsides and downsides of filesystem version numbers, but
that's a separate bikeshed. (Workaround, moderately specific to gzip,
and good for only a single file: gunzip < x-grey.tar.foo > whatever)
And GCC also has trouble with extentions:
[spc]lucy:/tmp>cp hello.c hello.foo
[spc]lucy:/tmp>gcc hello.foo
hello.foo: file not recognized: File format not recognized
collect2: ld returned 1 exit status
[spc]lucy:/tmp>gcc hello.c
[spc]lucy:/tmp>
Yes. Read the documentation. gcc has options to specify what's in a
file; the guesses based on .c, .s, .i, etc are just heuristics,
overridable with the appropriate options. (At least in the version of
gcc whose documentation I was reading when I stumbled across that; I
don't know how ubiquitous it is.)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at
rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B