[mcclim-devel] Re: [PATCH] Drei: adding some PRINT-OBJECTs for lambda-list related objects.

Troels Henriksen <athas@sigkill.dk> writes:

"Tobias C. Rittweiler" <tcr@freebits.de> writes:

...

I'm thinking of splitting out, and extending the lambda-list stuff into a standalone library. Now I wonder why all the lambda-list relevant classes only define reader methods for their slots. Is there some intentional purpose behind this functional design, or is it just this way because of KISS and YAGNI?

I like immutable data structures for this kind of stuff. The lambda list frobbing interface is loosely based on CL pathnames.

How can you currently rename a parameter in a lambda-list? -T.