comparison src/debug.cc @ 9039:51dc9691f23f

Cleanup documentation files errors.texi, debug.texi, io.texi Spellcheck Stylecheck
author Rik <rdrider0-list@yahoo.com>
date Sun, 22 Mar 2009 13:14:15 -0700
parents eb63fbe60fab
children 94ae487acd1b
comparison
equal deleted inserted replaced
9038:fca0dc2fb042 9039:51dc9691f23f
497 @table @code\n\ 497 @table @code\n\
498 @item func\n\ 498 @item func\n\
499 String representing the function name. When already in debug\n\ 499 String representing the function name. When already in debug\n\
500 mode this should be left out and only the line should be given.\n\ 500 mode this should be left out and only the line should be given.\n\
501 @item line\n\ 501 @item line\n\
502 Line number you would like the breakpoint to be set on. Multiple\n\ 502 Line number you would like the breakpoint to be set on. Multiple\n\
503 lines might be given as separate arguments or as a vector.\n\ 503 lines might be given as separate arguments or as a vector.\n\
504 @end table\n\ 504 @end table\n\
505 \n\ 505 \n\
506 The rline returned is the real line that the breakpoint was set at.\n\ 506 The rline returned is the real line that the breakpoint was set at.\n\
507 @seealso{dbclear, dbstatus, dbstep}\n\ 507 @seealso{dbclear, dbstatus, dbstep}\n\
529 @table @code\n\ 529 @table @code\n\
530 @item func\n\ 530 @item func\n\
531 String representing the function name. When already in debug\n\ 531 String representing the function name. When already in debug\n\
532 mode this should be left out and only the line should be given.\n\ 532 mode this should be left out and only the line should be given.\n\
533 @item line\n\ 533 @item line\n\
534 Line number where you would like to remove the breakpoint. Multiple\n\ 534 Line number where you would like to remove the breakpoint. Multiple\n\
535 lines might be given as separate arguments or as a vector.\n\ 535 lines might be given as separate arguments or as a vector.\n\
536 @end table\n\ 536 @end table\n\
537 No checking is done to make sure that the line you requested is really\n\ 537 No checking is done to make sure that the line you requested is really\n\
538 a breakpoint. If you get the wrong line nothing will happen.\n\ 538 a breakpoint. If you get the wrong line nothing will happen.\n\
539 @seealso{dbstop, dbstatus, dbwhere}\n\ 539 @seealso{dbstop, dbstatus, dbwhere}\n\
540 @end deftypefn") 540 @end deftypefn")
541 { 541 {
542 octave_value retval; 542 octave_value retval;
543 std::string symbol_name = ""; 543 std::string symbol_name = "";
992 DEFUN (dbstep, args, , 992 DEFUN (dbstep, args, ,
993 "-*- texinfo -*-\n\ 993 "-*- texinfo -*-\n\
994 @deftypefn {Command} {} dbstep @var{n}\n\ 994 @deftypefn {Command} {} dbstep @var{n}\n\
995 @deftypefnx {Command} {} dbstep in\n\ 995 @deftypefnx {Command} {} dbstep in\n\
996 @deftypefnx {Command} {} dbstep out\n\ 996 @deftypefnx {Command} {} dbstep out\n\
997 In debugging mode, execute the next @var{n} lines of code. If @var{n} is\n\ 997 In debugging mode, execute the next @var{n} lines of code. If @var{n} is\n\
998 omitted execute the next line of code. If the next line of code is itself\n\ 998 omitted execute the next line of code. If the next line of code is itself\n\
999 defined in terms of an m-file remain in the existing function.\n\ 999 defined in terms of an m-file remain in the existing function.\n\
1000 \n\ 1000 \n\
1001 Using @code{dbstep in} will cause execution of the next line to step into\n\ 1001 Using @code{dbstep in} will cause execution of the next line to step into\n\
1002 any m-files defined on the next line. Using @code{dbstep out} with cause\n\ 1002 any m-files defined on the next line. Using @code{dbstep out} with cause\n\
1003 execution to continue until the current function returns.\n\ 1003 execution to continue until the current function returns.\n\
1004 @seealso{dbcont, dbquit}\n\ 1004 @seealso{dbcont, dbquit}\n\
1005 @end deftypefn") 1005 @end deftypefn")
1006 { 1006 {
1007 if (Vdebugging) 1007 if (Vdebugging)