3 ms·
Nowadays, they’re case-preserving, so the compiler _could_ distinguish the two. Historically, though, lowercase character weren’t allowed in file names (even t
by Someone 6y ago
Nowadays, they’re case-preserving, so the compiler _could_ distinguish the two.
Historically, though, lowercase character weren’t allowed in file names (even though the on-disk format would have allowed it), so compilers couldn’t make the distinction. Given that using “.C” has fallen out of fashion (if it ever was fashionable), I don’t see much pressure to add that functionality, especially given that it might break compilation of C source code copied over from old times that uses .C.
- karatinversion 6y agoI've had similar fun on macOS, where IIRC the project had both an API.h and an api.h file.