Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!umcp-cs!nbs-amrf!manheime
From: manheime@nbs-amrf.UUCP (Ken Manheimer)
Newsgroups: net.emacs
Subject: Re: MLisp local var in Gosling's (Flaw, not feature!!)
Message-ID: <372@nbs-amrf.UUCP>
Date: Fri, 1-Aug-86 13:20:44 EDT
Article-I.D.: nbs-amrf.372
Posted: Fri Aug  1 13:20:44 1986
Date-Received: Sat, 2-Aug-86 23:22:24 EDT
References: <1514@vax135.UUCP> <916@unirot.UUCP> <371@nbs-amrf.UUCP>
Organization: National Bureau of Standards
Lines: 13

> [Excerpt from my prior article:]
> (Incidentally, you also don't have another essential feature of
> lisp in Mlisp, list data structures, so you have no efficient way
> to organize objects bigger than single characters (which you can
> deal with using the one data structure in Mlisp, strings).

On a little further thought it occurred to me that the text buffers
(and all their paraphenalia, eg marks) can be considered to be data
structures of Emacs lisps, so that mlisp isn't just confined to strings.
None the less, a list data structure (and oblists, arrays, plists, ...)
is crucial.

Ken.