unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: print out all members of a list, v.1.0
Date: Tue, 1 Mar 2011 21:33:56 -0800 (PST)	[thread overview]
Message-ID: <de6b22f3-8921-4f3c-ac36-b719b45666b7@k10g2000prh.googlegroups.com> (raw)
In-Reply-To: barmar-5DB332.23511801032011@news.eternal-september.org

On Mar 2, 9:51 am, Barry Margolin <bar...@alum.mit.edu> wrote:
> In article
> <d00d6215-5ab4-499d-8e7b-07168ad8a...@o18g2000prh.googlegroups.com>,
>
>  rusi <rustompm...@gmail.com> wrote:
> > yes it is. emacs lisp became obsolete when scheme and common lisp came
> > out -- which is about 30 years ago.
>
> How is that possible, since Emacs Lisp came out AFTER Scheme and Common
> Lisp?  CLtL was published in 1984, the same year Stallman started
> writing GNU Emacs?  And Scheme is older, since CL took a number of ideas
> from it (most notably lexical scoping).

Ok I stand corrected technically.

I was speaking more generically -- elisp as a member of the
dynamically scoped 2-lisp family.
ie. to the family of {MAC,Franz,UCI}-lisps that preceded scheme and
CL.

[Personal note: I did my degree project in mid 80s writing a lisp
interpreter.  The only reference I had was the UCI lisp manual.  I
thought the scoping (I had implemented) was strange  (static/dynamic
etc were no words I knew then). After I finished I got hold of the CL
manual
and then had the 'Aha: ' The goofup was not mine!]


  reply	other threads:[~2011-03-02  5:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 15:20 print out all members of a list ken
2011-02-28 16:50 ` Teemu Likonen
2011-02-28 17:21 ` ken
2011-02-28 18:25   ` print out all members of a list, v.1.0 ken
2011-02-28 18:32   ` print out all members of a list Thierry Volpiatto
2011-02-28 20:26   ` PJ Weisberg
     [not found]   ` <mailman.5.1298917525.1451.help-gnu-emacs@gnu.org>
2011-02-28 21:32     ` print out all members of a list, v.1.0 Tim X
2011-03-01  5:48     ` Pascal J. Bourguignon
2011-03-01  6:02     ` rusi
2011-03-02  4:51       ` Barry Margolin
2011-03-02  5:33         ` rusi [this message]
2011-03-02 11:56         ` Pascal J. Bourguignon
2011-03-03  0:36           ` Barry Margolin
2011-03-03  9:02             ` Pascal J. Bourguignon
2011-03-03 15:37               ` rusi
2011-03-03 16:00                 ` Pascal J. Bourguignon
2011-03-04  2:34               ` Barry Margolin
2011-03-04  4:09                 ` Drew Adams
2011-03-04 10:39                 ` Pascal J. Bourguignon
2011-03-04 11:06                   ` David Kastrup
2011-03-05  3:24                   ` Barry Margolin
     [not found] ` <mailman.0.1298913700.1451.help-gnu-emacs@gnu.org>
2011-03-01  5:41   ` print out all members of a list Pascal J. Bourguignon
2011-03-01 11:33 ` Andreas Röhler
2011-03-01 11:44 ` Andreas Röhler
     [not found] ` <mailman.5.1298979610.15512.help-gnu-emacs@gnu.org>
2011-03-01 13:10   ` Pascal J. Bourguignon
2011-03-01 14:45     ` Stefan Monnier
2011-03-01 14:50     ` Le Wang
2011-03-01 15:10     ` Richard Riley
2011-03-01 18:39     ` Andreas Röhler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=de6b22f3-8921-4f3c-ac36-b719b45666b7@k10g2000prh.googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).