C/Lisp--compiled/interpreted?

C/Lisp--compiled/interpreted?

Post by Ian Da » Sat, 20 Apr 1991 00:28:17




Quote:

>Yeah, some of us prefer Lisp, but most people seem to like C.  But for
>the purpose of running on a slow machine, a compiled extension
>language is essential.

Ah, but GNU emacs has both! Haven't you noticed what language GNU
emacs is written in? Note that GNU emacs has it's lisp primitives
written in C, but it also has quite a lot of higher level functions
written in C for efficiency. There are even macros to make your C
look a bit lispish!

Every now and then someone creates extensions which involve changes to
the C code as well as changes to the lisp code. Usually the C changes
die out after a few new releases. I guess it is too much trouble to
keep track.

If your extra C is only doing something that could be done in lisp
anyway, the interface with the rest of emacs is pretty simple, and all
your changes can be confined to one new file. All the distributed
stuff could be put in a library to speed up recompilations.

--
Ian Dall          I'm not into isms, but hedonism is the most
                  harmless I can think of. -- Phillip Adams


 
 
 

1. interpreting keystrokes from emacs lisp

I would like to find out if is is possible in gnu emacs emacs lisp
call something with a string argument that will have the same effect
as if I had typed the string to the current environment.  If this is a
way to do this, could someone tell me about it?

Thanks,

Dave

2. New 8 Bit page with AcornSite - Comming Soon

3. ws-mode byte-compile messages (was Compiling GNU Emacs lisp)

4. NT WinLogon/GINA.DLL

5. Problem in lisp mode (run-lisp and lisp-send-defun)

6. cluster problem

7. CVS interprets library system as RCS instead of clearcase

8. New Post

9. regexp char ^ interpreted as control key in edmacro

10. Compiling GNU Emacs lisp files

11. Lisp code for compiling java....

12. How to make (X)emacs to interpret tabs as 4 spaces