>>>>> "Wolfgang" == Wolfgang Jenkner <wjenkner@inode.at> writes:
Wolfgang> Raymond Toy <toy@rtp.ericsson.se> writes:
>>
>> Perhaps, then, we should check for the existence of the lisp file
>> before we overwrite it? If it exists, we'll either (1) ask the user if he
>> wants to overwrite it or (2) just return an error saying it already
>> exists. Choose one.
Wolfgang> I guess the example I gave of having two related but different files
Wolfgang> foo.LISP and foo.lisp was a bit whimsical and therefore misleading,
Wolfgang> sorry.
Wolfgang> What I really wanted to point out is that substituting .lisp for .LISP
Wolfgang> gives something which is nicer to look at but, on the other hand, we
Wolfgang> lose some information (i.e., this lisp code is generated) and maybe
Wolfgang> some flexibility.
Ok, but this is a problem for Windows where foo.lisp and foo.LISP are the
same file, even though they are listed with different case.
I think we should either always overwrite the file or ask the user if
he wants to overwrite it. (Returning an error is a pain, when you've
modified the mac file and are compiling it again.)
I'm leaning towards just overwriting the file without question, as we
do today. No one complains when gcc -c foo.c wipes out that foo.o
file that I really wanted. :-)
Ray