Mercurial > octave-nkf
changeset 6606:2c19eaa2c6f7
[project @ 2007-05-07 17:09:38 by jwe]
| author | jwe |
|---|---|
| date | Mon, 07 May 2007 17:09:38 +0000 |
| parents | 376b71574728 |
| children | 98724cae69c7 |
| files | doc/faq/Octave-FAQ.texi doc/interpreter/dynamic.txi scripts/ChangeLog scripts/sparse/spy.m |
| diffstat | 4 files changed, 15 insertions(+), 17 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/faq/Octave-FAQ.texi Wed May 02 16:15:28 2007 +0000 +++ b/doc/faq/Octave-FAQ.texi Mon May 07 17:09:38 2007 +0000 @@ -69,7 +69,7 @@ command history is saved, so that commands entered during previous sessions are not lost. -The Octave distribution includes a 500+ page Texinfo manual. Access +The Octave distribution includes a 550+ page Texinfo manual. Access to the complete text of the manual is available via the help command @c really, the *complete* text? at the Octave prompt. @@ -198,9 +198,9 @@ @item better support for both msvc and mingw -@item many many other minor features and compatibility changes +@item a fully compatiable MEX interface -@item a fully compatiable MEX interface +@item many many other minor features and compatibility changes @end itemize @@ -592,16 +592,10 @@ @item Octave takes a long time to find symbols. -Octave is probably spending this time recursively searching directories for -function files. Check the value of the internal variable LOADPATH, -accessible through the Octave fucntion @code{path}. For those -elements that end in @samp{//}, do any name a very large directory tree? -Does it contain directories that have a mixture of files and -directories? In order for the recursive directory searching code to -work efficiently, directories that are to be searched recursively should -have either function files only, or subdirectories only, but not a -mixture of both. Check to make sure that Octave's standard set of -function files is installed this way. +Octave uses the @code{genpath} function to recursively add directories +to the list of directories searched for function files. Check the list +of directories with the @code{path} command. If the path list is very +long check your use of the @code{genpath} function. @end itemize @node How do I ...?
--- a/doc/interpreter/dynamic.txi Wed May 02 16:15:28 2007 +0000 +++ b/doc/interpreter/dynamic.txi Mon May 07 17:09:38 2007 +0000 @@ -1099,7 +1099,7 @@ The major issue is that the help string will typically be longer than a single line of text, and so the formatting of long help strings need to -be taken into account. There are several manner in which to happen this +be taken into account. There are several manner in which to treat this issue, but the most common is illustrated in the following example @example @@ -1130,9 +1130,9 @@ and demonstration code. This is equally a requirement for oct-files. Furthermore the test and demonstration code must be included in a comment block of the compiled code to avoid it being interpreted by -the compiler. Finally, he Octave test and demonstration code must have +the compiler. Finally, the Octave test and demonstration code must have access to the source code of the oct-file and not just the compiled code -as th<e tests are stripped from the compiled code. An example in an +as the tests are stripped from the compiled code. An example in an oct-file might be @example
--- a/scripts/ChangeLog Wed May 02 16:15:28 2007 +0000 +++ b/scripts/ChangeLog Mon May 07 17:09:38 2007 +0000 @@ -1,3 +1,7 @@ +2007-05-07 David Bateman <dbateman@free.fr> + + * sparse/spy.m: Reverse Y axis for new graphics code. + 2007-05-02 John W. Eaton <jwe@octave.org> * plot/__go_draw_axes__.m: Convert NA to NaN before writing.