> as long as, when > __builtin_special_null_keyword_that_is_specific_to_my_compiler is > converted to a pointer type, it becomes a null pointer.
And, if converted to integer type, it becomes 0. Right; I was certainly talking about standard integer/pointer types, without compiler magic, which must be 0, not any other value. Thing is, even the special compiler keyword is *indistinguishable* from 0, except for type checking rules. > GCC uses such an implementation defined constant to allow additional > warnings when NULL is used in a non-pointer context (i.e. int i = 0;). And also, I believe, to finesse away type conflicts in C++. -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
