doco remembering versus SCM_STRING_CHARS

* doco remembering versus SCM_STRING_CHARS
@ 2003-06-12  1:29 Kevin Ryde
  2003-06-12 14:04 ` Marius Vollmer
  0 siblings, 1 reply; 2+ messages in thread
From: Kevin Ryde @ 2003-06-12  1:29 UTC (permalink / raw)


[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

Is it true the the scm_remember_upto_here_1 stuff applies also to
SCM_STRING_CHARS and friends?

        * data-rep.texi (Vector Data): For SCM_VECTOR_BASE, SCM_STRING_CHARS
        and SCM_SYMBOL_CHARS, cross reference "Remembering During Operations".

Text:

   Note that `SCM_VECTOR_BASE', `SCM_STRING_CHARS' and
`SCM_SYMBOL_CHARS' return pointers to data within the respective
object.  Care must be taken that the object is not garbage collected
while that data is still being accessed.  This is the same as for a
smob, *Note Remembering During Operations::.



[-- Attachment #2: data-rep.texi.remembering-arrays.diff --]
[-- Type: text/plain, Size: 645 bytes --]

--- data-rep.texi.~1.11.~	2003-06-12 09:07:53.000000000 +1000
+++ data-rep.texi	2003-06-12 11:26:01.000000000 +1000
@@ -875,6 +875,12 @@
 There are also a few magic values stuffed into memory before a symbol's
 characters, but you don't want to know about those.  What cruft!
 
+Note that @code{SCM_VECTOR_BASE}, @code{SCM_STRING_CHARS} and
+@code{SCM_SYMBOL_CHARS} return pointers to data within the respective
+object.  Care must be taken that the object is not garbage collected
+while that data is still being accessed.  This is the same as for a
+smob, @xref{Remembering During Operations}.
+
 
 @node Procedures
 @subsubsection Procedures

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread