[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: So what happens now?

This page is part of the web mail archives of SRFI 89 from before July 7th, 2015. The new archives for SRFI 89 contain all messages, not just those from before July 7th, 2015.



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16-Nov-06, at 7:44 AM, felix winkelmann wrote:


[This gratuitous text inserted by mailing list moderator to keep this
message from being classified as a request for help by the list
manager.]

???

--
http://galinha.ucpel.tche.br:8081/blog/blog.ssp

Here are the things I plan to change:

1) Change the title of the SRFI to "Optional positional and named
   parameters".

2) Remove overloading of "lambda" and "define", i.e. the forms will
   be called "lambda-opt" and "define-opt".  This will promote the
   use of optional parameters (users don't have to wait for their
   Scheme implementations to overload lambda and define).  I strongly
   recommend implementors to overload lambda and define so that
   somewhere down the line code can drop the "-opt".

3) In order to promote the use of named parameters I'm thinking of
   adding a "define-keywords" form to define keywords.  This will be
   used like this:

     (define-keywords foo: bar: baz:)

   On Scheme implementations which support SRFI 88 (Keyword objects)
   it will expand to

     (begin)

   On Scheme implementation which do not support SRFI 88 it will
   expand to

     (begin
       (define foo: 'foo:)
       (define bar: 'bar:)
       (define baz: 'baz:))

   And (keyword? obj) will be #t if obj is a symbol ending with
   a colon.  All arguments of define-keywords must be "keywords".

Marc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFXIeI//V9Zc2T/v4RAlrNAKCL16KUb/4hFqgW5qFKHPcmn9liWwCfVPFi
J172YIgSvxfoJo+9+7/s1Zc=
=tdGK
-----END PGP SIGNATURE-----