What is the difference among nil, NULL, Nil in Objective-C?



They are all zeros, the difference lies in their types
-> The NSNull class defines a singleton object used to represent null values in collection objects (which don’t allow nil values). {NSNull is a class for objects that represent null.}
(https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSNull_Class/Reference/Reference.html#//apple_ref/occ/cl/NSNull)
-> nil is an id. So its points to a non-existent objective-c object
-> Nil is a non-existent objective-c class
-> [NSNull null] is an object that’s meant to stand in for nil in situations where nil isn’t allowed. For example, you can’t have a nil value in an NSArray. So if you need to represent a “nil”, you can use [NSNull null]
Also there is no ‘null’ in the objective c its ‘NULL’ not ‘null’. ‘null’ exist in Java or in C# not in Objective-C

nil -> Null-pointer to objective- c object
NIL -> Null-pointer to objective- c class

null-> null value for C pointer.

NSNUll -> Singleton object used to represent null.



NSNull     [NSNull null]     singleton object used to represent null
nil is the literal null value for Objective-C objects, corresponding to the abstract type id or any Objective-C type declared via @interface. For instance:
NSString *someString = nil;
NSURL *someURL = nil;
id someObject = nil;

if (anotherObject == nil) // do something
Nil is the literal null value for Objective-C classes, corresponding to the type Class. Since most code doesn’t need variables to reference classes, its use is not common. One example is:
 Class someClass = Nil;
 Class anotherClass = [NSString class];
Link (http://stackoverflow.com/questions/9578748/iphone-difference-between-nil-vs-nil-and-true-vs-true)

Comments

Post a Comment

Popular posts from this blog

Launch iPhone simulator without Xcode.

To launch simulator you have to way. 1. Using Terminal 2. Using UI. 1 Using UI. ->    Open Finder and then press   shift +  cmnd + g   or Go -> Go to Folder then enter this address /Applications/ Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications the double click on simulator.app. 2 Using Terminal  Open terminal and then press this command open / Applications / Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app or open `xcode-select --print-path` / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app To run application follow this, http://cocoamanifest.net/articles/2011/12/running-your-ios-app-in-the-simulator-from-the-command-line.html
Read more

How to Make REST api call in Objective-C.

We can call using this. NSString * twitterUrl = @ "YourUrlString" ; NSString * resp = [ self makeRestAPICall : twitterUrl ]; and method is -( NSString *) makeRestAPICall : ( NSString *) reqURLStr { NSURLRequest * Request = [ NSURLRequest requestWithURL :[ NSURL URLWithString : reqURLStr ]]; NSURLResponse * resp = nil ; NSError * error = nil ; NSData * response = [ NSURLConnection sendSynchronousRequest : Request returningResponse : & resp error : & error ]; NSString * responseString = [[ NSString alloc ] initWithData : response encoding : NSUTF8StringEncoding ]; NSLog (@ "%@" , responseString ); return responseString ; } 1 2 3 4 @ interface ViewController : UIViewController < NSURLConnectionDelegate > {      NSMutableData * _responseData ; }
Read more

id vs NSObject

There's often confusion about the difference between the following three declarations in Objective-C: id foo1; ->   It simply declares a pointer to some Objective-C object,  If you don't want (or can't have) any type checking, then use   id . if you do want compile-time type checking, you must decide between the second and third cases.. NSObject *foo2; ->  declaring a generic pointer of type NSObject* id<NSObject> foo3; ->   pointer to  any  object that behaves like an NSObjec , "foo3 is a pointer to an object of any type that behaves like an NSObject" , ( you really don't care what class the object is, you only care that it  behaves  like an NSObject.) The first one is the most common. It simply declares a pointer to some Objective-C object (see  /usr/include/objc/objc.h ).  id  gives the compiler no information about the actual type of the object, so the compiler cannot do compile-time type ...
Read more