RE: Protocol doesn't seem to compile? (SOLVED)
RE: Protocol doesn't seem to compile? (SOLVED)
- Subject: RE: Protocol doesn't seem to compile? (SOLVED)
- From: "Jason Vowell" <email@hidden>
- Date: Fri, 27 Feb 2004 10:31:58 -0600
That is very helpful. I can just declare them in a .h file and include the
in an empty .m file and even take the opportunity to test them in the .m
file if need be (as suggested previously).
Thanks for everyone's help. Sorry for that blockage in my head.
-----Original Message-----
From: email@hidden
[
mailto:email@hidden] On Behalf Of Sherm Pendley
Sent: Friday, February 27, 2004 9:54 AM
To: Jason Vowell
Cc: email@hidden
Subject: Re: Protocol doesn't seem to compile? (SOLVED)
On Feb 27, 2004, at 10:21 AM, Jason Vowell wrote:
>
So if one were wanting to do something like what I was describing..
>
just
>
writing protocols for someone else to implement.. these protocols
>
would need
>
to be writing inside a .m files so that the make file that Xcode writes
>
would actually look for them.
You need to leave your protocols in .h files - how else would someone
else be able to include them?
Use #import to include the declarations found in the .h files, just
like any user of your protocol would do.
And yes, the whole deal with header files can be a PITA at first, if
you've got a Java background. Doing away with that sort of thing is one
of the few things Java got right, IMHO.
sherm--
_______________________________________________
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.
_______________________________________________
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.