[BACK]Return to gforth.ds CVS log [TXT] [DIR] Up to [gforth] / gforth / doc

Diff for /gforth/doc/gforth.ds between versions 1.133 and 1.134

version 1.133, 2004/12/08 12:47:29 version 1.134, 2004/12/28 22:37:07
Line 3379  all of your input successfully. Now type Line 3379  all of your input successfully. Now type
   
 @example  @example
 @kbd{qwer341@key{RET}}  @kbd{qwer341@key{RET}}
 :1: Undefined word  *the terminal*:2: Undefined word
 qwer341  >>>qwer341<<<
 ^^^^^^^  Backtrace:
 $400D2BA8 Bounce  $2A95B42A20 throw 
 $400DBDA8 no.extensions  $2A95B57FB8 no.extensions 
 @end example  @end example
   
 The exact text, other than the ``Undefined word'' may differ slightly on  The exact text, other than the ``Undefined word'' may differ slightly
 your system, but the effect is the same; when the text interpreter  on your system, but the effect is the same; when the text interpreter
 detects an error, it discards any remaining text on a line, resets  detects an error, it discards any remaining text on a line, resets
 certain internal state and prints an error message. For a detailed description of error messages see @ref{Error  certain internal state and prints an error message. For a detailed
 messages}.  description of error messages see @ref{Error messages}.
   
 The text interpreter waits for you to press carriage-return, and then  The text interpreter waits for you to press carriage-return, and then
 processes your input line. Starting at the beginning of the line, it  processes your input line. Starting at the beginning of the line, it
Line 3440  command: Line 3440  command:
   
 @example  @example
 @kbd{12 dup fred dup@key{RET}}  @kbd{12 dup fred dup@key{RET}}
 :1: Undefined word  *the terminal*:3: Undefined word
 12 dup fred dup  12 dup >>>fred<<< dup
        ^^^^  Backtrace:
 $400D2BA8 Bounce  $2A95B42A20 throw 
 $400DBDA8 no.extensions  $2A95B57FB8 no.extensions 
 @end example  @end example
   
 When you press the carriage-return key, the text interpreter starts to  When you press the carriage-return key, the text interpreter starts to
Line 3845  define @code{add-two}: Line 3845  define @code{add-two}:
   
 @example  @example
 @kbd{: add-two 2 + . ;@key{RET}}  @kbd{: add-two 2 + . ;@key{RET}}
   ^^^^^^^  *the terminal*:4: Undefined word
 Error: Undefined word  : >>>add-two<<< 2 + . ;
 @end example  @end example
   
 The reason that this didn't happen is bound up in the way that @code{:}  The reason that this didn't happen is bound up in the way that @code{:}
Line 12105  A typical Gforth error message looks lik Line 12105  A typical Gforth error message looks lik
 in file included from \evaluated string/:-1  in file included from \evaluated string/:-1
 in file included from ./yyy.fs:1  in file included from ./yyy.fs:1
 ./xxx.fs:4: Invalid memory address  ./xxx.fs:4: Invalid memory address
 bar  >>>bar<<<
 ^^^  
 Backtrace:  Backtrace:
 $400E664C @@  $400E664C @@
 $400E6664 foo  $400E6664 foo
Line 12116  The message identifying the error is @co Line 12115  The message identifying the error is @co
 error happened when text-interpreting line 4 of the file  error happened when text-interpreting line 4 of the file
 @file{./xxx.fs}. This line is given (it contains @code{bar}), and the  @file{./xxx.fs}. This line is given (it contains @code{bar}), and the
 word on the line where the error happened, is pointed out (with  word on the line where the error happened, is pointed out (with
 @code{^^^}).  @code{>>>} and @code{<<<}).
   
 The file containing the error was included in line 1 of @file{./yyy.fs},  The file containing the error was included in line 1 of @file{./yyy.fs},
 and @file{yyy.fs} was included from a non-file (in this case, by giving  and @file{yyy.fs} was included from a non-file (in this case, by giving
Removed from v.1.133  
changed lines
  Added in v.1.134

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>