Aside from that. Are there tutorials or some such for these Cocoa
Release ideals or will I cross them when I read the pdf ?
There's a *very* simple set of rules to follow regarding retain/release.
Newbies sometimes make it hard on themselves by doing extra work, rather
than trying to follow the
On Mar 25, 2008, at 2:06 PM, Scott Ribe wrote:
There's a *very* simple set of rules to follow regarding retain/
release.
Yes, but where are they documented? Or, if they're so simple, can you
quote them here?
Not to sound querulous, but what I know of these very simple rules I
picked up
On Mar 25, 2008, at 4:01 PM, Jack Repenning wrote:
On Mar 25, 2008, at 2:06 PM, Scott Ribe wrote:
There's a *very* simple set of rules to follow regarding retain/
release.
Yes, but where are they documented?
On Mar 25, 2008, at 6:01 PM, Jack Repenning wrote:
On Mar 25, 2008, at 2:06 PM, Scott Ribe wrote:
There's a *very* simple set of rules to follow regarding retain/
release.
Yes, but where are they documented? Or, if they're so simple, can
you quote them here?
Not to sound querulous, but
On Mar 25, 2008, at 4:02 PM, Rob Napier wrote:
On Tue, Mar 25, 2008 at 6:15 PM, Randall Meadows [EMAIL PROTECTED]
pc.com
wrote:
I was thinking
http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Concepts/ObjectOwnership.html#/
/apple_ref/doc/uid/2043
.
If people
I'll make a compromise with you. :-)
I'll let you try one... just one... RubyCocoa application before you
start looking at Objective-C. Start here:
http://developer.apple.com/documentation/Cocoa/Conceptual/RubyPythonCocoa/Articles/BuildingRubyCocoaAppl.html#/
On Mar 25, 2008, at 4:28 PM, Jack Repenning wrote:
On Mar 25, 2008, at 4:02 PM, Rob Napier wrote:
I was thinking
http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Concepts/ObjectOwnership.html
If people will read nothing but Practical Memory Management (the
page
after
on 2008-03-24 10:32 AM, Scott Thompson at [EMAIL PROTECTED] wrote:
Over time, there will be more code able to take advantage of the
Garbage Collector, but I think it will be some time before it's
ubiquitous enough to remove the retain/release memory management
scheme from the literature.
Let
In Ruby GC just works dandy without thought. Why is it so different in
Cocoa Obj2.0?
What kinda of real headaches will I have jumping into osx programing
compared to ruby ?
On 3/24/08, Bill Cheeseman [EMAIL PROTECTED] wrote:
on 2008-03-24 10:32 AM, Scott Thompson at [EMAIL PROTECTED] wrote:
In Ruby GC just works dandy without thought. Why is it so different in
Cocoa Obj2.0?
What kinda of real headaches will I have jumping into osx programing
compared to ruby ?
The short answer is that Ruby is a nifty high level scripting language
that insulates the programmer thoroughly from
on 2008-03-24 11:30 AM, colo at [EMAIL PROTECTED] wrote:
In Ruby GC just works dandy without thought. Why is it so different in
Cocoa Obj2.0?
My main issue is how to know exactly when to declare instance variables weak
or strong. There seem to be some subtleties in that area that I don't yet
Scott Thompson wrote:
To integrate the two, someone would have to rewrite the internals of
the Ruby interpreter and add in special case code for Objective-C
objects.
FYI, there's a project afoot to do just that, porting the Ruby 1.9
interpreter to run on top of Cocoa:
On Mar 24, 2008, at 3:03 PM, colo wrote:
But I do not wish to use the bridge options yet I would rather do it
right in one place than trying to glue it together and spend days not
getting it
I'll make a compromise with you. :-)
I'll let you try one... just one... RubyCocoa application
13 matches
Mail list logo
