On 6 Feb 2009, at 14:18, Steve Sisak wrote:
If you use an Objective-C 2.0 property (rather than a variable) and
specifying retain semantics, you'll get that behavior -- with a bit
of overhead.
Ah interesting, just the kind of result I was hoping to obtain from
asking dumb questions. In my experience there is never a definite
never. Everything can be resolved by a degree of abstraction and a
penalty in performance at the price of convenience.
On 6 Feb 2009, at 13:53, Sherm Pendley wrote:
The compiler can't do that because assigning to a pointer and
assigning to a pointer's target are two *completely* different
things, and the programmer asked it to do the former.
C and its derivatives do what you say, not what you mean. That is a
feature, not a flaw.
sherm--
OK cheers, everything is starting to click back in place now. I was
originally C and Basic , But have been spoilt by the simplicities of
PHP, Javascript, Actionscript, Perl, cobal, html, css for far too
long. Occasionally dipped in and out of Objective C/Cocoa wrote a few
programs a few years ago for the platform but managed to limp by
without addressing the topic of memory to much of an extent.
And for the last year I have been working on Facebook platform, which
was just a royal PITA all round.
A couple of experimental OSX apps, then I'm full time OSX Developer,
have many social app ideas I wish to work on.
And I look forward to it, have always enjoyed the poetry of logic
found in few places other than Cocoa/Objective C.
It's good to be home :)
_______________________________________________
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 arch...@mail-archive.com
