On Jan 14, 2014, at 4:37 PM, Jordan Rose <[email protected]> wrote:
> > On Jan 14, 2014, at 16:33 , jahanian <[email protected]> wrote: > >> >> On Jan 14, 2014, at 4:18 PM, Jordan Rose <[email protected]> wrote: >> >>> The problem isn't that it's unimplemented, it's that it's undeclared. And >>> @selector isn't really an operator. How about "no methods visible for >>> selector %0" or "no methods declared for selector %0 in this translation >>> unit”? >> >> Warning is for when a method is declared but no implementation of it is seen >> in the translation unit. I am not sure what you mean >> by an "undeclared method”? Do you consider a method declared in an >> @interface but its implementation (or definition) is not >> in the current TU, an ‘undeclared method’? > > Oops, sorry. I thought this was a much more useful warning than it actually > is. >< I still think "using @selector on method" is the wrong phrasing, > though. "no method with selector %0 implemented in this translation unit”? In r199278. - Fariborz >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
