On Jun 9, 2015, at 13:40 , Jens Alfke <[email protected]> wrote:
>
> - (instancetype) initWithString: (NSString*)str NS_DESIGNATED_INITIALIZER;
I think the issue is that declaring your initializer “designated” causes the
compiler to enforce different inheritance semantics
> - (instancetype) init {
> @throw [NSException exceptionWithName: NSInternalInconsistencyException
> reason: @"Flump cannot be initialized with
> -init"
> userInfo: nil];
> }
>
> But this didn’t fix it.
Try:
> - (instancetype) init NS_DESIGNATED_INITIALIZER {
Unfortunately, search at developer.apple.com <http://developer.apple.com/>
seems to be broken since they changed the site yesterday, so I can’t easily
look for documentation about this.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com
This email sent to [email protected]
