From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Lions & tigers & variables - Oh my! [was: Lisp error on function :documentation]
Date: Wed, 19 Oct 2022 01:25:43 +0200 [thread overview]
Message-ID: <87y1tcbtoo.fsf@dataswamp.org> (raw)
In-Reply-To: SJ0PR10MB5488AA2F20F919FE8F17372FF3289@SJ0PR10MB5488.namprd10.prod.outlook.com
Drew Adams wrote:
>> global variables can be virtually eliminated by using
>> closures
>
> _*ALL*_ variables can (really, not virtually) be eliminated,
> with combinatory logic. Magic.
But not in practise writing code ...
> That doesn't mean you'll likely find it preferable to do all
> your programming without variables. It does mean that
> variables aren't at all necessary.
Right.
> Yes, all of that is OT. What's not OT is that for
> Emacs users, _in particular_, special (global) vars
> can be quite useful.
All global variables are dynamic/special but not all
dynamic/special variables are global ...
> https://www.gnu.org/software/emacs/emacs-paper.html#SEC15
Good paper ...
Lisp is Loose!
The traditional attitude towards Lisp holds that it is
useful only for esoteric amusements and Artificial
Intelligence. The appearance of Multics EMACS as a Honeywell
product is the death knell of this view. Now, a mainframe
manufacturer is offering a system utility program written in
Lisp; a program intended for heavy use by the general user
community. The special properties of Lisp, which make
extensibility possible, are a key feature, even though many
of the users will not be programmers. Lisp has escaped from
the ivory tower forever, and is a force to be reckoned with
as a system programming language.
I don't know, maybe the ivory tower has just changed form :)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-10-18 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:37 Lions & tigers & variables - Oh my! [was: Lisp error on function :documentation] Drew Adams
2022-10-18 23:25 ` Emanuel Berg [this message]
2022-10-19 14:09 ` [External] : " Drew Adams
2022-10-19 20:20 ` Emanuel Berg
2022-10-20 8:48 ` tomas
2022-10-21 3:37 ` Emanuel Berg
2022-10-21 8:40 ` Emanuel Berg
2022-10-19 5:16 ` Emanuel Berg
2022-10-19 5:27 ` Emanuel Berg
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=87y1tcbtoo.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).