Re: Cocoa and dead-code stripping
Re: Cocoa and dead-code stripping
- Subject: Re: Cocoa and dead-code stripping
- From: Chris Suter <email@hidden>
- Date: Mon, 2 Jul 2007 12:41:26 +1000
So it sounds like, if I want to end up with reasonably-sized code,
that I should create just the classes (and methods) that I need for
a particular task. When I want to do something similar, it sounds
like I should copy the class sources into another target, add some
methods, etc., and then compile/link that version?
Is code bloat a problem for you? The approach you suggest doesn't
sound very maintainable to me. How much unused code are you talking
about and what problem are you trying to fix by keeping it down?
By the way, this is the same as for Carbon/C++ since as far as I
know, the OS X linker doesn't support function level linking.
Actually in that case the linker generally knows who's calling what
and can strip out the unused methods and classes. From what I've
seen, gcc still has some issues with this, but at least a lot of
stuff -is- stripped out...
Yes, I'm sure you saw my subsequent e-mail.
- Chris
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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