On May 1, 2009, at 11:32 AM, Jeremy Pereira wrote:
On 30 Apr 2009, at 17:16, Dave DeLong wrote:
(Except protocols, which I don't know of a way to forward declare)
@protocol MyProtocol ;
Oh, well, that would make sense. =)
Thanks!
Dave
___
Co
On 30 Apr 2009, at 17:16, Dave DeLong wrote:
Hi Andre,
#import means that the compiler will only include the file once,
thus eliminating re-declaration errors. It does not, however,
eliminate the problems introduced by circular dependencies (which is
what you've got going here).
As a
Ah, that makes sense. I knew the @class thing was working, but it was
so annoying to never know if the method call was correct or not.
Adding the .h files to the respective .m files fixed the issue though.
Thanks so much!
Andre
On 30-Apr-09, at 11:07 AM, Sherm Pendley wrote:
On Thu, Apr 30,
On Thu, Apr 30, 2009 at 2:55 AM, Andre Doucette <
andre.eckythump.douce...@gmail.com> wrote:
It seems that it doesn't like the double #import, but I thought the whole
> idea behind #import was that it ensured one-time includes.
#import guards against multiple includes, but not circular includes.
Hi Andre,
#import means that the compiler will only include the file once, thus
eliminating re-declaration errors. It does not, however, eliminate
the problems introduced by circular dependencies (which is what you've
got going here).
As a general rule, the only thing you should be #impo
Hi everyone!
I have noticed a problem in a few projects and don't understand why. I
have found a work around, but it seems both unnecessary and a pain due
to warnings.
For one example, I have two classes, AppController and
NetworkController.
For the AppController class:
