From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: guile-user <guile-user@gnu.org>,
guile-devel <guile-devel@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>, "Andy Wingo" <wingo@pobox.com>
Cc: Jan Nieuwenhuizen <janneke@gnu.org>, Tomas Volf <~@wolfsden.cz>,
Maxime Devos <maximedevos@telenet.be>,
David Pirotte <david@altosw.be>
Subject: Re: Keywords in GOOPS methods v2
Date: Sun, 24 Nov 2024 18:54:28 +0100 [thread overview]
Message-ID: <CAA2Xvw+GRumm7t9FtaepDyX_iANLyNxnZuv2ckJA+Tid++fhhg@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwLq26b6UujtUU=pFmh88hgpa_9DWbN87XzDza2fqzGHzA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
Ah... I forgot to complete parse-keyword-formals, which is currently only
rudimentary and doesn't compose the correct argument list for (next-method).
There will be a version 3...
On Sun, Nov 24, 2024 at 3:43 PM Mikael Djurfeldt <mikael@djurfeldt.com>
wrote:
> Guile maintainers might want to consider if we should time this kind of
> change in the API with a particular release. For my part, I think we could
> just add it.
>
> On Sun, Nov 24, 2024 at 3:40 PM Mikael Djurfeldt <mikael@djurfeldt.com>
> wrote:
>
>> This is my second attempt at introducing keyword aware methods in GOOPS.
>>
>> I was split but finally decided to go with keeping keyword non-aware
>> define-method and method and introducing keyword aware new syntax method*
>> and define-method*. Arguments are:
>>
>> 1. It preserves simplicity in method and define-method such that other
>> implementations (like guile-hoot) can choose to only define these (and
>> possibly provide something like Mark's macro doe define-method*).
>> 2. It aligns with lambda* and define*.
>> 3. It is somewhat better at protecting backward compatibility.
>> 4. It preserves the option to also in the internal implementation use
>> something like Mark's macro once this gives equal performance.
>>
>> I've also committed these changes to
>>
>> https://github.com/mdjurfeldt/guile/tree/goops-keyword
>>
>> I'm going to start documenting this now and will then commit it to the
>> Guile repo.
>>
>> Best regards,
>> Mikael
>>
>>
[-- Attachment #2: Type: text/html, Size: 2371 bytes --]
prev parent reply other threads:[~2024-11-24 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 14:40 Keywords in GOOPS methods v2 Mikael Djurfeldt
2024-11-24 14:43 ` Mikael Djurfeldt
2024-11-24 17:54 ` Mikael Djurfeldt [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=CAA2Xvw+GRumm7t9FtaepDyX_iANLyNxnZuv2ckJA+Tid++fhhg@mail.gmail.com \
--to=mikael@djurfeldt.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=janneke@gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
--cc=wingo@pobox.com \
--cc=~@wolfsden.cz \
/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).