Message-Id: <3.0.1.16.19980721154049.2d4fc168@shadow.net> Date: Tue, 21 Jul 1998 15:40:49 To: Hans-Bernhard Broeker From: Ralph Proctor Subject: Re: An ELISP compiler with EMACS? Cc: djgpp AT delorie DOT com In-Reply-To: <199807211910.VAA12245@acp3bf.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Precedence: bulk At 09:10 PM 7/21/98 +0200, you wrote: >[For the record: this mail didn't go to Eli, it went to the whole >DJGPP newsgroup/mailinglist. You've just reached Eli and another >2000 or more readers :-| ] Somethings wrong here. All I did was send TO: eliz AT is DOT elta DOT co DOT il with CC:djgpp AT delorie DOT com >The words 'compiler' and 'Lisp' don't really work together. Make that >'ELisp interpreter' (and a bytecode compiler, which just another word >for a lisp code compressor, IMHO), and it's true. > >> And that one can write a program in ELISP and you would call this a >> "macro"--is this true? > >Yes. Your _emacs file, and all the *.el/*.elc files you'll see in your >emacs/lisp directory are all ELisp programs, or "macros" (the name >doesn't really matter). >100% correct, I'd say. Emacs' Lisp interpreter is not the only one, >but it's maybe the most wide-spread of all, on DOS. > >> Where is the elisp compiler--is it emacs itself? > >The ELisp interpreter is not Emacs, nor the other way round. But the >interpreter is the very heart of Emacs. Originally the name 'Emacs' >meant 'Editor MACroS', and that's exactly what it is: a (*huge*) set >of (byte-compiled) ELisp macros, plus a few highly optimized functions >written in C to speed it up, and there you are: an editor, and *much* >more as well (a file maintenance utility, an IDE, whatever). > >-- >Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) >Even if all the snow were burnt, ashes would remain. Thank your for your information. I am very impressed with what we have here. Regards, Ralph Ralph Proctor Coral Gables, Florida ralphgpr AT shadow DOT net For one shining moment we had Steve Wozniak