help-octave
[Top][All Lists]
Advanced

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

Re: save function


From: Thorsten Meyer
Subject: Re: save function
Date: Wed, 09 Mar 2005 22:50:15 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1

Francesco Potorti` wrote:
imaginary parts of complex numbers) and current behavior.  Maybe something 
like "-ascii-annotated" would be a good name for the current "-ascii" 
feature.
    

The -ascii switch is very useful and handy.  I always use it, because I
never know how I will manage may data.  I only use -binary when I am
going to reuse the data immediately, in the same run.

This means that, in my personal situation, I wouldn't be afected by an
incompatible change to the -binary format, I wouldn't even realize it.
But I would be affected by a change in the -ascii format, because I
could be saving more than one variable and later find that the file is
useless without the meta information.

Apart from my personal habits, if it must really happen that -ascii
behaviour is changed (I hope not), then please choose an equivalently
short name, like -text or whatever, don't use -ascii-annotated.

  
Hi,

I do not think that changing the behaviour of save -ascii to the matlab way is a good idea. For a person that is new to octave (but not coming from matlab) it would be quite confusing if the save function did not do the obvious thing, i.e. save data in such a way that they can be loaded again. Thus you might end up with those octave newbies complaining who do not come from matlab.  To mend that you might change the default_save_format, but to what? To octave binary or even to matlab binary (for compatibility reasons)? Please don't do that.
By the way: are you planning to remove the global variable default_save_format at some point?

regards

Thorsten Meyer


reply via email to

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