Mercurial > hg > octave-lyh
diff doc/interpreter/numbers.txi @ 8828:8463d1a2e544
Doc fixes.
* 2]$$. => 2].$$
* @var{extrapval} => @var{extrapval}.
* call helloworld.oct => called @file{helloworld.oct}
* @itemize => @table @code
* shows. => shows:
* save => @code{save}
* @ref{Breakpoints} => @pxref{Breakpoints}
* add @noindent following example
* which is computed => and compute it
* clarify wording
* remove comma
* good => well
* set => number
* by writing => with the command
* has the option of directly calling => can call
* [-like-] {+of the right size,+}
* solvers => routines
* handle => test for
* add introductory section
* add following
* {+the+} [0..bitmax] => [0,bitmax]
* of the => with
* number => value
* add usual
* Besides when doing comparisons, logical => Logical {+also+}
* array comparison => array, comparisons
* param => parameter
* works very similar => is similar
* strings, => strings
* most simple => simplest
* easier => more easily
* like => as
* called => called,
* clarify wording
* you should simply type => use
* clarify wording
* means => way
* equally => also
* [-way much-] {+way+}
* add with mean value parameter given by the first argument, @var{l}
* add Functions described as @dfn{mapping functions} apply the given
operation to each element when given a matrix argument.
* in this brief introduction => here
* It is worth noticing => Note
* add following
* means => ways
| author | Brian Gough <bjg@network-theory.co.uk> |
|---|---|
| date | Fri, 20 Feb 2009 11:17:01 -0500 |
| parents | 0eb83938c8bc |
| children | eb63fbe60fab |
line wrap: on
line diff
--- a/doc/interpreter/numbers.txi +++ b/doc/interpreter/numbers.txi @@ -514,7 +514,7 @@ then re-casting the values back to the original integer type. As the double precision type of Octave is only capable of representing integers with up to 53 bits of precision, it is not possible to perform -arithmetic of the 64 bit integer types. +arithmetic with 64 bit integer types. When doing integer arithmetic one should consider the possibility of underflow and overflow. This happens when the result of the computation @@ -566,7 +566,7 @@ @code{10}, it is treated as the bits @code{[1, 0, 1, 0]} rather than the bits of the native floating point format representation of @code{10}. -As the maximum number that can be represented by a number is important +As the maximum value that can be represented by a number is important for bit manipulation, particularly when forming masks, Octave supplies the function @code{bitmax}. @@ -622,7 +622,7 @@ The basic logical operations are @code{&}, @code{|}, and @code{!}, which correspond to ``Logical And'', ``Logical Or'', and ``Logical -Negation''. These operations all follow the rules of logic. +Negation''. These operations all follow the usual rules of logic. It is also possible to use logical values as part of standard numerical calculations. In this case @code{true} is converted to @code{1}, and @@ -645,7 +645,7 @@ Instead of creating the @code{idx} array it is possible to replace @code{data(idx)} with @code{data( data <= 2 )} in the above code. -Besides when doing comparisons, logical values can be constructed by +Logical values can also be constructed by casting numeric objects to logical values, or by using the @code{true} or @code{false} functions.