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.

    • palordrolap@kbin.social
      37·
      1 year ago

      THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?

      OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?

        • Neshura@bookwormstory.socialEnglish
          5·
          1 year ago

          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·
            1 year ago

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

      • milicent_bystandr@lemm.ee
        2·
        1 year 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.

      • Hazzard@lemm.ee
        2·
        1 year 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.

        • sjmulder@lemmy.sdf.org
          4·
          1 year ago

          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.

      • sjmulder@lemmy.sdf.org
        5·
        1 year ago

        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!

        • JoYo 🇺🇸OPEnglish
          5·
          1 year ago

          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·
            1 year ago

            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.

            • JoYo 🇺🇸OPEnglish
              2·
              1 year ago

              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.