unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Llorens <daniel.llorens@bluewin.ch>
To: 20512@debbugs.gnu.org
Subject: bug#20512: bogus warning with (format) and ~{ ~}
Date: Wed, 6 May 2015 11:16:04 +0200	[thread overview]
Message-ID: <F2337461-BB2A-4292-9ED2-85AD25737A95@bluewin.ch> (raw)


Hello,

this is with current master, I don't know what stable 2.0 does, although I don't think it's changed there.

scheme@(guile-user)> (format #t "~{~{~a~^ ~}\n~}" '((1 2) (3 4)))
;;; <stdin>:1:0: warning: "~{~{~a~^ ~}\\n~}": wrong number of `format' arguments: expected 2, got 1
1 2
3 4
$1 = #t

apparently it only happens with double nesting, e.g. triple nesting is fine:

scheme@(guile-user)> (format #t "~{~{~{~a~^:~}~^ ~}\n~}" '(((1 2) (3 4)) ((5 6) (7 8))))
1:2 3:4
5:6 7:8
$2 = #t

Regards,

	Daniel






             reply	other threads:[~2015-05-06  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  9:16 Daniel Llorens [this message]
2019-09-16 15:06 ` bug#20512: bogus warning with (format) and ~{ ~} levenson

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=F2337461-BB2A-4292-9ED2-85AD25737A95@bluewin.ch \
    --to=daniel.llorens@bluewin.ch \
    --cc=20512@debbugs.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).