[bugs #11724] -[EOModel writeToFile:] broken

[David Ayers]

Update of bugs #11724 (project gnustep):

              Item Group:                     Bug => Change Request         
                  Status:                    None => Invalid                
             Assigned to:                    None => ayers                  

    _______________________________________________________

Follow-up Comment #1:

Hello Dirk,

I've spent some time looking into this and with the exception of the noop of
loadAllModelObjects which I now have implemented in CVS, this is the expected
behavior.



I admit it is counter intuitive but calling -writeToFile: has the side effect
of changing the name and path of the model in memory independent of whether
the write is successful or not.



I’m inclined to interpret a the state of the model as undefined by the API
therefore allowing us to change this behavior to cache the old name and path
and reset it to the old value of writing fails.  OTOH this adds extra
complexity that I’m not really fond of either.



For now I’ll put this report on "invalid" but I’ll wait for you thoughts
before adding documentation and closing the bug report.



As to validation, there is actually very little validation that I could
encounter in WO4.5.  In fact I know of production applications that use
certain constructs that EOModeler warns about when saving but are crucial to
the correct execution of the app.  So unless we have a very good reason to
force correct values in -writeToFile: I think we should leave it as it is. 
Is there a specific issue that you are worried about?



    _______________________________________________________

This item URL is:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=11724>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/