From: Maxime Devos <maximedevos@telenet.be>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: 49311@debbugs.gnu.org
Subject: bug#49311: (null?) cannot be compiled (error from (language typs types))
Date: Thu, 01 Jul 2021 13:47:14 +0200 [thread overview]
Message-ID: <a6f4472be3cc07e513711fcb0c4fc2128c6eed8d.camel@telenet.be> (raw)
In-Reply-To: <87lf6q5kcn.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
Dr. Arne Babenhauserheide schreef op do 01-07-2021 om 13:44 [+0200]:
> Maxime Devos <maximedevos@telenet.be> writes:
> > scheme@(guile-user)> (null?)
> > ;;; <stdin>:1:0: warning: possibly wrong number of arguments to `null?'
>
> This is a correct warning: null? requires an argument (the list to check
> for emptyness). The path forward from here is to find out why null? does
> not receive an argument.
Yes, the warning is correct. I wasn't referring to the warning, but to the compile
error.
scheme@(guile-user)> (null?)
;;; [the warning]
While compiling expression:
Wrong number of arguments to #<procedure 7fad2ea94660 at language/cps/types.scm:609:0 (in succ param val)>
^^^ this error
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2021-07-01 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 7:59 bug#49311: (null?) cannot be compiled (error from (language typs types)) Maxime Devos
2021-07-01 11:44 ` Dr. Arne Babenhauserheide
2021-07-01 11:47 ` Maxime Devos [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=a6f4472be3cc07e513711fcb0c4fc2128c6eed8d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49311@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).