Mercurial > octave-libgccjit
diff doc/interpreter/dynamic.txi @ 8347:fa78cb8d8a5c
corrections for typos
Here is a patch with some corrections for typos and missing/extra
words in the manual.
changeset: 8347:34fd1d1c2294
user: Brian Gough <bjg@gnu.org>
date: Wed Nov 26 11:00:15 2008 -0500
summary: [docs] can not => cannot
author | Brian Gough<bjg@network-theory.co.uk> |
---|---|
date | Thu, 27 Nov 2008 10:28:24 +0100 |
parents | 804c60f92fb1 |
children | cc3ad79fd6b7 |
line wrap: on
line diff
--- a/doc/interpreter/dynamic.txi Tue Nov 25 14:04:55 2008 +0100 +++ b/doc/interpreter/dynamic.txi Thu Nov 27 10:28:24 2008 +0100 @@ -69,7 +69,7 @@ @end itemize Also, as oct- and mex-files are dynamically linked to octave, they -introduce to possibility of having Octave abort due to coding errors in +introduce the possibility of Octave crashing due to errors in the user code. For example a segmentation violation in the user's code will cause Octave to abort. @@ -1137,7 +1137,7 @@ @noindent where, as can be seen, end line of text within the help string is -terminated by @code{\n\} which is an an embedded new-line in the string +terminated by @code{\n\} which is an embedded new-line in the string together with a C++ string continuation character. Note that the final @code{\} must be the last character on the line. @@ -1259,7 +1259,7 @@ m-file. This can also be useful to allow a sample implementation of the mex-file within the Octave language itself for testing purposes. -Although we can not have multiple entry points into a single mex-file, +Although we cannot have multiple entry points into a single mex-file, we can use the @code{mexFunctionName} function to determine what name the mex-file was called with. This can be used to alter the behavior of the mex-file based on the function name. For example if