argh. stupid windows headers and how they hide definitions from you unless you remember to define WINVER/_WIN32_WINNT

I DON'T LIKE THIS DESIGN DECISION

when I look up FooBarA() and MSDN says it's in winfoo.h, I assume that I need to do just #include <winfoo.h> for it to work.

that's how C headers work basically everywhere else, after all

BUT NO, FooBarA() is only defined if you set _WIN32_WINNT to at least 0x500 because it isn't defined until Windows 2000

Follow

@foone We have that on unix / linux too. _DEFAULT_SOURCE, _GNU_SOURCE, _BSD_SOURCE, etc.

Just one example. Want the BYTE_ORDER‎ macro the POSIX standard says has to be in endian.h, but you use glibc? Define one of the magic macros! Also, that's not POSIX requiring it, and the man page doesn't even mention the existence of the BYTE_ORDER‎ macro!

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!