internals.texi

[Luc Teirlinck <teirllm@dms.auburn.edu>]

If there is pure space overflow, the warning messages refer to the
node Pure Storage in the Elisp manual.  But that node nowhere mentions
the problems that pure space overflow causes (a very bad memory leak).

I propose the following minor changes to internals.texi.  I can
install if desired.

===File ~/internals.texi-diff===============================
*** internals.texi	10 May 2006 20:55:37 -0500	1.49
--- internals.texi	28 May 2006 17:52:17 -0500	
***************
*** 160,166 ****
  the part that didn't fit.  If that happens, you should increase the
  compilation parameter @code{PURESIZE} in the file
  @file{src/puresize.h} and rebuild Emacs, even though the resulting
! image will work.  Such an overflow normally won't happen unless you
  try to preload additional libraries or add features to the standard
  ones.  Emacs will display a warning about the overflow when it
  starts.
--- 160,167 ----
  the part that didn't fit.  If that happens, you should increase the
  compilation parameter @code{PURESIZE} in the file
  @file{src/puresize.h} and rebuild Emacs, even though the resulting
! image will work: garbage collection is disabled in this situation,
! causing a memory leak.  Such an overflow normally won't happen unless you
  try to preload additional libraries or add features to the standard
  ones.  Emacs will display a warning about the overflow when it
  starts.
***************
*** 348,353 ****
--- 349,358 ----
  object consists of a header and the storage for the string text
  itself; the latter is only allocated when the string is created.)
  @end table
+ 
+ If there was overflow in pure space (see the previous section),
+ @code{garbage-collect} returns @code{nil}, because a real garbage
+ collection can not be done in this situation.
  @end deffn
  
  @defopt garbage-collection-messages
============================================================