[Gcl-devel] bug in write-to-string, correction

[root]

The bug is actually in GCL 2.5.2

===================================================

In GCL 2.4.1:

(setq *print-escape* nil)
(write-to-string '|a|) ==> "a"

in GCL 2.5

(setq *print-escape* nil)
(write-to-string '|a|) ==> "|a|"

It appears that write-to-string is ignoring *print-escape*
in the latest version. This is a bug.

This causes the "Won't parse" messages in the latest port.

Tim Daly
address@hidden
address@hidden


------- End of forwarded message -------