Mercurial > octave
changeset 24317:221f1eacd66a
doc: Remove references to filemarker function deleted in a26a8714db26.
* system.txi: Remove DOCSTRING entry for filemarker.
* debug.txi: Remove example showing usage of filemarker.
| author | Rik <rik@octave.org> |
|---|---|
| date | Sun, 26 Nov 2017 21:30:46 -0800 |
| parents | 01fc0e70d4c1 |
| children | a17862b28f0d |
| files | doc/interpreter/debug.txi doc/interpreter/system.txi |
| diffstat | 2 files changed, 3 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/interpreter/debug.txi Sun Nov 26 21:20:41 2017 -0800 +++ b/doc/interpreter/debug.txi Sun Nov 26 21:30:46 2017 -0800 @@ -133,19 +133,13 @@ @example @group -dbstop (["func1", filemarker(), "func2"]) +dbstop func1>func2 @result{} 5 @end group @end example -Note that @code{filemarker} returns the character that marks subfunctions from -the file containing them. Unless the default has been changed this character -is @samp{>}. Thus, a quicker and more normal way to set the breakpoint would -be - -@example -dbstop func1>func2 -@end example +Note that @samp{>} is the character that distinguishes subfunctions from the +m-file containing them. Another simple way of setting a breakpoint in an Octave script is the use of the @code{keyboard} function.