2) Define a custom C struct (like NSRect, but with e.g. 'string' and 'offset' members) and return objects in it. Just like any other returned objects, the caller would be expected to retain them individually if it needed to keep them around.
I'd probably do it this way if the method was private to the module; with the struct passed in by reference thereby passing any memory management issues onto the caller, i.e. it could be stack allocated or malloc'd
Otherwise if it was a public method, it follow the -get... convention returning both parameters by reference.
Keith Duncan [EMAIL PROTECTED], 33software.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
