unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Christopher Lam <christopher.lck@gmail.com>
Cc: 38617-done@debbugs.gnu.org
Subject: bug#38617: should internal defines be callable with incorrect number of args?
Date: Sun, 12 Jan 2020 21:52:20 +0100	[thread overview]
Message-ID: <87blr8o0sb.fsf@pobox.com> (raw)
In-Reply-To: <CAKVAZZLUEYVTTG5fx-8WiAbHHgRJj46942_K_KDCuMeo6Lhqqw@mail.gmail.com> (Christopher Lam's message of "Sun, 15 Dec 2019 01:02:41 +0000")

On Sun 15 Dec 2019 02:02, Christopher Lam <christopher.lck@gmail.com> writes:

> See snippet below. 
> IMHO the second call to add1 should fail. On guile-2.2.6 it does not error out.
> On guile-2.0 it does throw error (as I think it should).
> Is this intentional?

OMG what an embarrassing bug!  Thank you for finding and reporting it!
Fixed on 2.2 and master.

Andy





      reply	other threads:[~2020-01-12 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15  1:02 bug#38617: should internal defines be callable with incorrect number of args? Christopher Lam
2020-01-12 20:52 ` Andy Wingo [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=87blr8o0sb.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=38617-done@debbugs.gnu.org \
    --cc=christopher.lck@gmail.com \
    /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).