From: Phillip Lord <p.lord@russet.org.uk>
Subject: Re: Differences between Elisp and Lisp
Date: 29 Apr 2003 18:16:48 +0100 [thread overview]
Message-ID: <vfd6j5z0jj.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: sfwy91tw8wp.fsf@shell01.TheWorld.com
>>>>> "Kent" == Kent M Pitman <pitman@world.std.com> writes:
>> Perhaps I am confusing things here, but I always assumed that the
>> problem with dynamic binding is that it makes odd things happen.
Kent> You're saying the same thing as I was saying only in different
Kent> words. Both the efficiency loss and this other effect you
Kent> cite (accessibility from outside) are effects of having the
Kent> name be accessible from the outside.
Yes, you are correct here. For the user within emacs, its just that
the effect on the programmer is probably more of an issue that the
optimisation.
Obviously if fixing the former, gives you the latter for free, then
this is a good thing.
>> Optimisation might be an issue as well of course, but processors
>> are fast these days! Its nice, but not essential.
Kent> This sort of assumes a single-user machine. Server machines
Kent> can be overloaded regardless of capacity.
A reasonable assumption in the context of emacs!
Kent> You might assume emacs is not a server, but one of the good
Kent> effects of merging CL and emacs might be that emacs could do
Kent> more tasks that are often relegated to other programs and that
Kent> those other programs could get some of the services emacs
Kent> usually does. So the lines might get blurred.
This is certainly true. I can imagine a emacs based web server would
be quite nice, as you could use all the emacs based formatting
abilities.
I think we are in furious agreement here!
Phil
next prev parent reply other threads:[~2003-04-29 17:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5343.1051607007.21513.help-gnu-emacs@gnu.org>
2003-04-29 10:22 ` Differences between Elisp and Lisp Friedrich Dominicus
2003-04-29 10:27 ` Lars Magne Ingebrigtsen
2003-04-29 10:35 ` David Kastrup
2003-04-29 11:03 ` Oliver Scholz
2003-04-29 12:23 ` Phillip Lord
2003-04-29 14:17 ` Thomas Link
2003-04-29 15:43 ` Kent M Pitman
2003-04-29 15:56 ` Phillip Lord
2003-04-29 16:44 ` Kent M Pitman
2003-04-29 17:16 ` Phillip Lord [this message]
2003-04-29 18:41 ` Kai Großjohann
2003-04-30 12:39 ` Phillip Lord
2003-04-30 13:12 ` Kai Großjohann
2003-04-30 18:07 ` Kevin Rodgers
2003-04-29 18:59 ` Oliver Scholz
2003-04-30 12:43 ` Phillip Lord
2003-04-29 17:01 ` Kai Großjohann
2003-04-30 23:02 ` Stefan Monnier
2003-05-01 5:22 ` Lars Magne Ingebrigtsen
2003-05-01 5:41 ` Friedrich Dominicus
2003-05-01 5:54 ` Lars Magne Ingebrigtsen
2003-05-01 6:37 ` [OT] " Friedrich Dominicus
[not found] ` <yoijznm9y5yr.fsf@bilbo.dd.chalmers.se>
2003-04-29 13:45 ` Kent M Pitman
2003-04-29 15:23 ` Nicolas Neuss
2003-04-29 15:28 ` Nicolas Neuss
2003-04-29 14:23 ` Marco Antoniotti
2003-04-29 14:29 ` Phillip Lord
2003-04-29 19:06 ` Oliver Scholz
2003-04-29 16:51 ` Kaz Kylheku
2003-04-29 8:57 Daniel R. Anderson
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=vfd6j5z0jj.fsf@rpc71.cs.man.ac.uk \
--to=p.lord@russet.org.uk \
/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).