@marcoarment I’ll call it something’s wrong because -x is executed twice.
-
-
-
@CocoaClimber It’s not. -
@marcoarment If the object (self) is created inside the nib it will. Try: https://files.app.net/dzq9TudC
-
-
-
@marcoarment -commonInit. And you may want to consider -initWithCoder: instead of -awakeFromNib: - View other replies
-
@drance@marcoarment static void InitFoo(Foo *self). You get accidental overrides with -initCommon. - View other replies
-
@kongtomorrow@drance@marcoarment Ken’s correct. - Show more
-
-
@marcoarment commonInit I like to keep the name reminiscent of init while avoiding potentially confusing adj like shared, combined, main -
-
@marcoarment -commonInit. (-initCommon not correct since it's technically not the allocator, per naming guidelines) - View other replies
-
@marcoarment perhaps use -stupidNotDRY because we have to write the many boilerplates calling it in -init*, -awakeFrom*, all the + ctors.
-
-
-
@marcoarment Two hours have passed and no one has given the obvious answer. Q: What do you call x? A: Ten - Show more
-
-
-
@marcoarment “_commonInit” due to https://gist.github.com/tjw/910308 -
@pgor@marcoarment Having ‘x’ as a method is going to cause you nightmares if you ever subclass.
-
-
@marcoarment -(void)setupAllTheThings™ -
@marcoarment@ismh@caseyliss It's the joke that just keeps giving. -
@marcoarment commonInit -
-
@marcoarment@VTPG setup or ClassName_setup depending on likelihood of name collision -
@heathborders@marcoarment@Zalambar When I retweeted that, I meant it to be attached to https://twitter.com/kongtomorrow/status/420276701130534912 … not a question.
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Marco Arment
Joaquín Durand
Matt Drance
Ken Ferry
Andy Matuschak
Stephen Hackett
David Smith
Nat Brown
Dr. Drang
Paul Goracke
Flo Gehring
Bryan Irace
Heath Borders
Vincent Gable