site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=breaqz.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= breaqz.com; bh=XCrTYYRQSfPFYjkj9SdipGHzS5g=; b=ILGRgpPKTfgeuzcAb C0hHVzGVcjHEAWRz8AnQ/tAIyOwPmR3mQnTG9H4NnPElyzeTMbGD4HVBc/93pMNO RInFU+UVy/cWroNpihhstyctkNoPPkwgA4uX8O2p1brKKC53srloYcOQ7SmTFs12 088RlmOtULad1w2F0ivI/b26dg=
On Aug 8, 2017, at 2:15 PM, Uli Kusterer <witness.of.teachtext@gmx.net> wrote:
On 8. Aug 2017, at 18:38, Doug Hill <cocoadev@breaqz.com> wrote:
As others have mentioned, I too have never seen any evidence or statements from Apple that discourages +new or -init. Or designated initializers.
I never said anything about init or designated initializers. In fact, ObjC gained support for marking designated initializers fairly recently.
I was responding to a lot of different issues in my email, not necessarily just yours. My apologies if it came off that way. But, that said, designated initializers have been in the Objective-C Programming Guide from Apple since at least 2003 (the earliest version of the document I can find). And this pattern probably originated in the NeXT days. What are the recent developments in designated initializers? Doug Hill _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com