On Mon, 29 Nov 2010 12:39:52 -0800, David Duncan <david.dun...@apple.com> said: >Objective-C is a dynamic enough language that it cannot fully check for >conformance at compile time (which is why the message above is a warning and >not an error). Technically you don't even need to conform to the protocol, you >can just implement the methods and go, but implementing the protocol allows >for error checking by the compiler but only when the compiler can actually >see the protocol declarations in the first place (which is not the case above).
Still, the OP has a point. If everything in a protocol is optional, then (1) why should the compiler care whether we formally adopt the protocol or not, and (2) what sort of "error checking" could the compiler do? In other words I'm suggesting that there should be no warning unless the protocol has required methods. m. -- matt neuburg, phd = m...@tidbits.com, <http://www.apeth.net/matt/> A fool + a tool + an autorelease pool = cool! AppleScript: the Definitive Guide - Second Edition! http://www.apeth.net/matt/default.html#applescriptthings_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
