[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: un-deprecating CL
From: |
Richard Stallman |
Subject: |
Re: un-deprecating CL |
Date: |
Mon, 17 Sep 2007 18:25:03 -0400 |
> `every', `substitute', `find' and `subsetp' have the ugly CL keyword
> arguments, so I don't want to add them.
It isn't clear to me what exactly is so bad about keyword arguments,
or what alternative (if any) you have in mind for dealing sensibly
with functions accepting more than one or two optional arguments.
The fact that they accept so many optional arguments is one thing I
don't like about them. It is too much complexity. If you showed me
lots of places that wanted to call a simple `union' function, I'd say
sure. But adding a CL-style `union' function is another story.
- Re: un-deprecating CL, (continued)
- Re: un-deprecating CL, Richard Stallman, 2007/09/17
- Re: un-deprecating CL, David O'Toole, 2007/09/17
- Re: un-deprecating CL, Richard Stallman, 2007/09/17
- Re: un-deprecating CL, Lennart Borgman (gmail), 2007/09/18
- Re: un-deprecating CL, Richard Stallman, 2007/09/18
- Re: un-deprecating CL, David O'Toole, 2007/09/18
- Re: un-deprecating CL, Richard Stallman, 2007/09/19
- Re: un-deprecating CL, David O'Toole, 2007/09/19
- Re: un-deprecating CL, David O'Toole, 2007/09/17
- Re: un-deprecating CL, Richard Stallman, 2007/09/17
- Re: un-deprecating CL,
Richard Stallman <=
- Re: un-deprecating CL, Johan Bockgård, 2007/09/18
- Re: un-deprecating CL, David O'Toole, 2007/09/16
- Re: un-deprecating CL, Richard Stallman, 2007/09/16
- Re: un-deprecating CL, David O'Toole, 2007/09/16
- Re: un-deprecating CL, Eli Zaretskii, 2007/09/16