Diff for /gforth/doc/gforth.ds between versions 1.201 and 1.202

version 1.201, 2008/11/13 22:37:02 version 1.202, 2008/12/25 21:20:31
Line 12293  c-library lseek-lib Line 12293  c-library lseek-lib
 end-c-library  end-c-library
 @end example  @end example
   
 The effect of giving such a name to the interface is that the  The effect of giving such a name to the interface is that the names of
 generated files will contain that name, and when you use the interface  the generated files will contain that name, and when you use the
 a second time, it will use the existing files instead of generating  interface a second time, it will use the existing files instead of
 and compiling them again, saving you time.  Note that even if you  generating and compiling them again, saving you time.  Note that even
 change the declarations, the old (stale) files will be used, probably  if you change the declarations, the old (stale) files will be used,
 leading to errors.  So, during development of the declarations we  probably leading to errors.  So, during development of the
 recommend not using @code{c-library}.  declarations we recommend not using @code{c-library}.  Normally these
   files are cached in @file{$HOME/.gforth/libcc-named}, so by deleting
   that directory you can get rid of stale files.
   
   Note that you should use @code{c-library} before everything else
   having anything to do with that library, as it resets some setup
   stuff.  The idea is that the typical use is to put each
   @code{c-library}...@code{end-library} unit in its own file, and to be
   able to include these files in any order.
   
 Note that the library name is not allocated in the dictionary and  Note that the library name is not allocated in the dictionary and
 therefore does not shadow dictionary names.  It is used in the file  therefore does not shadow dictionary names.  It is used in the file

Removed from v.1.201  
changed lines
  Added in v.1.202


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