FROM : Daniel Child
DATE : Fri Feb 01 19:10:10 2008
I use categories to separate out additional methods beyond the basic
accessors and init / constructor / dealloc.
In this case, though, since there are different subclasses, a
separate strategies class seemed to work better. Thanks for the
suggestion, though, as it gives me an idea for reverse sorting with
arrays.
On Jan 27, 2008, at 2:09 PM, Sam Stigler wrote:
> You might consider looking into categories. They let you add
> methods to existing classes... for example, add an -appendDOCstring:
> (NSData *)wordDocument method to NSMutableAttributedString. For
> more, see http://developer.apple.com/documentation/Cocoa/Conceptual/
> ObjectiveC/Articles/chapter_4_section_1.html . It might be more
> convenient for you in the long run to write all of your parsers as
> categories -- if not of NSMutableAttributedString, maybe of NSData.
DATE : Fri Feb 01 19:10:10 2008
I use categories to separate out additional methods beyond the basic
accessors and init / constructor / dealloc.
In this case, though, since there are different subclasses, a
separate strategies class seemed to work better. Thanks for the
suggestion, though, as it gives me an idea for reverse sorting with
arrays.
On Jan 27, 2008, at 2:09 PM, Sam Stigler wrote:
> You might consider looking into categories. They let you add
> methods to existing classes... for example, add an -appendDOCstring:
> (NSData *)wordDocument method to NSMutableAttributedString. For
> more, see http://developer.apple.com/documentation/Cocoa/Conceptual/
> ObjectiveC/Articles/chapter_4_section_1.html . It might be more
> convenient for you in the long run to write all of your parsers as
> categories -- if not of NSMutableAttributedString, maybe of NSData.
| Related mails | Author | Date |
|---|---|---|
| Daniel Child | Jan 27, 19:33 | |
| Sam Stigler | Jan 27, 20:09 | |
| Shripada Hebbar | Jan 28, 05:13 | |
| Daniel Child | Feb 1, 19:10 |






Cocoa mail archive

