Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Returning structs of NSStrings

I would always create classes. You get a lot of benefits from working
with proper classes IMO. Why code in ObjC if you're not using objects?

j o a r

On 2004-03-25, at 11.26, Michael Becker wrote:

> So thanks for the replies! But my second question still bothers me:
>
> I've noticed that dealing with large structs of NSStrings can get
> really annoying ("copying" these structs can only be done via copying
> each NSString in them [right?]). So should I make all of these into
> classes, providing accessor methods? Or am I missing out on something
> again? Should I maybe even mix Objective-C++ into it all?
>
> Sorry for asking question that nobody should answer but myself, but I
> am more or less asking for stylistic guidance :-)

[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
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.

References: 
 >Returning structs of NSStrings (From: Michael Becker <email@hidden>)
 >Re: Returning structs of NSStrings (From: Michael Becker <email@hidden>)
 >Re: Returning structs of NSStrings (From: j o a r <email@hidden>)
 >Re: Returning structs of NSStrings (From: Michael Becker <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.