[Openmcl-devel] Faster Formatting for fun (the OpenMCL version)

Gary King gwking at cs.umass.edu
Mon Jun 7 16:32:10 UTC 2004


Ahhh, good idea. That turns out to be the "reason" that MCL was consing 
so much and OpenMCL wasn't: I had *print-pretty* set to t in MCL and 
nil in OpenMCL. FWIW, I had *print-pretty* and *print-readably* 
confused in my head and thought that using princ was giving me the 
benefits of *print-pretty* being false. Another small win is to convert 
the princ's into write-string's for the things that are strings. I'd 
still like to make it faster though.



On Jun 7, 2004, at 11:56 AM, Zach Beane wrote:

> On Mon, Jun 07, 2004 at 11:49:30AM -0400, Gary King wrote:
>> The trouble is that the princ method is actually slower
>> (though it appears not to cons at all). Note that the MCL data showed 
>> a
>> much larger slow down and lots and lots of consing. Any ideas / help /
>> commiseration would be appreciated.
>
> Does it help to set *print-pretty* to nil?
>
> Zach
>
>
-- 
Gary Warren King, Lab Manager
EKSL East, University of Massachusetts * 413 577 0176

"no art, however minor, demands less than total dedication if you want 
to excel in it."
   -- Alberti




More information about the Openmcl-devel mailing list