Re: Why is NULL used sometimes when documentation specifies nil?
Re: Why is NULL used sometimes when documentation specifies nil?
- Subject: Re: Why is NULL used sometimes when documentation specifies nil?
- From: Roarke Lynch <email@hidden>
- Date: Fri, 14 Jan 2005 22:01:25 -0500
What is the difference between nil and NULL?
Why does the Foundation Reference for NSScanner specify nil to skip
search results, while the NSScanner example in "Strings"
documentation uses NULL to omit results?
[snip
So why is NULL used sometimes when documentation specifies nil?
Well nil is used to imply no object in Cocoa Objective-C and NULL for
traditional uses of NULL in C. In reality they are one in the same
value so they can be used interchangeably.
The code example, in a perfect world, should be using nil since
intoString is expecting an object.
-Shawn
Knowing that nil and NULL are essentially the same value, I was under
the impression that syntactically nil refers to "no object" while NULL
referrers to "a pointer to nothing", so in the the NSScanner method in
question since the argument is of type NSString** not NSString* NULL is
used because it is the second case.
Roarke Lynch
-------------------------------
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden