Re: Octave 2.1.57 available for ftp

[Paul Thomas]

John,

I am beginning to think that I am unimaginative; I have already found 
2.1.56 to be bomb-proof!

As I have said elsewhere, I am shipping work home from the other product 
and it runs without problem on octave.  There are some slight 
differences that have required code modifications; for example, gnuplot 
defaulting to legends('on') and matlab to legends('off') - this had a 
truly spectacular outcome the first time that I ran my X-ray optics 
programme because each of many tens of components is drawn with several 
separate lines! However, the computational results are identical.

Has anybody done an inventory of the N-d features available on the other 
product?

Paul T

John W. Eaton wrote:

> Octave 2.1.57 is now available for ftp from ftp.octave.org in the
> directory /pub/octave/bleeding-edge:
>
>  -rw-r--r--  1 103  5333458 Mar 12 13:41 octave-2.1.57.tar.gz
>  -rw-r--r--  1 103  4202080 Mar 12 13:41 octave-2.1.57.tar.bz2
>  -rw-r--r--  1 103    14588 Mar 12 13:42 octave-2.1.56-2.1.57.patch.gz
>  -rw-r--r--  1 103    13658 Mar 12 13:42 octave-2.1.56-2.1.57.patch.bz2
>
> This version should fix most of the bugs reported since 2.1.56.
>
> There are still some significant features related to N-d arrays that
> need to be implemented, but this version does provide a cat function
> and also allows you to use the [] to concatenate N-d numeric arrays.
> This still needs to be extended to handle cell and structure arrays
> and user-defined types.  We hope to fix this in the near future.
> If you find that another of your favorite N-d array operations doesn't
> work, please mention it so we can have some idea of what features are
> missed the most.  Patches are also welcome.
>
> As always, if your favorite bug is still not fixed, please report it.
>
> Since we seem to be converging on something that works reasonably
> well, I'm going to make a bold move and call 2.1.57 the recommended
> version.  If there are any objections to that, or if you know of any
> serious problems with 2.1.56 that you have not yet reported, please
> speak up.
>
> Thanks,
>
> jwe
>
>
>