Re: [clisp-list] does describe/describe-object conform to clhs?

[Tomas Z. <zel...@gm...>]

On 7/24/06, Sam Steingold <sd...@po...> wrote:
> > * Tomas Zellerin <mryyreva@tznvy.pbz> [2006-07-24 15:00:03 +0200]:
> >
> > Is there a reason for this behaviour?
>
> since describe output always starts with "~S is ", it makes sense to do
> that at the highest level.

This is certainly true for objects described by the implementation.
However, the describe-object is also meant as hook for users:

"Users can write methods for describe-object for their own classes if
they do not wish to inherit an implementation-supplied method."

and here the details of the API do matter. Other implementation seem
to do as hinted in CLHS.

I can live easily with it as it is now; I was just curious whether to
#-clisp the "~S is" string in describe-object or to expect change.

Regards,

Tomas