Re: Class won't allocate
Re: Class won't allocate
- Subject: Re: Class won't allocate
- From: email@hidden
- Date: Mon, 12 Jun 2006 07:53:04 +0200 (CEST)
- Importance: Normal
>
>
> There must be something you're not telling us, something that's
> specific for this project / class. If you create a new project and
> define a subclass to NSObject, I'm sure that you will be able to
> allocate instances of that class. So, what is the difference between
> this particular project / class, and such a sample project. If you
> figure that out, you probably have the solution to your problem. I
> don't think that anyone here can help you further, at least not
> without more information.
>
> j o a r
>
>
>
>Turn off ZeroLink, then fix the link errors that appear, and you
>should be set. (And for best results, leave ZL off, and turn it off
>reflexively whenever you make a new project.)
>
>Mike
I just found out an old post in the Cocoa archive
(http://lists.apple.com/archives/cocoa-dev/2004/Mar/msg01765.html)
which was exactly what I was looking for. I first browsed the archive
with the keywords "alloc problem" and nothing of interest to me appeared
in the first 10 results. Later I tried "alloc nil" and found the
abovementioned
post.
I'll keep your advice in mind about ZeroLink. If I understood
correctly, the
problem appeared because of ZeroLink and because the files PrimesRecord.h&.m
were created in a different project and added later, and Xcode forgot to
update
the targets for those files. Although I copy files from one project to
another
often, it is the first time I have come across this one. Xcode's behaviour
looks
rather erratic on this ...
Thanks to you both anyway.
Ewan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden