Re: Cocoa and dead-code stripping
Re: Cocoa and dead-code stripping
- Subject: Re: Cocoa and dead-code stripping
- From: "Clark Cox" <email@hidden>
- Date: Tue, 3 Jul 2007 07:50:20 -0700
On 7/2/07, Andrew Demkin <email@hidden> wrote:
On Jul 2, 2007, at 8:28 PM, Wade Tregaskis wrote:
>> The way this would work is to have the development tools scan all
>> message selector references (and class literal references) and
>> strip all methods and classes that aren't referenced. This process
>> would repeat until the tool can no longer perform any more stripping.
>
> O rly?
>
> .h
> IBOutlet id myTextField;
>
> .m
> NSString *selectorName = [myTextField stringValue];
> SEL newSelector = NSSelectorFromString(selectorName);
> [myObject performSelector:newSelector];
Yes, this is exactly the sort of example which I tried to cover in my
original posting when I said,
Of course, there's still the probability that some references
won't be known at compile-time, and for these methods and classes,
a tagging technique would be necessary to suppress the stripping.
Tagging would not work, as *any* method can be called dynamically at
runtime. You'd have to tag every single method--which would defeat the
purpose.
--
Clark S. Cox III
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden