[Gcl-devel] Re: [Axiom-developer] bug in write-to-string, correction

[Camm Maguire]

Greetings!  Just looked at this very briefly, so take with a grain of
salt.  There is another print flag that's been added in the ansi spec
-- print readably.  The only patch to printing that I can see which
would affect the behavior you note is

-       PRINTescape = escape != Cnil;
+       PRINTreadably = readably != Cnil;
+       PRINTescape = PRINTreadably || escape != Cnil;

Try altering *print-readably* too and see if you get the behavior you
want.  I think we did this to match the spec'ed behavior, but I can't
remember the details at this point.  "Readably" support was added in
the 1.12 revision of print.d, should you care to examine the diff in
cvs. 

Take care,

root <address@hidden> writes:

> 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 -------
> 
> 
> _______________________________________________
> Axiom-developer mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/axiom-developer
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah