From: David Pirotte <david@altosw.be>
To: <bug-guile@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: GOOPS - specialized make method upon user defined class 'does not work'
Date: Tue, 29 Oct 2024 01:20:32 -0300 [thread overview]
Message-ID: <20241029012032.41d1f6d3@tintin> (raw)
In-Reply-To: <20241028202700.18fbbdb1@tintin>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
> GOOPS - specialized make method upon user defined class 'does
> not work': those methods are properly defined and added to the
> make (make-instance) generic function, but not eligible as
> applicable methods ...
Actually, as the protocol states (but i somehow forgot and missed it at
re-reading ...), specialized make method first arg is (must be) a
metaclass.
I'll close the bug as soon as I receive its bug number.
Sorry for the noise,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-10-29 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 23:27 GOOPS - specialized make method upon user defined class 'does not work' David Pirotte
2024-10-29 4:20 ` David Pirotte [this message]
2024-10-29 20:22 ` bug#74073: close - not a bug David Pirotte
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=20241029012032.41d1f6d3@tintin \
--to=david@altosw.be \
--cc=bug-guile@gnu.org \
--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).