From: Rob Browning <rlb@defaultvalue.org>
To: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: Unintentional conflict in define-immutable-type?
Date: Fri, 27 Nov 2015 15:24:08 -0600 [thread overview]
Message-ID: <87610ncf0n.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87oaepiuyu.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> This is expected. The macro, like that of SRFI-9, creates one binding
> for the record-type descriptor, one for the constructor, one for the
> predicate, and one for the accessor. Since the first two have the
> same name, it Doesn’t Work.
OK, so I just wasn't paying close enough attention.
If I really do want to have <foo> for the goops class, and don't want to
patch things up afterward, I could also just rename the default
constructor, i.e.:
(use-modules (srfi srfi-9 gnu))
(use-modules (oop goops))
(define-immutable-record-type foo
(make-foo x)
foo?
(x x))
(display foo) (newline)
(display <foo>) (newline)
Whether or not that's a good idea is of course a different question...
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
prev parent reply other threads:[~2015-11-27 21:24 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
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 [this message]
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=87610ncf0n.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).