[armedbear-devel] RfC: Renaming LispObject.writeToString() to LispObject.printObject()

Ville Voutilainen ville.voutilainen at gmail.com
Fri Jul 15 07:13:32 UTC 2011

On 15 July 2011 09:50, Mark Evenson <evenson at panix.com> wrote:
> I think that the meaning of writeToString() was that the function
> should provide an implementation of serialization to a string able
> to be READ with the #S notation.  It is not really performing a
> PRINT-OBJECT-alike function which is a specialization of such an
> implementation on Lisp STANDARD-OBJECT or STRUCTURE-OBJECT.
> On the other hand there is some justification for not calling such
> an implementation writeToString() as that will certainly confuse a
> Java user used to every object either inheriting or overrriding
> java.lang.Object.toString().  I might suggest then, that to clarify
> that this function isn't a direct implementation of CL's PRINT-OBJECT
> which actually takes an both arguments to specify the object it is
> operating on and to specify the output streamthat we rename the
> Java-side to writeLispObject(). The return type of this method,

Why don't we just call it serializeLispObject(), then?

More information about the armedbear-devel mailing list