Re: NSClassFormString returning nil.
Re: NSClassFormString returning nil.
- Subject: Re: NSClassFormString returning nil.
- From: Quincey Morris <email@hidden>
- Date: Wed, 04 May 2011 11:10:10 -0700
On May 4, 2011, at 10:19, Kyle Sluder wrote:
> Static ObjC libraries are still very useful on iOS, because you can't
> load code dynamically. It's just so much easier and faster to split
> our apps up into seven or eight static libraries rather than our old
> method of compiling all the source into one binary at the same time.
> Since we reuse frameworks on the desktop and on iOS, this is a much
> more natural solution.
iOS? Just a fad. No need to get excited about it.
;)
On May 4, 2011, at 10:31, Gustavo Pizano wrote:
> I need to use the a library because its a iOS project so no framework, and also because I will be reusing the code in the lib for many other apps not just this one Im making..
I think you missed my point. You can reuse the *source code* in all the apps, simply by dropping it into your Xcode projects much the same way you would otherwise drop a static library in.
Kyle makes a good point, though (which I meant to say in my previous post but forgot). If there are multiple developers working on multiple projects, it may be convenient for housekeeping reasons to package shared code as libraries.
If you're in a less complicated working environment (I note that Kyle says "we" but you say "I"), then the advantages aren't as clear.
_______________________________________________
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