[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Thu, 12 Dec 96 23:15:22 GMT
Most of my m files dont't run with 2.0. The fault is of course
the changed behaviour of scanf family. Shouldn't a compatibility
flag exist, such as octave-1.1.1_mode = 1, such that I just need
to add it at the top of my 'old' m files, instead of changing
all scanf statments? Of course, I can run sed on all my files, but
what about fget (and probably others) changed behaviour, from
[line count] = fgets(...) to just line = fgets(...)?
Do you think that matlab compatibility is more important that
octave compatibility? After all, we are talking of compatibility
with a 1.1.1 release, not a beta one.
Anyway, thanks for 2.0
Yes, I read it, but there is really no turnaround?
* The C-style I/O functions (fopen, fprintf, etc.) have been
rewritten to be more compatible with Matlab. The fputs function
has also been added. Usage of the *printf functions that was
allowed in previous versions of Octave should still work.
However, there is no way to make the new versions of the *scanf
functions compatible with Matlab *and* previous versions of
Octave. An optional argument to the *scanf functions is now
available to make them behave in a way that is compatible with
previous versions of Octave.
Joao Cardoso, INESC | e-mail: address@hidden
R. Jose Falcao 110 | tel: + 351 2 2094345
4000 Porto, Portugal | fax: + 351 2 2008487
- Oh, no...,
Joao Cardoso <=