Mercurial > hg > octave-lyh
changeset 3600:c11d138d654a
[project @ 2000-02-24 03:55:32 by jwe]
author | jwe |
---|---|
date | Thu, 24 Feb 2000 03:55:33 +0000 |
parents | b8fa63b7ea79 |
children | b1830ce6993a |
files | doc/interpreter/bugs.txi scripts/linear-algebra/rank.m scripts/plot/mesh.m scripts/plot/meshdom.m src/DLD-FUNCTIONS/qr.cc src/DLD-FUNCTIONS/schur.cc src/error.cc src/mappers.cc |
diffstat | 8 files changed, 10 insertions(+), 13 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/interpreter/bugs.txi +++ b/doc/interpreter/bugs.txi @@ -79,7 +79,7 @@ @end example when trying to plot many lines on one graph, you have probably generated -a plot command that is too larger for @code{gnuplot}'s fixed-length +a plot command that is too large for @code{gnuplot}'s fixed-length buffer for commands. Splitting up the plot command doesn't help because replot is implemented in gnuplot by simply appending the new plotting commands to the old command line and then evaluating it again.
--- a/scripts/linear-algebra/rank.m +++ b/scripts/linear-algebra/rank.m @@ -25,11 +25,11 @@ ## argument is omitted, it is taken to be ## ## @example -## tol = max (size (@var{a})) * sigma (1) * eps; +## tol = max (size (@var{a})) * sigma(1) * eps; ## @end example ## ## @noindent -## where @code{eps} is machine precision and @code{sigma} is the largest +## where @code{eps} is machine precision and @code{sigma(1)} is the largest ## singular value of @var{a}. ## @end deftypefn
--- a/scripts/plot/mesh.m +++ b/scripts/plot/mesh.m @@ -19,7 +19,7 @@ ## -*- texinfo -*- ## @deftypefn {Function File} {} mesh (@var{x}, @var{y}, @var{z}) -## Plot a mesh given matrices @code{x}, and @var{y} from @code{meshdom} and +## Plot a mesh given matrices @var{x}, and @var{y} from @code{meshdom} and ## a matrix @var{z} corresponding to the @var{x} and @var{y} coordinates of ## the mesh. If @var{x} and @var{y} are vectors, then a typical vertex ## is (@var{x}(j), @var{y}(i), @var{z}(i,j)). Thus, columns of @var{z}
--- a/scripts/plot/meshdom.m +++ b/scripts/plot/meshdom.m @@ -22,9 +22,6 @@ ## Given vectors of @var{x} and @var{y} coordinates, return two matrices ## corresponding to the @var{x} and @var{y} coordinates of the mesh. ## -## See the file @file{sombrero.m} for an example of using @code{mesh} and -## @code{meshdom}. -## ## Note: this function is provided for compatibility with older versions ## of @sc{Matlab}. You should use @code{meshgrid} instead. ## @end deftypefn
--- a/src/DLD-FUNCTIONS/qr.cc +++ b/src/DLD-FUNCTIONS/qr.cc @@ -120,7 +120,7 @@ given the matrix @code{a = [1, 2; 3, 4]},\n\ \n\ @example\n\ -[q, r, pi] = qr(a)\n\ +[q, r, p] = qr(a)\n\ @end example\n\ \n\ @noindent\n\
--- a/src/DLD-FUNCTIONS/schur.cc +++ b/src/DLD-FUNCTIONS/schur.cc @@ -135,7 +135,7 @@ @ifinfo\n\ @code{2 x 2}\n\ @end ifinfo\n\ -blocks along the diagonal. The diagonal elements of\n\ +along the diagonal. The diagonal elements of\n\ @iftex\n\ @tex\n\ $S$\n\
--- a/src/error.cc +++ b/src/error.cc @@ -354,9 +354,9 @@ @deftypefn {Built-in Function} {} warning (@var{msg})\n\ Print a warning message @var{msg} prefixed by the string @samp{warning: }. \n\ After printing the warning message, Octave will continue to execute\n\ -commands. You should use this function should when you want to notify\n\ -the user of an unusual condition, but only when it makes sense for your\n\ -program to go on.\n\ +commands. You should use this function when you want to notify the user\n\ +of an unusual condition, but only when it makes sense for your program\n\ +to go on.\n\ @end deftypefn") { return handle_message (warning, "unspecified warning", args);
--- a/src/mappers.cc +++ b/src/mappers.cc @@ -331,7 +331,7 @@ DEFUN_MAPPER (finite, 0, xfinite, xfinite, 0, 0, 0, 0.0, 0.0, 0, "-*- texinfo -*-\n\ @deftypefn {Mapping Function} {} finite (@var{x})\n\ -Return 1 for elements of @var{x} that are NaN values and zero\n\ +Return 1 for elements of @var{x} that are finite values and zero\n\ otherwise. For example,\n\ \n\ @example\n\