[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bugs #11724] -[EOModel writeToFile:] broken
From: |
Dirk Lattermann |
Subject: |
[bugs #11724] -[EOModel writeToFile:] broken |
Date: |
Mon, 24 Jan 2005 21:06:47 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 |
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=11724>
Summary: -[EOModel writeToFile:] broken
Project: GNUstep
Submitted by: dlatt
Submitted on: Mon 01/24/2005 at 21:06
Category: gdl2
Severity: 5 - Average
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
I. This method sets the receiver's path early.
1. This may be problematic in case of a failure: when the method doesn't
complete because of some error, the EOModel's path should not be modified (I
guess).
2. Strangely, in this method, the model tries to _read_ some information from
the file given by path. As it has modified its path by then, this fails.
Even if I call -initWithContentsOfFile: and then loadAllModelObjects, the
model wants to read something from file during -writeToFile:.
3. In EOModel.m, moving the call [self _setPath: path] from the top of
-writeToFile: to the very end seems to help, but I don't know if there are
side effects.
II. after creating a model with an .eomodeld-file by
-initWithContentsOfFile:, writing it to a file effectively copies the old
file, even when there are nonsensical key = value pairs in the plist
dictionaries. Is this ok? Also, there are no default values for omitted keys
written to the output file. Is this ok, too?
_______________________________________________________
This item URL is:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=11724>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bugs #11724] -[EOModel writeToFile:] broken,
Dirk Lattermann <=