For trivial apps, no-one cares. But most libraries take huge advantage of the concept of “subclassing”, and programmers using those libraries need to make intelligent choices about “which subclass do I use?”.<\/p>\n
Thanks to auto-complete, or “because it sounded what I needed at that moment in time” – or simply “because I was tired” – your base class gets instantiated when it shouldn’t have been. And strange bugs come from it, wasting everyone’s time. You might argue “not MY time”, but I’m a strong believer in writing code that EITHER does the obvious OR protects the people using it – my code doesn’t crash, it checks for obvious mistakes (e.g. checks that a file exists before loading it!), etc.<\/p>\n
In the long run, that frequently comes back to help you: when YOU then re-use your own code, and make a dumb mistake because it’s been a long time and you’d forgotten how to use it.<\/p>\n
In some languages, you can create “abstract base classes” that allow other classes to share type, but cannot be used on their own. This makes it obvious to other programmers that they should look for subclasses and pick one – instead of trying to use the superclass.<\/p>\n
Unfortunately, ObjectiveC has no support for “abstract classes”.<\/p>\n
…or does it?<\/p>\n
An abstract class is one that cannot be instantiated. To achieve that in Objective-C, all you have to do is:<\/p>\n
\r\n@implementation DontAllowInit\r\n\r\n- (id)init\r\n{\r\n NSAssert(false, @\"You cannot init this class directly. Instead, use a \r\nsubclass e.g. AcceptableSubclass\");\r\n\r\n \/\/ NB: I prefer to use NSAssert because this is aimed at programmers, and \r\n \/\/ ObjC programmers should generally be using assertions during dev!\r\n \r\n \/\/ You could instead use more fancy approaches, like raising an NSException\r\n \/\/ - but Apple\/Cocoa are very anti-exception, and don't support them well.\r\n\r\n return nil;\r\n}\r\n@end\r\n<\/pre>\n…but this causes a problem. Because as soon as someone creates a subclass, they’ll find their code crashes:<\/p>\n
\r\n@interface SubClass : DontAllowInit\r\n@end\r\n\r\n@implementation SubClass\r\n\r\n- (id)init\r\n{\r\n self = [super init]; \/\/ CRASH!\r\n if( self != nil )\r\n {\r\n \/\/ all the normal setup code\r\n }\r\n return self;\r\n}\r\n@end\r\n<\/pre>\nYou can workaround this by writing documentation that says:<\/p>\n
\n\/*
\nThis class can’t be instantiated, because I wanted an Abstract Class, but Objective-C was too primitive to allow it.<\/p>\n
So, um, please don’t call [super init]. Instead call … ah .. [super secretInit] which does the same thing, but which other people won’t realise exists!
\n*\/\n<\/p><\/blockquote>\n
There’s an obvious problem there … the super-secret-init is easy to call anyway, and BOOM your library. It might seem obvious to you that no-one would call that method without understanding it, but this is the way of the world.<\/p>\n
Selective Denial: what am I?<\/h3>\n
The solution is to think about what happens when you instantiate a subclass. The key thing here is that when you call:<\/p>\n
\r\nSuper* s = [[Super alloc] init];\r\n<\/pre>\nit’s NOT the same as when you call:<\/p>\n
\r\nSub* s = [[Sub alloc] init];\r\n<\/pre>\n…in the first case, the thing that gets sent “init” is an instance of “Super”, whereas in the second case it’s an instance of “Sub”.<\/p>\n
That might not sound interesting, but when Sub executes the first (standards-compliant) line of its init method:<\/p>\n
The key thing here is that when you call:<\/p>\n
\r\n-(id) init\r\n{\r\n self = [super init];\r\n<\/pre>\n…then the code in Super.m is *not* being run on an object of type “Super”, but rather an object of type “Sub”.<\/p>\n
And so we have a solution:<\/p>\n
\r\n@implementation DontAllowInit\r\n- (id)init\r\n{\r\n\tif( [self class] == [DontAllowInit class])\r\n\t{\r\n\t\tNSAssert(false, @\"You cannot init this class directly. Instead, use a subclass e.g. MyPreferredSubclass\");\r\n\t\t\r\n\t\treturn nil;\r\n\t}\r\n\telse\r\n\t\treturn [super init];\r\n}\r\n<\/pre>\nDoes it really matter?<\/h3>\n
When writing code, you have lots to think about. In my years of experience, two of the most important questions are:<\/p>\n
\n- Does it do what it says \/ work as intended?\n
- Can someone else use (and modify) the code later, when you’re not there … correctly?\n<\/ol>\n
Documentation goes a long way to solving both those issues. However … docs take a long time to write, and more importantly:<\/p>\n
\nOther people frequently don’t read the documentation\n<\/p><\/blockquote>\n
More importantly:<\/p>\n
\nIf you are a great programmer, other programmers SHOULD NOT NEED TO read the code documentation any more than they expected to\n<\/p><\/blockquote>\n
“Expected to” is critical here. If your codebase is 1 million lines long, then a programmer would be insane to think they could just “dive in” and start writing \/ modifying it – the thing is fantastically complex. But if it’s clear and simple, then often they should expect to read the “core” documentation, and be able to work the rest out as they go, from reading your class and method names.<\/p>\n
Abstract classes enable you – with very little effort – to use complex chains of OOP subclassing without endangering the programmers who come after you<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"Abstract classes: saving programmers from each other For trivial apps, no-one cares. But most libraries take huge advantage of the concept of “subclassing”, and programmers using those libraries need to make intelligent choices about “which subclass do I use?”. Thanks to auto-complete, or “because it sounded what I needed at that moment in time” – […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"_links":{"self":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/2102"}],"collection":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/comments?post=2102"}],"version-history":[{"count":0,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/2102\/revisions"}],"wp:attachment":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/media?parent=2102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/categories?post=2102"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/tags?post=2102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}