Mercurial > octave-nkf
diff doc/interpreter/stmt.txi @ 18851:9ac2357f19bc
doc: Replace "non-zero" with "nonzero" to match existing usage.
Replace all occurrences in both documentation and code comments.
* doc/interpreter/contrib.txi, doc/interpreter/diagperm.txi,
doc/interpreter/external.txi, doc/interpreter/sparse.txi,
doc/interpreter/stmt.txi, doc/interpreter/testfun.txi, doc/refcard/refcard.tex,
examples/mysparse.c, libinterp/corefcn/balance.cc,
libinterp/corefcn/cellfun.cc, libinterp/corefcn/data.cc,
libinterp/corefcn/filter.cc, libinterp/corefcn/find.cc,
libinterp/corefcn/kron.cc, libinterp/corefcn/ls-mat5.cc,
libinterp/corefcn/luinc.cc, libinterp/corefcn/mappers.cc,
libinterp/corefcn/oct-fstrm.cc, libinterp/corefcn/oct-fstrm.h,
libinterp/corefcn/oct-iostrm.cc, libinterp/corefcn/oct-iostrm.h,
libinterp/corefcn/oct-stdstrm.h, libinterp/corefcn/oct-strstrm.h,
libinterp/corefcn/spparms.cc, libinterp/corefcn/toplev.cc,
libinterp/corefcn/utils.cc, libinterp/dldfcn/symrcm.cc,
libinterp/octave-value/ov-bool-mat.cc, liboctave/array/CSparse.cc,
liboctave/array/Sparse.cc, liboctave/array/Sparse.h,
liboctave/array/dSparse.cc, liboctave/numeric/randmtzig.c,
liboctave/operators/Sparse-op-defs.h, scripts/help/get_first_help_sentence.m,
scripts/miscellaneous/edit.m, scripts/plot/draw/pie.m,
scripts/plot/draw/pie3.m, scripts/sparse/colperm.m, scripts/sparse/nonzeros.m,
scripts/sparse/spdiags.m, scripts/sparse/spfun.m, scripts/sparse/spones.m,
scripts/sparse/sprand.m, scripts/sparse/sprandn.m, scripts/sparse/sprandsym.m,
scripts/sparse/spstats.m, scripts/sparse/svds.m,
scripts/special-matrix/gallery.m, scripts/statistics/base/moment.m,
scripts/statistics/tests/cor_test.m:
Replace "non-zero" with "nonzero" to match existing usage.
author | Rik <rik@octave.org> |
---|---|
date | Sun, 08 Jun 2014 17:59:59 -0700 |
parents | faf32a725693 |
children | 0e1f5a750d00 |
line wrap: on
line diff
--- a/doc/interpreter/stmt.txi Sun Jun 08 16:36:54 2014 -0700 +++ b/doc/interpreter/stmt.txi Sun Jun 08 17:59:59 2014 -0700 @@ -83,10 +83,10 @@ @var{condition} is true. The condition in an @code{if} statement is considered true if its value -is non-zero, and false if its value is zero. If the value of the +is nonzero, and false if its value is zero. If the value of the conditional expression in an @code{if} statement is a vector or a matrix, it is considered true only if it is non-empty and @emph{all} -of the elements are non-zero. +of the elements are nonzero. The second form of an if statement looks like this: @@ -398,10 +398,10 @@ The @code{while} statement is the simplest looping statement in Octave. It repeatedly executes a statement as long as a condition is true. As with the condition in an @code{if} statement, the condition in a -@code{while} statement is considered true if its value is non-zero, and +@code{while} statement is considered true if its value is nonzero, and false if its value is zero. If the value of the conditional expression in a @code{while} statement is a vector or a matrix, it is considered -true only if it is non-empty and @emph{all} of the elements are non-zero. +true only if it is non-empty and @emph{all} of the elements are nonzero. Octave's @code{while} statement looks like this: @@ -463,10 +463,10 @@ true, and the test of the condition is at the end of the loop, so the body of the loop is always executed at least once. As with the condition in an @code{if} statement, the condition in a @code{do-until} -statement is considered true if its value is non-zero, and false if its +statement is considered true if its value is nonzero, and false if its value is zero. If the value of the conditional expression in a @code{do-until} statement is a vector or a matrix, it is considered -true only if it is non-empty and @emph{all} of the elements are non-zero. +true only if it is non-empty and @emph{all} of the elements are nonzero. Octave's @code{do-until} statement looks like this: