Re: Protocol doesn't seem to compile?
Re: Protocol doesn't seem to compile?
- Subject: Re: Protocol doesn't seem to compile?
- From: Chris Hanson <email@hidden>
- Date: Sat, 28 Feb 2004 17:22:16 -0500
On Feb 27, 2004, at 9:35 AM, Jason Vowell wrote:
There is no need to write code to test protocols or "interfaces" they
are
designed and they can be used to present a design for someone else to
implement...
There is very definitely a need to test protocols or interfaces. How
do you know they contain what you want and that you can do what you
need to with them?
I've said this before in a number of places and I'll say it again: Test
Driven Development works and works well In this case, before even
writing the protocol definition you'd write some failing tests that
check whether an object implements it and so on. So you'd wind up
having the protocol compiled and used by a class.
This is not to excuse any gaps in the compiler or other such issues.
But there is an easy way to cover for them, one most everyone should be
doing as much as possible anyway.
-- Chris
--
Chris Hanson <email@hidden>
bDistributed.com, Inc.
Outsourcing Vendor Evaluation
Custom Mac OS X Development
Cocoa Developer Training
_______________________________________________
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.