unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: SCM_STRING_CHARS is deprecated. See the manual for alternatives.
Date: Fri, 11 Aug 2006 10:30:56 +1000	[thread overview]
Message-ID: <87lkpwp0zj.fsf@zip.com.au> (raw)
In-Reply-To: <44DAAEC6.7080007@gnu.org> (Bruce Korb's message of "Wed, 09 Aug 2006 20:57:58 -0700")

Bruce Korb <bkorb@gnu.org> writes:
>
>   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!

That para sounds a bit unnecessary, doesn't it :).

>   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::.

Not sure if that's true any more either.  Is the "remembering"
protection enough now?


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


  parent reply	other threads:[~2006-08-11  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  3:57 SCM_STRING_CHARS is deprecated. See the manual for alternatives Bruce Korb
2006-08-10  8:05 ` Neil Jerram
2006-08-11  0:30 ` Kevin Ryde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-16 21:46 Bruce Korb
2006-09-23 10:19 ` Neil Jerram
2006-09-23 17:04   ` Bruce Korb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lkpwp0zj.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).