unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: rm@tuxteam.de
To: rixed@happyleptic.org, guile-user@gnu.org
Subject: Re: gc question
Date: Mon, 9 May 2011 11:34:21 +0200	[thread overview]
Message-ID: <20110509093421.GB14837@seid-online.de> (raw)
In-Reply-To: <20110509090542.GC16764@ccellier.rd.happyleptic.org>

On Mon, May 09, 2011 at 11:05:42AM +0200, rixed@happyleptic.org wrote:
> -[ Mon, May 09, 2011 at 11:14:11AM +0200, rm@tuxteam.de ]----
> > am I correct in assuming that the return value from
> > scm_from_locale_keyword("unknown"); 
> > won't ever be garbage collected od do I have to protect 
> > it?
> 
> >From an IRC discussion some time ago:
> 
> 16:11 < rixed> BTW, is it required to scm_gc_protect_object a symbol ?
> 16:11 < civodul> no
> 16:13 < rixed> civodul: even with guile 1.8?
> 16:14 < civodul> in 1.8 you have to protect it
> 16:14 < civodul> but you should use the snarfing macros
> 16:14 < civodul> SCM_SYMBOL and SCM_GLOBAL_SYMBOL
> 16:14 < rixed> civodul: well, probably, but that's my first project using guile so I'd rather do it by hand - I find it actualy simpler :)
> 16:14 < dsmith-work> Wasn't there some recent changes that allow symbols to be gc'd?
> 16:16 < civodul> rixed: ok; so if you want both 1.8 and 1.6, then always scm_gc_protect_object
> 16:16 < civodul> s/1.6/2.0/
> 16:29 < rixed> civodul: will do. thanx!
> 
> So I'd say it depends on the target guile version.

But that talk was about symbols (which might well go aut of scope), im
asking about _keywords_ whose semantics seem to be different.


 Cheers, RalfD




  reply	other threads:[~2011-05-09  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09  9:14 gc question rm
2011-05-09  9:05 ` rixed
2011-05-09  9:34   ` rm [this message]
2011-05-09  9:12     ` rixed
2011-05-09 10:00 ` Andy Wingo

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=20110509093421.GB14837@seid-online.de \
    --to=rm@tuxteam.de \
    --cc=guile-user@gnu.org \
    --cc=rixed@happyleptic.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).