Re: un-deprecating CL

[Richard Stallman]

    > `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.