Re: LispWorks IDE history & precursors (semi-off-topic)
The main thing I recall was in Interlisp - the stack was a first class object (so you could capture the state of your program in a variable for backtracking purposes - like a dynamic closure, but without the limitations - more like a continuation). And using the editor meant you couldn't do conditional compilation - we dropped the D machines for Lisp at U Rochester when we needed to write portable code. (That is, no way to do #+foo since that's outside your parens). Since we had a mixed unix (franz), symbolics, dandylion environment, the d machines were the 'most different' and fell into disuse. (I think there was a group that continued to use Mesa for some years though).
On Feb 18, 2012, at 7:45 AM, Tim Bradshaw wrote:
>
> On 17 Feb 2012, at 22:42, rudolf mittelmann wrote:
>
>> Because of your remarks about Interlisp D
>> (I worked on Dandelion machines with Interlisp D from 1985-90?)
>> I just loaded LispWorks Personal and I can't get it. What is the relation/inheritance/similarity? The Inspector?
>
> Well, my memory is now fading since, like you, I've not used a D machines for more than 20 years, but I think the way it reminds me of them is that it's a lots-of-little-windows environment (ie listener, editor, inspector, system browser &c &c), together with the ability to make your own tools in an incredibly lightweight way -- I'm still in the process of reviving various things I had from old CVS repositories, but it's terribly easy to create little visualisation tools based on the grapher, and I used to have lots of such things, as well as others I'd make on the fly via CAPI:CONTAIN.
>
> Obviously it differs in that it look after source as text files with an emacsy editor rather than as structures in memory with a structure editor, and that's a pretty profound difference.
>
> But compared to the MIT-family environments it's also very different. I don't know how it compares with other modern non-Lisp IDEs - I have only really used Eclipse and LW just grinds that into dust, for me.
>
> --tim