* Is it better to use eLISP or Common LISP? @ 2003-10-20 18:22 Dan Anderson 2003-10-20 20:37 ` Sam Steingold [not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org> 0 siblings, 2 replies; 6+ messages in thread From: Dan Anderson @ 2003-10-20 18:22 UTC (permalink / raw) I am thinking of hacking some LISP for a project manager. I know that I can either use Emacs LISP or the eLISP file that interfaces with common LISP. Since I'd be learning LISP for the first time, what would be best to do? Also, are there any reasons why? -Dan ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Is it better to use eLISP or Common LISP? 2003-10-20 18:22 Is it better to use eLISP or Common LISP? Dan Anderson @ 2003-10-20 20:37 ` Sam Steingold [not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 6+ messages in thread From: Sam Steingold @ 2003-10-20 20:37 UTC (permalink / raw) > * Dan Anderson <qna@znguwhaxvrf.pbz> [2003-10-20 14:22:43 -0400]: > > I am thinking of hacking some LISP for a project manager. I know that I > can either use Emacs LISP or the eLISP file that interfaces with common > LISP. Since I'd be learning LISP for the first time, what would be best > to do? Also, are there any reasons why? The choice is between "Emacs-Lisp" and "Common Lisp". I recommend Common Lisp. Emacs-Lisp is a largely obsolete dialect, defined by its unique implementations (Emacs & XEmacs stem from the same codebase), unsuitable for large projects (even though many large projects indeed have been done in it!) Common Lisp is a modern standard language (actually, it was the first OO language to receive an ANSI standard) with several high quality implementations. details: <http://www.podval.org/~sds/tool.html> -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> MS Windows: error: the operation completed successfully. ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org>]
* Re: Is it better to use eLISP or Common LISP? [not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org> @ 2003-10-21 11:09 ` Phillip Lord 2003-10-21 14:36 ` Dan Anderson [not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org> 0 siblings, 2 replies; 6+ messages in thread From: Phillip Lord @ 2003-10-21 11:09 UTC (permalink / raw) >>>>> "Sam" == Sam Steingold <sds@gnu.org> writes: >> * Dan Anderson <qna@znguwhaxvrf.pbz> [2003-10-20 14:22:43 -0400]: >> >> I am thinking of hacking some LISP for a project manager.[...] Since >> I'd be learning LISP for the first time, what would be best to >> do? Also, are there any reasons why? Sam> The choice is between "Emacs-Lisp" and "Common Lisp". Sam> I recommend Common Lisp. Sam> Emacs-Lisp is a largely obsolete dialect, Sam> Common Lisp is a modern standard language If you want to learn a lisp, then Common Lisp would probably be the better choice. If you want to modify the behaviour of Emacs, then Emacs Lisp would be the better choice. >> I know that I can either use Emacs LISP or the eLISP file that >> interfaces with common LISP. I don't know what this means. What "elisp file that interfaces with common lisp". If you want emacs to do things, then you can use emacs lisp, or emacs lisp. Phil ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Is it better to use eLISP or Common LISP? 2003-10-21 11:09 ` Phillip Lord @ 2003-10-21 14:36 ` Dan Anderson [not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org> 1 sibling, 0 replies; 6+ messages in thread From: Dan Anderson @ 2003-10-21 14:36 UTC (permalink / raw) Cc: help-gnu-emacs > >> I know that I can either use Emacs LISP or the eLISP file that > >> interfaces with common LISP. > > I don't know what this means. What "elisp file that interfaces with > common lisp". If you want emacs to do things, then you can use emacs > lisp, or emacs lisp. I think I found an emacs lisp file that allows you to extend emacs using common lisp. Perhaps I was reading the manifest wrong. -Dan ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org>]
* Re: Is it better to use eLISP or Common LISP? [not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org> @ 2003-10-21 14:53 ` Phillip Lord 2003-10-22 8:23 ` Tim X 1 sibling, 0 replies; 6+ messages in thread From: Phillip Lord @ 2003-10-21 14:53 UTC (permalink / raw) >>>>> "Dan" == Dan Anderson <dan@mathjunkies.com> writes: >> >> I know that I can either use Emacs LISP or the eLISP file that >> >> interfaces with common LISP. >> >> I don't know what this means. What "elisp file that interfaces >> with common lisp". If you want emacs to do things, then you can >> use emacs lisp, or emacs lisp. Dan> I think I found an emacs lisp file that allows you to extend Dan> emacs using common lisp. Perhaps I was reading the manifest Dan> wrong. There is the "CL" packages within Emacs. This is written in Emacs Lisp, but provides a set of functions which are found in Common Lisp as well. If you want to use the CL packages, then there is no problem with this. Many people do use these packages. But they are an implementation of some of CL. They are not CL. If you read a book on CL, and then try is on Emacs, even using the CL code, its not going to work. Likewise you can look at EIEIO, which is Eric Ludlum's implementation of a CLOS-u-like object system for emacs lisp. But its not CLOS. If you want to write Emacs lisp add on's, then its Emacs Lisp you should learn. I would suggest that you start off with this... http://www.gnu.org/manual/emacs-lisp-intro/emacs-lisp-intro.html If you get the .info files, you can read it as hypertext within Emacs, and it has the advantage that the example source code in the book, is actually directly runnable within Emacs. It's a good introduction. Next I'd start to read the Emacs Lisp Manual. Its a bit heavier weight, and you want to be familiar with Emacs Lisp, and Emacs usage before you read it. The CL stuff is good to read, at about the same time, as there are lots of useful utility functions. Phil ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Is it better to use eLISP or Common LISP? [not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org> 2003-10-21 14:53 ` Phillip Lord @ 2003-10-22 8:23 ` Tim X 1 sibling, 0 replies; 6+ messages in thread From: Tim X @ 2003-10-22 8:23 UTC (permalink / raw) >>>>> "Dan" == Dan Anderson <dan@mathjunkies.com> writes: >> >> I know that I can either use Emacs LISP or the eLISP file that >> >> interfaces with common LISP. >> >> I don't know what this means. What "elisp file that interfaces >> with common lisp". If you want emacs to do things, then you can >> use emacs lisp, or emacs lisp. Dan> I think I found an emacs lisp file that allows you to extend Dan> emacs using common lisp. Perhaps I was reading the manifest Dan> wrong. You may be thinking about the cl package which adds many common lisp features to emacs lisp, such as 'declaim, proclaim etc'. It is documented in its own info pages under CL. Tim -- Tim Cross The e-mail address on this message is FALSE (obviously!). My real e-mail is to a company in Australia called rapttech and my login is tcross - if you really need to send mail, you should be able to work it out! ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-10-22 8:23 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2003-10-20 18:22 Is it better to use eLISP or Common LISP? Dan Anderson 2003-10-20 20:37 ` Sam Steingold [not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org> 2003-10-21 11:09 ` Phillip Lord 2003-10-21 14:36 ` Dan Anderson [not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org> 2003-10-21 14:53 ` Phillip Lord 2003-10-22 8:23 ` Tim X
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).