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

Diff for /gforth/doc/gforth.ds between versions 1.110 and 1.111

version 1.110, 2003/02/24 08:46:35 version 1.111, 2003/02/25 22:58:49
Line 246  Forth Words Line 246  Forth Words
 * Tokens for Words::              * Tokens for Words::            
 * Compiling words::               * Compiling words::             
 * The Text Interpreter::          * The Text Interpreter::        
   * The Input Stream::            
 * Word Lists::                    * Word Lists::                  
 * Environmental Queries::         * Environmental Queries::       
 * Files::                         * Files::                       
Line 4518  the exercises in a .fs file in the distr Line 4519  the exercises in a .fs file in the distr
 * Tokens for Words::              * Tokens for Words::            
 * Compiling words::               * Compiling words::             
 * The Text Interpreter::          * The Text Interpreter::        
   * The Input Stream::            
 * Word Lists::                    * Word Lists::                  
 * Environmental Queries::         * Environmental Queries::       
 * Files::                         * Files::                       
Line 5384  doc-cmove> Line 5386  doc-cmove>
 doc-fill  doc-fill
 doc-blank  doc-blank
 doc-compare  doc-compare
   doc-str=
   doc-str<
   doc-string-prefix?
 doc-search  doc-search
 doc--trailing  doc--trailing
 doc-/string  doc-/string
 doc-bounds  doc-bounds
   
   
 @comment TODO examples  @comment TODO examples
   
   
Line 7570  better, because the compiler knows that Line 7576  better, because the compiler knows that
 @code{create}d word can be changed.  @code{create}d word can be changed.
   
 @c ----------------------------------------------------------  @c ----------------------------------------------------------
 @node The Text Interpreter, Word Lists, Compiling words, Words  @node The Text Interpreter, The Input Stream, Compiling words, Words
 @section  The Text Interpreter  @section  The Text Interpreter
 @cindex interpreter - outer  @cindex interpreter - outer
 @cindex text interpreter  @cindex text interpreter
Line 7804  doc-save-input Line 7810  doc-save-input
 doc-restore-input  doc-restore-input
   
 doc-evaluate  doc-evaluate
   doc-query
   
   
   
Line 8071  doc-[REPEAT] Line 8078  doc-[REPEAT]
   
   
 @c -------------------------------------------------------------  @c -------------------------------------------------------------
 @node Word Lists, Environmental Queries, The Text Interpreter, Words  @node The Input Stream, Word Lists, The Text Interpreter, Words
   @section The Input Stream
   @cindex input stream
   
   @c !! integrate this better with the "Text Interpreter" section
   The text interpreter reads from the input stream, which can come from
   several sources (@pxref{Input Sources}).  Some words, in particular
   defining words, but also words like @code{'}, read parameters from the
   input stream instead of from the stack.
   
   Such words are called parsing words, because they parse the input
   stream.  Parsing words are hard to use in other words, because it is
   hard to pass program-generated parameters through the input stream.
   They also usually have an unintuitive combination of interpretation and
   compilation semantics when implemented naively, leading to various
   approaches that try to produce a more intuitive behaviour
   (@pxref{Combined words}).
   
   It should be obvious by now that parsing words are a bad idea.  If you
   want to implement a parsing word for convenience, also provide a factor
   of the word that does not parse, but takes the parameters on the stack.
   To implement the parsing word on top if it, you can use the following
   words:
   
   @c anton: these belong in the input stream section
   doc-parse
   doc-parse-word
   doc-name
   doc-word
   doc-\"-parse
   doc-refill
   
   Conversely, if you have the bad luck (or lack of foresight) to have to
   deal with parsing words without having such factors, how do you pass a
   string that is not in the input stream to it?
   
   doc-execute-parsing
   
   If you want to run a parsing word on a file, the following word should
   help:
   
   doc-execute-parsing-file
   
   @c -------------------------------------------------------------
   @node Word Lists, Environmental Queries, The Input Stream, Words
 @section Word Lists  @section Word Lists
 @cindex word lists  @cindex word lists
 @cindex header space  @cindex header space
Line 8804  doc-ud.r Line 8855  doc-ud.r
 doc-f.  doc-f.
 doc-fe.  doc-fe.
 doc-fs.  doc-fs.
   doc-f.rdp
   
 Examples of printing the number 1234.5678E23 in the different floating-point output  Examples of printing the number 1234.5678E23 in the different floating-point output
 formats are shown below:  formats are shown below:
Line 8862  doc-#> Line 8913  doc-#>
 doc-#>>  doc-#>>
   
 doc-represent  doc-represent
   doc-f>str-rdp
   doc-f>buf-rdp
   
   
 @noindent  @noindent
Line 9096  doc->float Line 9149  doc->float
 doc-accept  doc-accept
 doc-edit-line  doc-edit-line
 doc-pad  doc-pad
 @c anton: these belong in the input stream section  
 doc-parse  
 doc-word  
 doc-name  
 doc-parse-word  
 doc-\"-parse  
 doc-sword  
 doc-refill  
 @comment obsolescent words..  @comment obsolescent words..
 doc-convert  doc-convert
 doc-query  
 doc-expect  doc-expect
 doc-span  doc-span
   
Line 11493  And finally, @code{see} allows to inspec Line 11537  And finally, @code{see} allows to inspec
   
 doc-see  doc-see
 doc-xt-see  doc-xt-see
   doc-simple-see
   doc-simple-see-range
   
 @node Forgetting words, Debugging, Examining, Programming Tools  @node Forgetting words, Debugging, Examining, Programming Tools
 @subsection Forgetting words  @subsection Forgetting words
Removed from v.1.110  
changed lines
  Added in v.1.111

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