unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: when you gotta have a variable value for a symbol name
Date: Thu, 24 Jul 2014 01:24:32 +0200	[thread overview]
Message-ID: <87vbqn1wwf.fsf@debian.uxu> (raw)
In-Reply-To: mailman.5935.1406151450.1147.help-gnu-emacs@gnu.org

"Buchs, Kevin J." <buchs.kevin@mayo.edu> writes:

> I want to evaluate (kmacro-name-last-macro variable),
> where I want the value of "variable" passed as the
> symbol name. Despite years of trying, I don't think I
> ever really conceptually "got" the distinction
> between symbols and variables and that seems to be
> critical here.

Good question. In books on programming when they
mention Lisp in one paragraph they always say it came
out of a crazy mind. No, it came out of the push for AI
in the US in the 50s (probably with the cold war in
mind and everything). I thought that "AI" referred to
the data/code blend that can make a function rearrange
another function like any other list of data, perhaps
swapping a pair of operands around a binary operator
and reinsert the modified function in a pool of
competing functions, to see what first morphs into a
function that can solve some task... And more, the Lisp
reliance on the list data structure, that can be
nested, and searched, as so much of the AI applications
revolve around searching trees according to probability
calculations... But they (the books) also usually say
Lisp is about "symbolic manipulation". Is that
literally manipulating symbols?  Drawing on the
dynamic/lexical scope discussion the other day, symbols
would then be dynamic scope as the function would act
on the existing symbol. Variables would be the lexical
scope or the traditional programming approach of using
variables to build programs (and not the other way
around, to build programs to juggle around with
symbols). I guess almost all ordinary Elisping isn't
anything uncommon like that, just to have Emacs
automatize and do things certain ways, nothing fancy
from a theory/science point of view.

--
underground experts united


       reply	other threads:[~2014-07-23 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5935.1406151450.1147.help-gnu-emacs@gnu.org>
2014-07-23 23:24 ` Emanuel Berg [this message]
     [not found] <mailman.5972.1406239064.1147.help-gnu-emacs@gnu.org>
2014-07-24 22:22 ` when you gotta have a variable value for a symbol name Emanuel Berg
2014-07-23 21:37 Buchs, Kevin J.
2014-07-23 22:02 ` Drew Adams
     [not found]   ` <(message>
     [not found]     ` <from>
     [not found]       ` <Drew>
     [not found]         ` <Adams>
     [not found]           ` <on>
     [not found]             ` <Wed>
     [not found]               ` <23>
     [not found]                 ` <Jul>
     [not found]                   ` <2014>
     [not found]                     ` <15:02:38>
     [not found]                       ` <-0700>
2014-07-24 21:57   ` Robert Thorpe
2014-07-25  0:06     ` Drew Adams
     [not found] ` <mailman.5936.1406152985.1147.help-gnu-emacs@gnu.org>
2014-07-23 22:12   ` Pascal J. Bourguignon

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=87vbqn1wwf.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).