[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LismMachine File Reading.

To: kanderso%dino.bbn.com@RIVERSIDE.SCRC.SYMBOLICS.COM, Keith Price <price%iris.usc.edu@RIVERSIDE.SCRC.SYMBOLICS.COM>
Subject: Re: LismMachine File Reading.
From: "Robert W. Kerns" <RWK%fuji.ila.dialnet.symbolics.com@RELAY.CS.NET>
Date: Sat, 27 Jan 90 22:35:00 EST
Cc: slug%warbucks.ai.sri.com@RIVERSIDE.SCRC.SYMBOLICS.COM, love%alcoa.com@RIVERSIDE.SCRC.SYMBOLICS.COM, spindler%alcoa.com@RIVERSIDE.SCRC.SYMBOLICS.COM, shanefelt%alcoa.com@RIVERSIDE.SCRC.SYMBOLICS.COM, mthome%dino.bbn.com@RIVERSIDE.SCRC.SYMBOLICS.COM, jmorrill%dino.bbn.com@RIVERSIDE.SCRC.SYMBOLICS.COM, kanderson%dino.bbn.com@RIVERSIDE.SCRC.SYMBOLICS.COM
In-reply-to: <9001260808.aa07209@mintaka.lcs.mit.edu>

    Date: Fri, 26 Jan 90 07:37:49 -0500
    From: kanderso@dino.bbn.com

    I've looked into READ and have found a way to speed it up by a factor of 4.
    ...
    The flexiblity of READ lets us read other languages besides LISP,
    simply by changing *readtable*.  This flexibility is the ultimate
    performance limit of the current READ.
Right!

This is good investigative reporting.  Thanks, and I hope
Symbolics does something with it.

Prev by Date: Re: LISPM I/O performance
Next by Date: Re: LISPM I/O performance
Previous by thread: LismMachine File Reading.
Next by thread: Symbolics Marketing Strategy
Index(es):
- Date
- Thread