![](https://secure.gravatar.com/avatar/f6ddda1fabf459f90ca590f9499033c4.jpg?s=120&d=mm&r=g)
17 Jul
2008
17 Jul
'08
8:49 a.m.
"Tobias C. Rittweiler" <tcr@freebits.de> writes:
Hi all,
You'll find a small patch attached which adds some PRINT-OBJECTs for more descriptive results at the REPL; for example objects representing lambda-lists will be printed like
Thank you, committed.
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. -- \ Troels /\ Henriksen