Today I found a remove_bad_files.sh script lying around a project and I was very puzzled because I couldn't recall writing such script or ever using it. It took me a while to realize that trying out dead_code_analyzer might've something to do with it.
I think dead_code_analyzer shouldn't blindly be (over)writing a file remove_bad_files.sh in the current directory. It should perhaps just print the commands to stdout for the user to copy and maybe offer a command line option (off by default) which actually writes them to remove_bad_files.sh.
And even for the latter, it would've been very helpful if the script had a comment along the lines of "generated by dead_code_analyzer".
Today I found a
remove_bad_files.shscript lying around a project and I was very puzzled because I couldn't recall writing such script or ever using it. It took me a while to realize that trying out dead_code_analyzer might've something to do with it.I think dead_code_analyzer shouldn't blindly be (over)writing a file
remove_bad_files.shin the current directory. It should perhaps just print the commands to stdout for the user to copy and maybe offer a command line option (off by default) which actually writes them toremove_bad_files.sh.And even for the latter, it would've been very helpful if the script had a comment along the lines of "generated by dead_code_analyzer".