Casing of Constants in the C1X Standard

[wswartzendruber]

I'm looking at the current draft of the C1X standard. Here's an excerpt from the threading section:

[username234]

The obvious answer is that thrd_success, thrd_nomem, and thrd_error are enum constants instead of macros, so to maintain consistency in the standard they shouldn't be capitalized. Now, why they're enum constants as opposed to macros, I can't say. Hopefully, they'll post a C1X Standard rationale that explains it.
_________________
Creating usernames when you're
in a creative slump is a bad idea
because if you are when you do
then you end up with uninspiring
alphanumeric cocktails like the
one directly above.

[wswartzendruber]

I found this, but no explanation as to why. It seems that there are about two macros (uppercase) in the threading portion of C1X and about twenty enums.

[Hu]

I cannot speak for why they chose enums in this case, but the most common argument that I see in support of using enums is that macros are expanded by the preprocessor, which leads to less readable error messages if you misuse them, and that macros require extra work to make the values type safe. You usually want an error if you compare a foo_result to a bar_success, since foo and bar may have different numeric values for what constitutes "success." Using simple macros, those might be defined as integers, and the compiler would silently allow you to make a mistake. If you use an enum, you can do:

[username234]

That does remind me that you can do something like

[wswartzendruber]

Perhaps thread.h functions return different values depending on the underlying API (pthreads, etc...)?