Mercurial > octave-nkf
comparison doc/interpreter/dynamic.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 | 03b7f618ab3d |
| children | eb63fbe60fab |
comparison
equal
deleted
inserted
replaced
| 8827:55d999c23728 | 8828:8463d1a2e544 |
|---|---|
| 35 @appendix Dynamically Linked Functions | 35 @appendix Dynamically Linked Functions |
| 36 @cindex dynamic-linking | 36 @cindex dynamic-linking |
| 37 | 37 |
| 38 Octave has the possibility of including compiled code as dynamically | 38 Octave has the possibility of including compiled code as dynamically |
| 39 linked extensions and then using these extensions as if they were part | 39 linked extensions and then using these extensions as if they were part |
| 40 of Octave itself. Octave has the option of directly calling C++ code | 40 of Octave itself. Octave can call C++ code |
| 41 through its native oct-file interface or C code through its mex | 41 through its native oct-file interface or C code through its mex |
| 42 interface. It can also indirectly call functions written in any other | 42 interface. It can also indirectly call functions written in any other |
| 43 language through a simple wrapper. The reasons to write code in a | 43 language through a simple wrapper. The reasons to write code in a |
| 44 compiled language might be either to link to an existing piece of code | 44 compiled language might be either to link to an existing piece of code |
| 45 and allow it to be used within Octave, or to allow improved performance | 45 and allow it to be used within Octave, or to allow improved performance |
| 56 @item | 56 @item |
| 57 Is it thoroughly optimized Octave code? Vectorization of Octave code, | 57 Is it thoroughly optimized Octave code? Vectorization of Octave code, |
| 58 doesn't just make it concise, it generally significantly improves its | 58 doesn't just make it concise, it generally significantly improves its |
| 59 performance. Above all, if loops must be used, make sure that the | 59 performance. Above all, if loops must be used, make sure that the |
| 60 allocation of space for variables takes place outside the loops using an | 60 allocation of space for variables takes place outside the loops using an |
| 61 assignment to a like matrix or zeros. | 61 assignment to a matrix of the right size, or zeros. |
| 62 @item | 62 @item |
| 63 Does it make as much use as possible of existing built-in library | 63 Does it make as much use as possible of existing built-in library |
| 64 routines? These are highly optimized and many do not carry the overhead | 64 routines? These are highly optimized and many do not carry the overhead |
| 65 of being interpreted. | 65 of being interpreted. |
| 66 @item | 66 @item |
| 145 | 145 |
| 146 @example | 146 @example |
| 147 mkoctfile helloworld.cc | 147 mkoctfile helloworld.cc |
| 148 @end example | 148 @end example |
| 149 | 149 |
| 150 This will create a file call helloworld.oct, that is the compiled | 150 This will create a file called @file{helloworld.oct}, that is the compiled |
| 151 version of the function. It should be noted that it is perfectly | 151 version of the function. It should be noted that it is perfectly |
| 152 acceptable to have more than one @code{DEFUN_DLD} function in a source | 152 acceptable to have more than one @code{DEFUN_DLD} function in a source |
| 153 file. However, there must either be a symbolic link to the oct-file for | 153 file. However, there must either be a symbolic link to the oct-file for |
| 154 each of the functions defined in the source code with the @code{DEFUN_DLD} | 154 each of the functions defined in the source code with the @code{DEFUN_DLD} |
| 155 macro or the autoload (@ref{Function Files}) function should be used. | 155 macro or the autoload (@ref{Function Files}) function should be used. |