Summary

csc can delete files specified on the command-line

Metadata

Description

The follow commands:

 touch a.scm b.c
 csc -o b a.scm b.c

will delete the file b.c.

I expected, running the above, that the executable b would be created (or any errors in doing so to be reported.) Instead one finds the input file has been deleted.

Minimally I consider this anti-social, maximally I lost a file I'd invested a lot of time writing. :-(

Can a warning, error, or workaround be added to csc so it does not delete input files specified on the command-line?

Changes and comments

[2012-11-05 20:47:08 UTC] felix changed status from new to assigned

[2012-11-05 20:47:08 UTC] felix set owner to felix

[2012-11-18 21:20:13 UTC] sjamaan changed status from assigned to closed

[2012-11-18 21:20:13 UTC] sjamaan set resolution to fixed

[2012-11-18 21:20:13 UTC] sjamaan wrote:

Fixed by 0b0fcb6

[2012-11-20 16:19:04 UTC] alanpost wrote:

Confirmed fixed. Thank you everyone for your feedback and effort.