nsobject

Before I start, I have already read the Swift documentation. I am still trying to comprehend what AnyObject actually is. Is it a base class for all objects/classes in Swift, as NSObject is in Objective C? If I create an array of type [AnyObject] and populate it with Movie class instances, that would mean that AnyObject is a base class of the Movie class right? let someObjects: [AnyObject] = [ Movie(name: "2001: A Space Odyssey", director: "Stanley Kubrick"), Movie(name: "Moon", director: "Duncan Jones"), Movie(name: "Alien", director: "Ridley Scott") ] This should be true or else you wouldn't

If you define a swift class like this @objc class Cat { } In swift you can just do var c = Cat() But how do you make a Cat instance in Objective-C ? Subclassing NSObject works because you can then "alloc-init" but can we achieve this without subclassing an Objective-C class? The most direct way is to subclass Cat from NSObject . If you can't do that, you will need to make a class method or a function that returns a Cat . @objc class Cat { class func create() -> Cat { return Cat() } } func CreateCat() -> Cat { return Cat() } Cat *cat = [Cat create]; Cat *cat = CreateCat(); In modern objective-c

I'm emotionally attached to my C++ class, but I really want it to go into a tableview. Is there a way to subclass NSObject from a standard c++ class? this is what I tried to do: class Model : NSObject { public: NSString *key; }; The compiler did not like it one bit. It tells me the the base specifier must be a class. Is there any kind of sneaky thing I can do? Should I just make it a standard objective C++ object? You cannot mix inheritance between C++ and Objective-C classes. Instead, just make a standard Objective-C++ object which wraps your C++ object. Teach the Obj-C object how to pass

for example, I have NSString *myClass = @"RootViewController" How do I get class from NSString? Try this id obj= [[NSClassFromString(@"RootViewController") alloc] init]; You can use Class class = NSClassFromString(@"RootViewController"); NSClassFromString Obtains a class by name. Class NSClassFromString ( NSString *aClassName ); Parameters aClassName The name of a class. Return Value The class object named by aClassName, or nil if no class by that name is currently loaded. If aClassName is nil, returns nil. Availability Available in iOS 2.0 and later. There is a lot of methods like this in

Typically when I subclass from a UI class I will call the superclass initializer of interest. However, I'm not sure of the implementation details of NSObject , and it seems like there's not much going on in terms of member vars, so I wonder: do I need to call [super init] if my subclass extends NSObject ? John Calsbeek Technically, no. The documentation for -[NSObject init] says that The init method defined in the NSObject class does no initialization; it simply returns self . Because it is documented and there's probably already a bunch of code that relies on it, that fact is highly unlikely

I'm building an iOS app in Swift and drawing on the Lister sample project Apple provides. Lister uses two model objects: List and ListItem. I found that both of them do not call super.init() in their initializers even though they subclass NSObject. However, in the Objective-C version of Lister, both model objects (AAPLList and AAPLListItem) do call [super init] . The Swift Programming Language clearly states that “designated initializers must call a designated initializer from their immediate superclass.” (Rule 1 of Initializer Chaining in Initialization) What's going on here? Why is this an