Discussion:
octave 2.1.x to 2.9.x code compatibility
(too old to reply)
Thomas Plehn
2007-07-13 12:18:28 UTC
Permalink
Hello,

I have written some code for octave 2.1.73. The only reason, why I did
not upgrade already is that I fear my old code will not be backward
compatible with octave 2.9.12.
My question: Is porting from earlier versions only possible with lots of
efforts, or can I expect, that most of my old code runs with minor changes?
David Bateman
2007-07-13 23:07:08 UTC
Permalink
Post by Thomas Plehn
Hello,
I have written some code for octave 2.1.73. The only reason, why I did
not upgrade already is that I fear my old code will not be backward
compatible with octave 2.9.12.
My question: Is porting from earlier versions only possible with lots of
efforts, or can I expect, that most of my old code runs with minor changes?
What features of Octave 2.1 did you use? Hard to say what difficulties
you'll have without knowing that. The list of user visible changes in
octave 2.9 relative to 2.1 can be found in

http://velveeta.che.wisc.edu/cgi-bin/cvsweb.cgi/octave/NEWS?rev=HEAD

D.
g***@gmail.com
2007-08-29 20:13:05 UTC
Permalink
In the stable version the 'ls' command simply returned a usable
string, but that's no longer the case. Is there an alternative method
to search a directory for a file and return a string?
David Bateman
2007-08-30 07:50:13 UTC
Permalink
Post by g***@gmail.com
In the stable version the 'ls' command simply returned a usable
string, but that's no longer the case. Is there an alternative method
to search a directory for a file and return a string?
Two come to mind.. "dir" and "readdir".. The "readdir" function is
particularly nice as it returns a cell array with each file an element
of the cell array. You might also want to look at the "glob" function

D.

Loading...