trinque: whaack: there are a few reasons the lisp code in these published items is idiosyncratic. I'd be happy to explain why sometime.
trinque: the short version is that I wrote the classes like I were writing Java.
trinque: mostly idiosyncratic in naming, but nevertheless, not to be taken as exemplar lisp.
trinque: that'd be the problem too; I don't know where to find exemplar lisp. it seems everybody makes a horrible mess of it.
trinque: this is not to go all depressive. there are still good books to be read. Keene's Object Oriented Programming in Common Lisp is good.
trinque: There is also The Art of the Metaobject Protocol.
trinque: a woman beckons to zip up her dress, bbl!
trinque: after unzipping, of course
whaack: trinque: Thanks. I'm not at a point where I could determine what in your code is/isn't idiosyncratic. I'm not even so sure what idiosyncratic means if there is no such thing as exemplar lisp. I'll take a look through those books though, thank you.