From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org
Subject: Re: unhandled keywords to goops "make" should signal errors
Date: 24 Apr 2002 20:36:25 +0200 [thread overview]
Message-ID: <87ofg9ndue.fsf@zagadka.ping.de> (raw)
In-Reply-To: <15498.49326.697620.427859@winona.neilvandyke.org>
"Neil W. Van Dyke" <nwv@neilvandyke.org> writes:
> Currently (latest Guile 1.5.4 from CVS), keyword arguments to the Goops
> "make" method that are not handled do not generate errors.
>
> Unless I misunderstand the way that Goops is to be used, I think that
> the default behavior should be to consider unhandled keyword arguments
> invalid.
Yep. I recorded this as bug 'unhandled-keyargs-should-error'.
Thanks!
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2002-04-24 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15498.49326.697620.427859@winona.neilvandyke.org>
2002-03-28 4:06 ` unhandled keywords to goops "make" should signal errors Thien-Thi Nguyen
[not found] ` <15522.49014.788932.395068@winona.neilvandyke.org>
2002-03-28 8:19 ` Thien-Thi Nguyen
2002-04-24 18:36 ` Marius Vollmer [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=87ofg9ndue.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@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).