On 7/31/05 1:46 PM, John Stiles didst favor us with:
If I were writing the framework/universal headers, that would have been
my choice.
And for the purist/pedantic among us, you could always do something
along the lines of
#if _cplusplus
const CFAllocatorRef kCFAllocatorDefault = NULL;
#else
#define kMyCFAllocatorDefault NULL
If I were going to use a macro, I'd define it like this:
#define kMyCFAllocatorDefault ((CFAllocatorRef)NULL)
This way you can't accidentally pass kMyCFAllocatorDefault in a parameter
that doesn't take a CFAllocatorRef. I know that's not likely to happen here,
but I'm a big advocate of consistently using good, defensive programming
practices as opposed to saying "Well, in *this* case I can just do [some
shortcut]."
