Best way to make a code library?
Best way to make a code library?
- Subject: Best way to make a code library?
- From: Steven Frank <email@hidden>
- Date: Sun, 1 Dec 2002 21:58:09 -0800
Hi all,
We have a lot of code in our project that could be re-used in future
projects -- customized table cells, categories on NSString, etc.
What I'd like to do is move this out of the application itself, and
into some sort of code library that can be re-used in all of our future
projects.
Is making a framework the best way to do this?
I've read (I believe in Scott Anguish's book) that it can be hard to
track down bugs in code that has been bundled into a framework. I
forget exactly why; I think because gdb wouldn't debug at the
source-level inside a framework, or something like that. I haven't
actually tried this yet. Any real-world anecdotes would be appreciated.
What other methods are you guys using for separating commonly-used
utility classes from application-specific stuff?
Just wondering,
Steven
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.