采用NS_DESIGNATED_INITIALIZER
是很好在http://useyourloaf.com/blog/2014/08/19/xcode-6-objective-c-modernization.html解释:
The designated initializer guarantees the object is fully initialised by sending an initialization message to the superclass. The implementation detail becomes important to a user of the class when they subclass it. The rules for designated initializers in detail:
- A designated initializer must call (via super) a designated initializer of the superclass. Where NSObject is the superclass this is just [super init].
- Any convenience initializer must call another initializer in the class - which eventually leads to a designated initializer.
- A class with designated initializers must implement all of the designated initializers of the superclass.
作为一个例子,如果接口是
@interface MyClass : NSObject
@property(copy, nonatomic) NSString *name;
-(instancetype)initWithName:(NSString *)name NS_DESIGNATED_INITIALIZER;
-(instancetype)init;
@end
则编译器检查是否(便利)初始化init
调用 的(指定)初始化程序initWithName:
,所以这会引起警告:
-(instancetype)init
{
self = [super init];
return self;
}
,这将是确定:
-(instancetype)init
{
self = [self initWithName:@""];
return self;
}
在斯威夫特的有关规定确定的和方便的初始化是更严格, 如果你混的Objective-C和斯威夫特代码,标志着指定目标-C初始化器帮助编译器执行规则。
例如,这斯威夫特子类会导致编译器错误:
class SwClass: MyClass {
var foo : String
init(foo : String) {
self.foo = foo
super.init()
}
}
,这将是确定:
class SwClass: MyClass {
var foo : String
init(foo : String) {
self.foo = foo
super.init(name: "")
}
}
Objective-C中的概念并不是很好的想法,因为'initWithName:@“”'在进行子类化时并不总是有意义的。相反,通常从超类中重写的指定初始化器应该抛出异常,说使用来自子类的指定初始化器。 – Andy 2015-10-18 15:47:23
要添加到Martin的答案,您可能想要完全禁止用户调用默认的初始化程序,在这种情况下,您可以使用以下内容: - (instancetype)init NS_UNAVAILABLE; – 2016-02-18 16:21:28