3 ms·
This is because the Windows filesystems (in backwards compatibility with DOS) are not case sensitive, so the compiler doesn't distinguish between .C and .c
by andai 6y ago
This is because the Windows filesystems (in backwards compatibility with DOS) are not case sensitive, so the compiler doesn't distinguish between .C and .c
- Someone 6y agoNowadays, 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.