public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: kawa <kawa@sourceware.org>
Subject: Using #!optional, #!rest, and #!key together
Date: Wed, 19 Apr 2017 15:22:00 -0000	[thread overview]
Message-ID: <28671.1492615372@vereq.eip10.org> (raw)

Some background: I'd like to define a procedure that accepts a few
keyword-arguments as well as a variable number of non-keyword arguments
(both required and optional).  So, I'm looking at using #!optional,
#!rest, and #!key together but am confused by the specification.

Which brings me to my main, somewhat vague, question:

  1.   What is a good way to achieve the above (in Kawa)?  

My more specific questions follow.

  2. When a lambda uses #!key, my reading of the specification seems to
     require an even number of actual arguments following the
     required+optional actual arguments in a corresponding invocation,
     even if there is a #!rest. Is that really the case?

  3. To be even more specific, given

       (define (test-args a b #!optional c d #!rest e
                          #!key (f 'vf) (g 'vg))
         (list a b c d e f g))

     is it true that the first of the following is OK but the second is
     an error? 

       (test-args 1 2 3 4 5 6 f: 7 g: 8)

       (test-args 1 2 3 4 5 f: 6 g: 7)

Kawa doesn't flag an error (which is fine, I understand), but binds f
and g to 7 and 8 in the first case, and to their default values vf and
vg in the second case, so it does seem to treat them quite differently.

My confusion is probably not specific to Kawa, as the relevant text in
the manual is probably essentially from the DSSSL spec (based on similar
text in other manuals).  However, Chicken and Bigloo (just the ones I
looked at) seem to have implemented extensions that work around the
above issues and I'm trying to figure out a suitable strategy using
Kawa.

I'm guessing others have encountered similar situations and have some
good solutions, which I would love to hear.

Regards,

-chaw

             reply	other threads:[~2017-04-19 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 15:22 Sudarshan S Chawathe [this message]
     [not found] <792B84DD-C6FA-4C57-9241-4FC0E59A9F3C@bothner.com>
2017-04-23 19:24 ` Sudarshan S Chawathe
2017-04-23 19:29   ` Per Bothner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28671.1492615372@vereq.eip10.org \
    --to=chaw@eip10.org \
    --cc=kawa@sourceware.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).