On Jun 2, 2008, at 19:50, Bill Bumgarner wrote:
On Jun 2, 2008, at 10:31 AM, Michael Vannorsdel wrote:
On Jun 2, 2008, at 5:24 AM, Francis Perea wrote:
Hi Graham, thanks for your reply.
I didn't know I could set any memory setting trough Interface
Builder!
After your question I looked into and I've seen that it states as
Beffered.
I've tried to use the Retained option, thinking that this way I
shouldn't use the retain message, but with Retained the windows
appears but doesn't accept any interaction.
I'd take a deep look into de Memory Management doc you suggest.
While learning the retain/release paradigm is certainly useful, it is
considerably more complex than GC. It is also unnecessary while
learning Cocoa. Specifically, GC is intended to be a production
quality solution that you can use in your Cocoa applications, without
exception. In Leopard, there have been a handful of bugs and they
have been addressed through software updates -- not surprising given
the rather sweeping and intrusive set of changes needed to support GC.
And GC will get better / faster in future releases.
An issue is that the previous releases still exist (retail Mac OS X
Leopard boxes are still 10.5?) and that someone may need to support
them. And in these cases, I would consider that retain/release is more
reliable.
I have a stupid question too. Considering that I sometimes see warnings
in Console.app related to Garbage Collection, does this mean that:
- the issue is in the application (Xcode sometimes display warnings for
instance) and not in the GC?
or
- that GC is more complex than retain/release in some cases?
_______________________________________________
Cocoa-dev mailing list ([email protected])
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]
