Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> If someone can point a finger at a place where the &WHOLE is given
> licence to signal an error should it appear in an ordinary
> lambda-list, I'd be quite happy.
(sorry for top-posting, I was not subscribed to the list before)
CLHS section 3.4.1 states that "Implementations are free to provide
additional lambda list keywords. For a list of all lambda list keywords
used by the implementation, see lambda-list-keywords.". IMHO, if you
really want to take the spec literally, the current state of SBCL might be
considered correct, since it provides two lambda list keywords,
&environment and &whole in ordinary lambda lists, both are present in
lambda-list-keywords, and their implementation-specified behavior is that
they signal the SB-INT:BUG condition. Although this is IMHO not too
appropriate. What do you think about this simple patch?