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
      link
      fedilink
      367 months ago

      THEREareWORSEwaysTOtypeTHINGSandSTILLhaveTHEMbeKINDofREADABLE.whoNEEDSspacesWHENweHAVEtwoLETTERcases?

      OrMaYbEwEcOuLdEsChEwEvEnThAtAnDjUsTaLtErNaTe.IfThErEaReWrItInGsYsTeMsWiThOuTvOwElsThAtCaNsTiLlBeReAdWhYnOtWrItElIkEtHiSiNsTeAd?

    • TurboWafflz
      link
      fedilink
      157 months ago

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

    • JoYoOP
      link
      fedilink
      English
      87 months ago

      ofcyfpos() #posix

      GetWittyReplyExA() #msvc

      • JoYoOP
        link
        fedilink
        English
        77 months ago

        man 2 ofcyfpos

        The “f” stands for fuck.

        • @sjmulder@lemmy.sdf.org
          link
          fedilink
          4
          edit-2
          7 months 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
        link
        fedilink
        57 months 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!

        • JoYoOP
          link
          fedilink
          English
          57 months 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
            link
            fedilink
            2
            edit-2
            7 months 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.

            • JoYoOP
              link
              fedilink
              English
              27 months 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.

  • katy ✨
    link
    57 months ago

    capital letters should be abolished