On Sep 21, 2008, at 18:08, Rick Mann wrote:
I was going to say...especially for immutable objects like NSString
and NSNumber, which you pointed out are almost always used as
attributes and not as relationships, it seems to make more sense
(from a performance standpoint, at least) to just as
On Sep 21, 2008, at 15:22:22, Quincey Morris wrote:
On Sep 21, 2008, at 15:00, Quincey Morris wrote:
So, is it really inappropriate? It seems very appropriate to
assign the pointer rather than allocate a new object and copy it,
especially for immutable objects.
No, it's not.
Sorry, jus
On Sep 21, 2008, at 15:00, Quincey Morris wrote:
So, is it really inappropriate? It seems very appropriate to assign
the pointer rather than allocate a new object and copy it,
especially for immutable objects.
No, it's not.
Sorry, just to clarify -- no, it's not really inappropriate. Yes,
On Sun, Sep 21, 2008 at 5:04 PM, Rick Mann <[EMAIL PROTECTED]> wrote:
> According to the Obj-C 2.0 docs:
>
>> assign
>> Specifies that the setter uses simple assignment. This is the default.
>>
>> If your application uses garbage collection, if you want to use assign for
>> a property whose class a
On Sep 21, 2008, at 14:04, Rick Mann wrote:
But the warning is:
"warning: 'assign' attribute on property 'portName' which implements
'NSCopying' protocol not appropriate with -fobjc-gc-only"
So, is it really inappropriate? It seems very appropriate to assign
the pointer rather than alloca
