octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #32750] save in 3.4.0 is not backwards compati


From: Rik
Subject: [Octave-bug-tracker] [bug #32750] save in 3.4.0 is not backwards compatible with load in 3.2.2
Date: Wed, 16 Mar 2011 16:41:03 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110303 Ubuntu/10.04 (lucid) Firefox/3.6.15

Update of bug #32750 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 3 - Low                
                  Status:                    None => Wont Fix               

    _______________________________________________________

Follow-up Comment #3:

I understand that this would be a nice feature to have, but it would also
limit future additions to Octave load/save functionality.

By example, Microsoft Word can save in either .doc or .docx format.  The old
.doc files can be read by any version of Word, but only later versions of Word
can use the extra features in the .docx format.  This is the same situation
that Octave has, although we didn't rename the file extension.

I checked your file and when saved in Octave text format under 3.2 it
correctly loads under 3.4.  Thus, 3.4 is backwards compatible with older
versions of Octave which is critically important for maintaining access to
legacy data.  However, to be able to take advantage of some new features (such
as range compression) you will need a recent version of Octave.

Incidentally, Matlab got into the same issue which is why there are -v4, -v6,
and -v7 flags for loading Matlab data files.

This bug won't be fixed, but the report will be left in place for users who
may stumble upon this issue.

Suggested workarounds
1) Upgrade all collaborating users to the same version of Octave.
2) Use a specified file format, such as -v7 or -hdf5, for sharing files
between different versions of Octave.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32750>

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]