On Dec 1, 2010, at 7:41 AM, Matt Neuburg wrote:
> 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 sugges
On Mon, 29 Nov 2010 12:39:52 -0800, David Duncan 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
On Nov 29, 2010, at 12:31 PM, David Rowland wrote:
> When I build, I get a warning,
>
> type 'id ' does not conform to the
> 'UIAccelerometerDelegate' protocol
Whatever is being referred to on the line you are getting this warning is only
typed as "id" so the compiler doesn't know that the
ob
I have a class defined like this,
@interface GAppDelegate : NSObject {
and inside that class I have implemented this,
// UIAccelerometerDelegate method, called when the device accelerates.
- (void)accelerometer:(UIAccelerometer *)accelerometer
didAccelerate:(UIAcceleration *)acceleration;
