[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re:  File names mangled for MS-DOS
- To: <michael@son-of-blob>, <us@son-of-blob>
 
- Subject: Re:  File names mangled for MS-DOS
 
- From: <eric@son-of-blob>
 
- Date: Sat, 9 Sep 89 17:11:01 PDT
 
>From michael Sat Sep  9 17:05:33 1989
	From: michael (Michael McClary)
	To: eric, us
	Subject: Re:  File names mangled for MS-DOS
	
	> Old Name		New Name
	> .h			c.h
	> .c			c.c
	> .o			c.o
	> .hxx			c.hxx
	> .cxx			x.cxx
	> .o			x.o
	
	Shouldn't those last three be either
	
	  .hxx			x.hxx
	  .cxx			x.cxx
	  .o			x.o
	
	or
	
	  .hxx			c.hxx
	  .cxx			c.cxx
	  .o			c.o
	
	?  (BTW, I prefer the latter, but only slightly.  Is there some reason
	to mark .o files with their origin as c++ source?  We should never have
	both a Foo.c and a Foo.cxx, because some c++ compiler systems may produce
	a temporary Foo.c file in the directory containing the Foo.cxx.)
	
		michael
	
The reason for the x.o vs. c.o name ends is that we did not want to have any
unmarked cases.