--- gforth/kernel/quotes.fs	2000/09/23 15:47:12	1.3
+++ gforth/kernel/quotes.fs	2001/05/04 07:41:03	1.4
@@ -22,21 +22,26 @@
 
 require ./vars.fs
 
-create s"-buffer /line chars allot
+\ create s"-buffer /line chars allot
 has? compiler 0= 
 [IF] : s" [ELSE] :noname [THEN]
-	[char] " parse
-    	/line min >r s"-buffer r@ cmove
-    	s"-buffer r> ;
+	[char] " parse save-mem ;
+\    	/line min >r s"-buffer r@ cmove
+\    	s"-buffer r> ;
 has? compiler [IF]
 :noname [char] " parse postpone SLiteral ;
 interpret/compile: S" ( compilation 'ccc"' -- ; run-time -- c-addr u )	\ core,file	s-quote
   \G Compilation: Parse a string @i{ccc} delimited by a @code{"}
   \G (double quote). At run-time, return the length, @i{u}, and the
   \G start address, @i{c-addr} of the string. Interpretation: parse
-  \G the string as before, and return @i{c-addr}, @i{u}. The
-  \G string is stored in a temporary buffer which may be overwritten
-  \G by subsequent uses of @code{S"}.
+  \G the string as before, and return @i{c-addr}, @i{u}. Gforth
+  \G @code{allocate}s the string. The resulting memory leak is usually
+  \G not a problem; the exception is if you create strings containing
+  \G @code{S"} and @code{evaluate} them; then the leak is not bounded
+  \G by the size of the interpreted files and you may want to
+  \G @code{free} the strings.  ANS Forth only guarantees one buffer of
+  \G 80 characters, so in standard programs you should assume that the
+  \G string lives only until the next @code{s"}.
 [THEN]
 
 :noname    [char] " parse type ;