Re: Encoding infinite loops
Re: Encoding infinite loops
- Subject: Re: Encoding infinite loops
- From: Uli Kusterer <email@hidden>
- Date: Wed, 23 May 2007 01:42:19 +0200
On 23.05.2007, at 01:05, Chris Kane wrote:
However, detecting this only when the document is later loaded (and
having the attempt fail) does not seem very satisfying. The user
saved their document and can't reopen it. But, the archiver, while
it knows when recursion occurs, can't detect this situation (not
all recursion is evil). I suppose you could say, though, that the
developer would presumably discover this problem in writing/testing
their app, before the situation gets to the end user.
Yes, that would at least make it easier on the developer than
having weird crashes because some object got released or only
partially constructed. There would be a chance of finding this during
development or later through an obviously visible failure to load
certain files. Also, a warning in the reference docs that links to a
description of the problem would also help developers avoid and track
down this issue.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden