From octave-maintainers-request at bevo dot che dot wisc dot edu Sat Nov 15 21:25:10 2003
Subject: Octave 2.1.51 available for ftp
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: octave-maintainers mailing list <octave-maintainers at bevo dot che dot wisc dot edu>
Date: Sat, 15 Nov 2003 21:24:55 -0600

Octave 2.1.51 is now available for ftp from ftp.octave.org in the
directory /pub/octave/bleeding-edge:

  -rw-r--r--  1 103  4888529 Nov 16 00:37 octave-2.1.51.tar.gz
  -rw-r--r--  1 103  3865822 Nov 16 00:37 octave-2.1.51.tar.bz2
  -rw-r--r--  1 103   277494 Nov 16 00:47 octave-2.1.50-2.1.51.patch.gz
  -rw-r--r--  1 103   222150 Nov 16 00:47 octave-2.1.50-2.1.51.patch.bz2

This version has many new features and bug fixes.  The biggest change
is that N-d arrays (for numbers, structs, and cells) are mostly
working, though there are some significant features that still need to
be implemented.  For example, the [] operator will fail to concatenate
N-d arrays, but we hope to fix this for 2.1.52.  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.

The following built-in preference variables have also been removed in
favor of always behaving in Matlab-compatible ways:

  default_eval_print_flag
  default_return_value
  define_all_return_values
  do_fortran_indexing
  empty_list_elements_ok
  implicit_num_to_str_ok
  implicit_str_to_num_ok
  ok_to_lose_imaginary_part
  prefer_column_vectors
  propagate_empty_matrices
  resize_on_range_error
  return_last_computed_value
  treat_neg_dim_as_zero
  whitespace_in_literal_matrix

The following built-in variables have been added to allow control over
warnings about some of the features that were previously controlled by
the deleted built-in variables:

  warn_empty_list_elements
  warn_fortran_indexing
  warn_imag_to_real
  warn_neg_dim_as_zero
  warn_num_to_str
  warn_resize_on_range_error
  warn_str_to_num

But regardless of the settings of these variables, the behavior is
always supposed to be Matlab compatible now.

As always, if your favorite bug is still not fixed, please let me know
about it.

Thanks,

jwe

-- 
www.octave.org        | Unfortunately we were hopelessly optimistic in 1954
www.che.wisc.edu/~jwe | about the problems of debugging FORTRAN programs.
                      |                                       -- J. Backus