unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
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 v3
Date: Mon, 25 Nov 2024 21:56:19 +0100	[thread overview]
Message-ID: <CAA2XvwJz4_Haw+J98r2SxgoyEFDBZ9jZMzBPM6_FMQaeyBQ0kQ@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwKXRuPHmxxoQOTbqpAHLHmnfcW4UrMttHmHMZnoJVOo+Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 582 bytes --]

I just pushed this to Savannah.

On Mon, Nov 25, 2024 at 11:28 AM Mikael Djurfeldt <mikael@djurfeldt.com>
wrote:

> This is the third attempt at introducing keyword aware methods in GOOPS.
>
> What is new in v3 is that keyword arguments and default parameters to
> keyword arguments are handled correctly when using (next-method). Now only
> those keyword arguments actually present in a call get forwarded to the
> next-method.
>
> I've also committed these changes to
>
> https://github.com/mdjurfeldt/guile/tree/goops-keyword
>
> Best regards,
> Mikael
>
>

[-- Attachment #2: Type: text/html, Size: 1067 bytes --]

  reply	other threads:[~2024-11-25 20:56 UTC|newest]

Thread overview: 7+ 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
2024-11-24 22:20   ` David Pirotte
2024-11-25 10:28 ` Keywords in GOOPS methods v3 Mikael Djurfeldt
2024-11-25 20:56   ` Mikael Djurfeldt [this message]
2024-11-25 22:51     ` 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=CAA2XvwJz4_Haw+J98r2SxgoyEFDBZ9jZMzBPM6_FMQaeyBQ0kQ@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).