From: David Rush <kumoyuki@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Nested Lambda function gives error in common lisp, guile, emacs lisp but works in scheme. Why?
Date: Sun, 07 Oct 2007 23:27:20 -0000 [thread overview]
Message-ID: <1191799640.394781.254540@v3g2000hsg.googlegroups.com> (raw)
In-Reply-To: <5mrsliFesppjU1@mid.individual.net>
On Oct 7, 12:02 pm, Pascal Costanza <p...@p-cos.net> wrote:
> Common Lisp (and presumably Emacs Lisp) is a Lisp-2, which means that
> function positions are evaluated differently than value positions.
Now I may be demonstrating a certain amount of historical ignorance
here, but I was under the impression that Lisp-2 referred to the fact
that there were effectively to different *name* spaces, one in which
'ordinary' values were bound and one in which 'callable' values were
bound. However, this text:
> order to treat a first-class value as a function, you have to shift it
> via FUNCALL. In order to yield a function as a first-class value, you
> have look it up with FUNCTION.
Makes it sound like there are two fundamentally different *types* of
values And FUNCALL and FUNCTION are the type cast operators between
those types. Is this a valid way of looking at this?
david rush
--
opinionated git
next prev parent reply other threads:[~2007-10-07 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 5:34 Nested Lambda function gives error in common lisp, guile, emacs lisp but works in scheme. Why? gnuist006
2007-10-07 5:36 ` gnuist006
2007-10-07 7:55 ` David Rush
2007-10-07 11:04 ` Pascal Costanza
2007-10-07 11:02 ` Pascal Costanza
2007-10-07 23:27 ` David Rush [this message]
2007-10-08 1:14 ` .
2007-10-08 3:43 ` Rainer Joswig
2007-10-08 2:58 ` William D Clinger
2007-10-08 6:42 ` Pascal Costanza
2007-10-08 20:33 ` namekuseijin
2007-10-08 20:48 ` Pascal Costanza
2007-10-08 19:05 ` Don Geddis
2007-10-08 6:39 ` Pascal Costanza
2007-10-08 0:09 ` Matthias Benkard
2007-10-08 12:24 ` Barry Margolin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1191799640.394781.254540@v3g2000hsg.googlegroups.com \
--to=kumoyuki@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.