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.

      • 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.