Re: Conflicting Namespaces on the Language Level
Re: Conflicting Namespaces on the Language Level
- Subject: Re: Conflicting Namespaces on the Language Level
- From: Ondra Cada <email@hidden>
- Date: Sun, 6 Oct 2002 15:57:22 +0200
On Friday, October 4, 2002, at 11:21 , email@hidden wrote:
(Do not place "[super init]" in a method implementation that is in a
subclass of an abstract superclass).
I fear you just found a workaround, not a fix. There is nothing like
abstract classes in ObjC; you can use some of them so, but the compiler
knows nothing of that.
[super init]
was the culprit, since it was calling upon an abstract class I suppose
(though I don't see how it would affect an entirely different line of
code at compile time).
Strange. I must have missed the start of this thread, so I don't know how
the offending code looked, but to my knowledge you can freely use [super
init] anywhere (in any method), so far as *compiler* can say.
With the deletion of this line of code (from each offending init...
function), the problem was fixed.
On the other hand -- not a compiler matter, but a library one -- there
should be just *one* init in a class which contains a [super init] (the
designated initalizer).
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.