FROM : G Douglas Davidson
DATE : Thu Oct 24 23:36:58 2002
If I import the file, do I also have to link in the code with those
selectors? I should have mentioned that this is something I'm doing in
bundles. I'm using a framework for most of the stuff, but there are
some things that I really want to be loose, hence the "id".
Thanks!
On Thursday, October 24, 2002, at 05:32 PM, David Remahl wrote:
>> Is there any way to use type "id" and not get two compiler warnings
>> per
>> usage?
>>
>> 1. warning: cannot find method
>> 2. warning: return type for "whatever:" defaults to id
>>
>> There are some times where I don't want or can't easily use static
>> typing, and it would be really nice if the compiler could say "Hey,
>> its
>> type 'id', that means he does not want warnings about methods (which
>> would be impossible anyway) and warnings about return types (which
>> would also be impossible.)" Ideally I'd like the compiler to check on
>> the static stuff and not on the type "id" stuff.
>>
>> Is this possible?
>
> Import the file where the selector is defined. Messages to id are
> checked
> against all the selectors the compiler knows of, collected from all
> classes,
> categories and protocols.
>
> / Rgds, David
>
>
--
G. Douglas Davidson | CityNet, Inc.
<email_removed> | Pittsburgh, PA
voice: 412.481.5406 | fax: 412.431.1315
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Thu Oct 24 23:36:58 2002
If I import the file, do I also have to link in the code with those
selectors? I should have mentioned that this is something I'm doing in
bundles. I'm using a framework for most of the stuff, but there are
some things that I really want to be loose, hence the "id".
Thanks!
On Thursday, October 24, 2002, at 05:32 PM, David Remahl wrote:
>> Is there any way to use type "id" and not get two compiler warnings
>> per
>> usage?
>>
>> 1. warning: cannot find method
>> 2. warning: return type for "whatever:" defaults to id
>>
>> There are some times where I don't want or can't easily use static
>> typing, and it would be really nice if the compiler could say "Hey,
>> its
>> type 'id', that means he does not want warnings about methods (which
>> would be impossible anyway) and warnings about return types (which
>> would also be impossible.)" Ideally I'd like the compiler to check on
>> the static stuff and not on the type "id" stuff.
>>
>> Is this possible?
>
> Import the file where the selector is defined. Messages to id are
> checked
> against all the selectors the compiler knows of, collected from all
> classes,
> categories and protocols.
>
> / Rgds, David
>
>
--
G. Douglas Davidson | CityNet, Inc.
<email_removed> | Pittsburgh, PA
voice: 412.481.5406 | fax: 412.431.1315
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| G Douglas Davidson | Oct 24, 23:20 | |
| David Remahl | Oct 24, 23:32 | |
| G Douglas Davidson | Oct 24, 23:36 | |
| Greg Titus | Oct 24, 23:40 | |
| Ondra Cada | Oct 25, 00:05 | |
| Kirk Kerekes | Oct 26, 18:53 | |
| matt neuburg | Oct 28, 21:22 |






Cocoa mail archive

