Newsgroups: comp.lang.lisp,comp.lang.c++
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!newsstand.cit.cornell.edu!news.acsu.buffalo.edu!dsinc!spool.mu.edu!howland.erols.net!vixen.cso.uiuc.edu!uchinews!news
From: Alexey Goldin <goldin@spot.uchicago.edu>
Subject: Re: Lisp versus C++ for AI. software
X-Nntp-Posting-Host: spot.uchicago.edu
Message-ID: <m1wwwrvikm.fsf@spot.uchicago.edu>
Lines: 36
Sender: news@midway.uchicago.edu (News Administrator)
Organization: University of Chicago
X-Newsreader: Gnus v5.3/Emacs 19.34
References: <3250E6C3.3963@eis.uva.es> <325B0122.1BCF@sybase.com>
	<3053855957080527@naggum.no> <325C6020.47F6@sybase.com>
	<53i5rv$jp2@Godzilla.cs.nwu.edu> <53rl90$f3q@nic.wat.hookup.net>
	<3263D027.14B9@dma.isg.mot.com>
Date: Wed, 16 Oct 1996 00:50:01 GMT
Xref: glinda.oz.cs.cmu.edu comp.lang.lisp:23231 comp.lang.c++:219006

Mukesh Prasad <mprasad@dma.isg.mot.com> writes:

> 
> >It seems to me that the C code is solely to provide the elisp and >bytecode
> >interpreter. Granted, Elisp has lots of datatypes and fubctions >designed to
> >make editing tasks written in Elisp easier, but the editor itself seems >to be
> >written in Elisp.
> >
> >Hartmann Schaffer
> 
> I would have to disagree.  The C code for byte code
> interpreting is small compared to the rest
> of the emacs C code.  Also, most of the core editor
> algorihtms were in C the last time I looked.
> Elisp provides several "facilities" and "hooks"
> on top, not at the core level.


On my Sparc 5 running Sparc Linux:



cd /usr/share/emacs/19.34/
spot:/usr/share/emacs/19.34$ du lisp
du lisp
239	lisp/term
19722	lisp
spot:/usr/share/emacs/19.34$ 


20 Megs seems like quite a lot to me.
I also believe that 20 megabytes of Lisp "facilities" and
"hooks" have way more functionality than 20 megabytes of C code.



