'save_precision' doesn't work

[Sergei Steshenko]

--- On Wed, 12/24/08, John W. Eaton <jwe at octave.org> wrote:

> From: John W. Eaton <jwe at octave.org>
> Subject: Re: 'save_precision' doesn't work
> To: sergstesh at yahoo.com
> Cc: "Jaroslav Hajek" <highegg at gmail.com>, bug-octave at octave.org
> Date: Wednesday, December 24, 2008, 10:22 AM
> On 24-Dec-2008, Sergei Steshenko wrote:
> 
> | There is no sense in having a 'save' subroutine
> which always truncates
> | data, i.e. if it's not a bug in code (i.e. the code
> works as advertised),
> | it's a bug in spec, i.e. the code implements wrong
> goals.
> 
> Complain to the MathWorks about the design decision.  Since
> the -ascii
> option to save is clearly documented as saving 8 digits, I
> think we
> would also see complaints if we did something different
> here.
> 
> | I think that 'save_precision' should simply
> affect all 'save' operations.
> 
> I think save_precision should maybe be removed from Octave.
> 
> jwe

What about '-octave_ascii' which obeys 'save_precision' ?

At all, probably there should be C++ code which is functionally betters
than the one of MathWorks, and a 'save.m' file which truncates/tunes the
C++ code to be compatible with Matlab.

Thanks,
  Sergei.