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.
27 Comments
xmunk@sh.itjust.works · 51 pts · 2y
iAmHappyToOblige
ifYouNeedAnythingElseDoNotHesitateToAsk
palordrolap@kbin.social · 36 pts · 2y
THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?
OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?
Infynis@midwest.social · 23 pts · 2y
Damn, that second one was tough. I didn't expect to find the word 'eschew' lol
neshura@bookwormstory.social · 5 pts · 2y
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.
xmunk@sh.itjust.works · 4 pts · 2y
If you go back in time far enough you can find manuscripts from before word separators were standard... they fucking suck.
driving_crooner@lemmy.eco.br · 7 pts · 2y
SQL programmers be like:
owenfromcanada@lemmy.world · 5 pts · 2y
Get your SpongeBob-ass casing outta here
gribodyr@lemmy.ml · 2 pts · 2y
Is this like BaSeSixTYfOuR?
milicent_bystandr@lemm.ee · 2 pts · 2y
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.
Hazzard@lemm.ee · 2 pts · 2y
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.
turbowafflz@lemmy.world · 16 pts · 2y
TheyDidn't_say-AnythingAbout-commentsSo+this%20iSprobablYfinEiwoulDsaY
JoYo@lemmy.ml · 8 pts · 2y
ofcyfpos()#posixGetWittyReplyExA()#msvcJoYo@lemmy.ml · 7 pts · 2y
man 2 ofcyfpossjmulder@lemmy.sdf.org · 4 pts · 2y
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 officialofcyfpos()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#definethe problem away.JoYo@lemmy.ml · 3 pts · 2y
UCRT makes me so hard.
sjmulder@lemmy.sdf.org · 5 pts · 2y
Don't forget to set the
cbSizeof theGETWITTYREPLYEXINFOstructure before passing it toGetWittyReplyEx()or you'll get funny things happening to your stack!JoYo@lemmy.ml · 5 pts · 2y
You didn't specify wide or ascii, we're all doomed.
I'm glad to to meet another Knight of 9x.
sjmulder@lemmy.sdf.org · 2 pts · 2y
That's handled by virtue of
GetWittyReplyExbeing#defined toGetWittyReplyExAandGetWittyReplyExWright? Just be aware thatnMaxReplyMessageneeds to be specified in bytes (excluding the null terminator!) but the returned length is in characters.JoYo@lemmy.ml · 2 pts · 2y
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
#definethat will save you from that. I may or may not have been that junior dev so no shade.cashews_best_nut@lemmy.world · 1 pts · 2y
NERD!
Balthazar@lemmy.world · 26 pts · 2y
You're_very_welcome.
driving_crooner@lemmy.eco.br · 26 pts · 2y
> unexpected character error on [You']
LostXOR@kbin.social · 10 pts · 2y
you_are_very_welcome
Balthazar@lemmy.world · 14 pts · 2y
Looks like OP is using a form of Hungarian notation in the post title...
idegenszavak@sh.itjust.works · 10 pts · 2y
imabigfanofidontfuckingcare. youreadthecode, itsyourproblemnow.
FiskFisk33@startrek.website · 7 pts · 2y
I-Prefer-Kebamel-Case
cupcakezealot@lemmy.blahaj.zone · 5 pts · 2y
capital letters should be abolished