r15486 - gnucash/trunk/src - SX "enabled" patch from Peter McAlpine <peter at aoeu.ca>.

[Josh Sled]

On Thu, 2007-02-01 at 20:10 -0500, Nathan Buchanan wrote:
> On 2/1/07, Derek Atkins <warlord at mit.edu> wrote:
>         Quoting Josh Sled <jsled at asynchronous.org>:
>         
>         > To preempt your question about "how do you tell a broken
>         datafile from
>         > one with simply new tags?", I say: "you don't".  You let
>         XML 
>         > well-formed-ness deal with really corrupted datafiles, and
>         you ignore
>         > any tags or attributes that you don't recognize.   If you
>         then ignore
>         > valid future data, fine; if you ignore invalid/broken data,
>         fine.  The 
>         > utility of reading a wider set of datafiles is higher than
>         the risk of
>         > reading inconsistent data, with some amount of care taken in
>         the future.
>         
>         I still maintain that loading-and-ignoring is WORSE than
>         failing-to-load. 
>         When you load-and-ignore, then when you save you've now LOST
>         data, and
>         worse, you've lost it silently!  I think that's worse than
>         just failing to
>         load the datafile.
>         
> As a lurking user, I'd like to say that data should not be lost
> silently. At worst, display a message so that the user can abort the
> load. 

FTR, I never suggested that.  We're in all agreement that you can not
and should not be silent about losing data.

-- 
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org;echo ${a}@${b}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20070201/49929a25/attachment.bin