this post was submitted on 02 Oct 2023
1379 points (96.7% liked)

Programmer Humor

19623 readers
26 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 58 points 1 year ago (1 children)

This is a feature, not a bug

[–] [email protected] 30 points 1 year ago (2 children)

Right? I rather not have a computer automatically autocorrect.

[–] [email protected] 6 points 1 year ago

Yeah, and I think most shells will correct this case by pressing tab

[–] [email protected] 3 points 1 year ago (2 children)

Also, I constantly name files in the same directory the same thing except for case. In my ~/tmp directory I have unrelated foo.c (C source) and foo.C (C++ source).

[–] [email protected] 4 points 1 year ago
[–] [email protected] 2 points 1 year ago (1 children)

Why not .cpp for C++? I don’t use C++, but I thought that was the standard.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

.C came first. I don't usually use it though; I usually use .cc or .cxx, but if I'm making some tiny test source, I often use .C. I'm strongly opposed to the .cpp extension because calling C++ "CPP" leads to confusion with the preexisting (before C++) use of the initialism to refer to the C preprocessor. There's a reason why CPPFLAGS refers to preprocessor flags and CXXFLAGS refers to C++ flags.

[–] [email protected] 1 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago

But then the filename wouldn't be /^[[:alnum:]._-]*~*$/.