Subject: bug#10522: Patch: Improve optional variable and keyword notation in manual

From: [email-masked] (Ludovic Courtès)
Date: Sat, 04 Feb 2012 00:54:02 +0100

Hello!  :-)

Andy Wingo <[email-masked]> skribis:

> On Mon 16 Jan 2012 20:46, Bake Timmons <[email-masked]> writes:
>> -@deffn {Scheme Procedure} resolve-module name [autoload=#t] [version=#f] [#:ensure=#t]
>> +@deffn {Scheme Procedure} resolve-module name [autoload=#t [version=#f]] @
>> +                          [#:ensure ensure=#t]
>
> Nesting the optional arguments in brackets can get a bit ugly.  It is
> precise but verbose.  But I suppose we should not encourage interfaces
> with many optional arguments, so perhaps it is a moot point.

Indeed.

> Also, it seems pedantic to repeat the keyword arguments (once as
> keyword, once as identifier).  Surely #:foo=bar is unambiguous?

That’s what I would think.

Perhaps the people behind [email-masked] have something to say
about this kind of thing, since there are other Lispy packages out there
with similar features?

Thanks,
Ludo’.