Re: Cocoa and dead-code stripping
Re: Cocoa and dead-code stripping
- Subject: Re: Cocoa and dead-code stripping
- From: Andrew Demkin <email@hidden>
- Date: Tue, 3 Jul 2007 11:26:04 -0700
On Jul 3, 2007, at 10:04 AM, Clark Cox wrote:
On 7/3/07, Andrew Demkin <email@hidden> wrote:
In this specific case, perhaps the best thing to do would be to
disable the hypothetical automatic stripping. So what? That doesn't
mean that stripping wouldn't work for more common cases.
The problem is that this specific case *is* the common case. You'd
have to disable this hypothetical automatic stripping for every Cocoa
program. In which case, what was the point in making such a stripping
program in the first place?
No, executing completely arbitrary message selectors (i.e. selectors
generated from unknown user input) is not the common case.
I've already mentioned that the practicality of stripping may not be
worth it. As Chris Hanson originally stated, framework-based
development (intrinsic to Cocoa) makes this less of an issue.
My only point here was to clarify that dynamic messaging isn't a deal-
breaker for automatic stripping. It can be made to work. Whether it
is useful is some cases or others is a separate matter.
This thread is way-off topic from Cocoa development, so I'll refrain
from any further posts on this issue :-)
Andrew
_______________________________________________
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