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

Diff for /gforth/Attic/gforth.ds between versions 1.5 and 1.7

version 1.5, 1995/01/12 18:37:51 version 1.7, 1995/01/24 17:31:22
Line 428  unwary (e.g., floating point addition is Line 428  unwary (e.g., floating point addition is
 for the wary. You should not use them unless you know what you are doing  for the wary. You should not use them unless you know what you are doing
 or you don't care that the results you get are totally bogus. If you  or you don't care that the results you get are totally bogus. If you
 want to learn about the problems of floating point numbers (and how to  want to learn about the problems of floating point numbers (and how to
 avoid them), you might start with @cite{Goldberg, What every computer  avoid them), you might start with @cite{David (?) Goldberg, What Every
 scientist should know about floating-point numbers, Computing Surveys  Computer Scientist Should Know About Floating-Point Arithmetic, ACM
 ?}.  Computing Surveys 23(1):5@minus{}48, March 1991}.
   
 doc-f+  doc-f+
 doc-f-  doc-f-
Line 449  doc-fexpm1 Line 449  doc-fexpm1
 doc-fln  doc-fln
 doc-flnp1  doc-flnp1
 doc-flog  doc-flog
   doc-falog
 doc-fsin  doc-fsin
 doc-fcos  doc-fcos
 doc-fsincos  doc-fsincos
Line 800  Therefore we recommend avoiding using @c Line 801  Therefore we recommend avoiding using @c
 @var{n}. One alternative is @code{@var{n} S+LOOP}, where the negative  @var{n}. One alternative is @code{@var{n} S+LOOP}, where the negative
 case behaves symmetrical to the positive case:  case behaves symmetrical to the positive case:
   
 @code{-2 0 ?DO  i .  -1 +LOOP}  prints @code{0 -1}  @code{-2 0 ?DO  i .  -1 S+LOOP}  prints @code{0 -1}
   
 @code{-1 0 ?DO  i .  -1 +LOOP}  prints @code{0}  @code{-1 0 ?DO  i .  -1 S+LOOP}  prints @code{0}
   
 @code{ 0 0 ?DO  i .  -1 +LOOP}  prints nothing  @code{ 0 0 ?DO  i .  -1 S+LOOP}  prints nothing
   
 The loop is terminated when the border between @var{limit@minus{}sgn(n)} and  The loop is terminated when the border between @var{limit@minus{}sgn(n)} and
 @var{limit} is crossed. However, @code{S+LOOP} is not part of the ANS  @var{limit} is crossed. However, @code{S+LOOP} is not part of the ANS
Line 884  The standard does not allow using @code{ Line 885  The standard does not allow using @code{
 every @code{?DO} etc. there is exactly one @code{UNLOOP} on any path  every @code{?DO} etc. there is exactly one @code{UNLOOP} on any path
 through the definition (@code{LOOP} etc. compile an @code{UNLOOP} on the  through the definition (@code{LOOP} etc. compile an @code{UNLOOP} on the
 fall-through path). Also, you have to ensure that all @code{LEAVE}s are  fall-through path). Also, you have to ensure that all @code{LEAVE}s are
 resolved (by using one of the loop-ending words or @code{UNDO}).  resolved (by using one of the loop-ending words or @code{DONE}).
   
 Another group of control structure words are  Another group of control structure words are
   
Line 1037  locals are initialized with values from Line 1038  locals are initialized with values from
 Currently there is no way to define locals with user-defined data  Currently there is no way to define locals with user-defined data
 structures, but we are working on it.  structures, but we are working on it.
   
 GNU Forth allows defining locals everywhere in a colon definition. This poses the following questions:  GNU Forth allows defining locals everywhere in a colon definition. This
   poses the following questions:
   
 @menu  @menu
 * Where are locals visible by name?::    * Where are locals visible by name?::  
Removed from v.1.5  
changed lines
  Added in v.1.7

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