this post was submitted on 11 Dec 2023

102 points (96.4% liked)

Programmer Humor

32479 readers

348 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

102

[meta] thanks for not camel casing your post titles (lemmy.ml)

submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]

27 comments fedilink hide all child comments

I wasn’t sure how to express my gratitude.

It wasn’t bad for the occasional topical jest but holy shit does it make reading feeds painful.

Edit: in no way am I making a statement about code syntax. We don't write documentation in camel case for good reason.

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

[–] [email protected] 53 points 11 months ago (3 children)

iAmHappyToOblige

ifYouNeedAnythingElseDoNotHesitateToAsk

[–] [email protected] 36 points 11 months ago (6 children)

THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?

OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?

[–] [email protected] 22 points 11 months ago (1 children)

Damn, that second one was tough. I didn't expect to find the word 'eschew' lol

[–] [email protected] 5 points 11 months ago (1 children)

I had to constantly skip back and forth to figure out where one word starts and another ends. Very painful to read, I've found new appreciation for whitespace.

[–] [email protected] 4 points 11 months ago

If you go back in time far enough you can find manuscripts from before word separators were standard... they fucking suck.

[–] [email protected] 7 points 11 months ago

SQL programmers be like:

[–] [email protected] 5 points 11 months ago

Get your SpongeBob-ass casing outta here

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago)

Is this like BaSeSixTYfOuR?

[–] [email protected] 2 points 11 months ago

I'm surprised how easy that is to read!

Sorry, am on mobile: snarkily replying in some weird letter mashup is far too much effort right now.

[–] [email protected] 2 points 11 months ago

Surprisingly legible, but feels like I can only read it with momentum, flitting past it and letting my subconscious tell me where the word breaks are. The moment I get confused and look more closely, it becomes almost impossible to read.

[–] [email protected] 15 points 11 months ago

TheyDidn't_say-AnythingAbout-commentsSo+this%20iSprobablYfinEiwoulDsaY

[–] [email protected] 8 points 11 months ago (2 children)

ofcyfpos() #posix

GetWittyReplyExA() #msvc

[–] [email protected] 7 points 11 months ago (1 children)

man 2 ofcyfpos

The "f" stands for fuck.

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

Note that while Visual C++'s msvcrt doesn't implement this POSIX function officially, there's a nonstandard _ofcyfpos_s() and it will in fact warn you that any use of the official ofcyfpos() is unsafe. The semantics are slightly different (it'll return 1 on success instead of the length of the reply) so you can't just #define the problem away.

[–] [email protected] 3 points 11 months ago

UCRT makes me so hard.

[–] [email protected] 5 points 11 months ago (1 children)

Don't forget to set the cbSize of the GETWITTYREPLYEXINFO structure before passing it to GetWittyReplyEx() or you'll get funny things happening to your stack!

[–] [email protected] 5 points 11 months ago (1 children)

You didn't specify wide or ascii, we're all doomed.

I'm glad to to meet another Knight of 9x.

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

That's handled by virtue of GetWittyReplyEx being #defined to GetWittyReplyExA and GetWittyReplyExW right? Just be aware that nMaxReplyMessage needs to be specified in bytes (excluding the null terminator!) but the returned length is in characters.

[–] [email protected] 2 points 11 months ago (1 children)

well hopefully that's how you're writing it.

i've definitely found the ascii version of a syscall being called because that's what the linux project uses so why wouldn't the junior dev that was assigned the port do it too?

there's no #define that will save you from that. I may or may not have been that junior dev so no shade.

[–] [email protected] 1 points 11 months ago

NERD!