On Thu, Jul 10, 2008 at 11:52 AM, Graham Cox <[EMAIL PROTECTED]> wrote: > Actually it doesn't emit a warning. > > If you recall my problem a few weeks ago with: > > - (float) position; > > vs. > > - (int) position; > > the compiler sailed blithely on without a mention, generating code that > smashed the stack to pieces. > > This is different from the situation that does emit a warning, where the > method is completely unknown and is assumed to return type 'id'. I do > compile with many additional warnings, but I haven't found one that picks up > this problem.
Some experimentation reveals that the compiler is "merely" extremely inconsistent about when it warns. For example, int and void warns, float and void warns, but float and int does not. Double and int warns, double and float warns, but int and id does not. I can't find any particular pattern to it, but it's clear that it's a bug, not a deliberate omission. I recommend you file a bug with Apple. Mike _______________________________________________ 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 [EMAIL PROTECTED]
