unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Unintentional conflict in define-immutable-type?
Date: Fri, 27 Nov 2015 15:33:22 -0600	[thread overview]
Message-ID: <8737vrcel9.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87mvtzuoia.fsf@netris.org>

Mark H Weaver <mhw@netris.org> writes:

> I guess that wouldn't work.  After (define-immutable-type <foo> ...),
> it's important that <foo> remain bound to the RTD in the module where
> 'define-immutable-type' was evaluated.  The other procedures defined by
> 'define-immutable-type' refer to <foo> and rely on it being bound to the
> RTD.

Ahh, right.

So I suppose if you want <foo> as the goops name, then you really do
just have to choose something other than foo for the constructor within
the module.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4



  reply	other threads:[~2015-11-27 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  4:25 Unintentional conflict in define-immutable-type? Rob Browning
2015-11-19 20:32 ` Mark H Weaver
2015-11-22  2:12   ` Rob Browning
2015-11-27 21:21     ` Mark H Weaver
2015-11-27 21:33       ` Rob Browning [this message]
2015-11-19 20:40 ` Ludovic Courtès
2015-11-27 18:34   ` Rob Browning
2015-11-27 20:37     ` Ludovic Courtès
2015-11-27 21:24   ` Rob Browning

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=8737vrcel9.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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).