On Fri, 31 Jul 2015 12:15:10 +0200, Jean-Daniel Dupas said:
Le 30 juil. 2015 à 18:26, Fritz Anderson fri...@manoverboard.org a écrit :
On 30 Jul 2015, at 11:03 AM, Trygve Inda cocoa...@xericdesign.com wrote:
It seems Apple is using retain rather than copy for NSString properties in
an
Le 30 juil. 2015 à 18:26, Fritz Anderson fri...@manoverboard.org a écrit :
On 30 Jul 2015, at 11:03 AM, Trygve Inda cocoa...@xericdesign.com wrote:
It seems Apple is using retain rather than copy for NSString properties in
an NSManagedObject subclass.
I was always under the impression
On 30 Jul 2015, at 11:03 AM, Trygve Inda cocoa...@xericdesign.com wrote:
It seems Apple is using retain rather than copy for NSString properties in
an NSManagedObject subclass.
I was always under the impression that copy should be used for NSString, so
why the retain??
For an immutable
It seems Apple is using retain rather than copy for NSString properties in
an NSManagedObject subclass.
I was always under the impression that copy should be used for NSString, so
why the retain??
Trygve
___
Cocoa-dev mailing list
On Jul 30, 2015, at 9:03 AM, Trygve Inda cocoa...@xericdesign.com wrote:
It seems Apple is using retain rather than copy for NSString properties in
an NSManagedObject subclass.
So, you’re saying that if you store an NSMutableString into a dynamic
NSManagedObject property, and then mutate
According to Andy Lee:
On May 11, 2009, at 10:15 PM, jon wrote:
my wild guess right now is to do this below when ever i have the
NSString instance assignment to prevent, for instance, theTitle
from randomly disappearing...
I hope the following doesn't sound harsh, because I'm not
On Tue, May 12, 2009 at 9:00 AM, Drew Lawson d...@furrfu.com wrote:
Maybe I'm just psychic, or it could be because I made a bunch of
newby mistakes 2-3 months ago, but it doesn't sound meaningless to
me.
It's meaningless because it does not address what the OP is actually
seeing.
from my very limited Objective-C programing experience of all of 10
days...
it appears to me that my assignments to NSStrings seem to, at random,
disappear. (i, being a new Objective-C programmer coming from
pascal and C, like to have a global string in several places, not
that it
On Mon, May 11, 2009 at 7:15 PM, jon trambl...@mac.com wrote:
from my very limited Objective-C programing experience of all of 10 days...
it appears to me that my assignments to NSStrings seem to, at random,
disappear. (i, being a new Objective-C programmer coming from pascal and
C, like
On May 11, 2009, at 10:15 PM, jon wrote:
my wild guess right now is to do this below when ever i have the
NSString instance assignment to prevent, for instance, theTitle
from randomly disappearing...
I hope the following doesn't sound harsh, because I'm not trying to
be...
I'd second
10 matches
Mail list logo
