Mail Archives: djgpp/2000/04/03/19:58:17
Hans-Bernhard Broeker wrote in message
<8caj5q$ii3$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>...
>> In the future, I will keep backups before I start invoking GCC
>> manually;
>
>I doubt that. Really. Forgetting to keep backups is even more like to
>happen accidentally than mistyping a gcc command line that badly.
I don't think I'll forget after that. Excuse me, but I normally rely on
RHIDE to do my compiling for me. It's not my fault if I get the filenames in
the wrong order and it starts writing the executable into the source file (I
presume that's what happened, but I don't know). I've rewritten the source,
and kept a backup, and written a batch file (I can't be bothered to read the
MAKE documentation) which creates the header as necessary and then compiles
the program. I seem to have got it right this time.
>> but I should point out to anyone concerned that GCC should
>> *not* have deleted a source file.
>
>Well --- you asked it to. Unix-borne tools like gcc are in the habit
>of doing exactly what you say, wherever possible. If you 'rm -rf /' on
>a Unix box as root, that's what it'll do.
Yes, but GCC is a compiler, not a deltree-equivalent!
Ben Davis
- Raw text -