Programmer Humor

24948 readers

1776 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

[email protected]

366

Why make it complicated? (lemmynsfw.com)

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

120 comments fedilink hide all child comments

Made with KolourPaint and screenshots from Kate (with the GitHub theme).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

any new keyword could break backwards compatibility

Wouldn't that happen anyway with variable and function names? Any type other than primitive/built in ones are usually camel case so lower case keywords are more likely to clash with single word variable and function names, unless you restrict the cases of those too or allow keyword overriding or something.

[–] [email protected] 3 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Yeah, it's in my edit I realized the same thing. I'm thinking it doesn't actually really make sense and the real reason is more "the specific way C does it causes a lot of problems so we're not poking syntax like that with a 10 foot pole" + "it makes writing the parser easier" + maybe a bit of "it makes grepping easier"

[–] [email protected] 1 points 2 weeks ago* (last edited 2 weeks ago)

One thing that annoyed me about C# as a Java guy is that it really wants you to use camel case for function and property names, even private ones. I don't like it specifically because it's hard to differentiate between a function/property and a type.

But C# has quite a few keywords and seem to like adding them more than Java.

Maybe that's their way of ensuring keywords don't clash with stuff?