From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Cc: guile-devel@gnu.org
Subject: Re: i18n, gettext support?
Date: Thu, 19 Aug 2004 10:07:26 +0200 [thread overview]
Message-ID: <uw5acwrh7pd.fsf@mail.math.uni-magdeburg.de> (raw)
In-Reply-To: <87smakdjbr.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 19 Aug 2004 11:10:00 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Andreas Rottmann <a.rottmann@gmx.at> writes:
>>
>> Maybe
>> the "superfluous argument" error should be disabled when you use @*?
>
> Arguably that'd make sense, but I think common lisp says you have to
> jump to the end. (Which is why I put that in the docs, under "~*".)
Actually, from the Common Lisp HyperSpec:
| 22.3.10.2 Missing and Additional FORMAT Arguments
|
| The consequences are undefined if no arg remains for a directive
| requiring an argument. However, it is permissible for one or more
| args to remain unprocessed by a directive; such args are ignored.
So maybe the check for superfluous arguments should be disabled in
Guile (whether ~@* is used or not). It's not a very important issue,
though; I'd say it's OK do deviate from CL here if it's documented.
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-19 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 8:21 i18n, gettext support? Jan Nieuwenhuizen
2004-08-16 18:47 ` Rob Browning
2004-08-17 1:49 ` Kevin Ryde
2004-08-18 14:40 ` Jan Nieuwenhuizen
2004-08-17 14:16 ` Andreas Rottmann
2004-08-17 15:24 ` Matthias Koeppe
2004-08-18 12:54 ` Andreas Rottmann
2004-08-19 1:10 ` Kevin Ryde
2004-08-19 8:07 ` Matthias Koeppe [this message]
2004-08-20 1:17 ` Kevin Ryde
2004-08-24 17:12 ` Marius Vollmer
2004-09-01 23:31 ` Kevin Ryde
2004-08-17 22:46 ` Kevin Ryde
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=uw5acwrh7pd.fsf@mail.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=guile-devel@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).