15 ms·
Creating three files named file.c, File.c, and FILE.c seems like being user hostile for the sake of being user hostile. Even for people using a case sensitive f
by tedunangst 12y ago
Creating three files named file.c, File.c, and FILE.c seems like being user hostile for the sake of being user hostile. Even for people using a case sensitive filesystem, it's a dick move. Imagine talking about your project over the phone. "Yeah, the problem is in file.c. No, not File.c, file.c. Idiot! I clearly said file.c, not FILE.c!"
- gchpaco 12y agoYeah, I don't think that's a reasonable thing to do even if you can do it.
- jacquesm 12y agoI've seen both Makefile and makefile in one archive.
- tedunangst 12y agoWhich is pretty ridiculous. Convention dictates that people use Makefile so that's the file people read and edit, yet the make utility reads makefile first by default. Including both is a great way to confuse users.
- jacquesm 12y agoYep. It definitely had that effect on me :)