From: Michael Heerdegen <michael_heerdegen@web.de>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How the backquote and the comma really work?
Date: Tue, 21 Jul 2015 23:50:06 +0200 [thread overview]
Message-ID: <87fv4hnptd.fsf@web.de> (raw)
In-Reply-To: <87mvz1b16h.fsf@mbork.pl> (Marcin Borkowski's message of "Sun, 12 Jul 2015 21:55:54 +0200")
Marcin Borkowski <mbork@mbork.pl> writes:
> > sorry for the late reply.
>
> It's fine, I'm working slowly on this anyway.
Sorry again. Was on vacation this time.
> > Yes, that's the right approach. You could of course translate into the
> > symbols named "'", "`" and "," instead, like the Lisp reader does, but
> > that's a detail. In Elisp, these aren't special forms. They could be
> > in your interpreter, of course.
>
> And they will be;-).
FWIW, "," and ",@" are not defined in Elisp at all. They're just
symbols used as tags that are recognized by `backquote'.
> > Dunno if your interpreter will support macros. If not, you could
> > handle backquote directly in your interpreter.
>
> No, I don't want to support macros – too much work and little benefit,
> I guess.
Mmh, I don't think so. Macros are an essential part of the Lisp
language. And I don't think it would be hard, it should be quite simple
to do. `defmacro' kind of defines a function. The difference to real
functions is that they get expressions (code) as arguments before
evaluation; the expansion itself is just like a function call. The
result is a new (expanded) expression to be evaluated.
So if you have `funcall' and `apply', you already have everything you
need to support macros. Your `eval' just has to use these to expand the
macro calls before it starts with the conventional evaluation.
> >> (require 'anaphora) ; we'll use acase
> >
> > It would be good if you could drop this dependence. This would spare
> > people from trying your code from installing additional stuff.
>
> Well, aif is also useful for me.
FWIW, there are now good replacements for such stuff in Emacs Lisp. You
can use `if-let' (new in Emacs 25.1 coming soon) instead of `aif', and
`pcase' (already part of Emacs) instead of `acase'. Learning
`pcase' will take some time, but it is worth it.
Lots of Lispers seems to hate these anaphoric macros and say they are
unlispy. Lots of others love them.
> > I guess you already know that you have not chosen the easiest way to
> > understand backquote. Anyway, you learn a lot of stuff with your
> > approach. Looking forward the next version!
>
> Not the easiest, but more thorough. I’m not satisfied with the “I kind
> of understand this... I guess” situation – if I can’t implement it,
> I don’t understand it. (Unfortunately, the converse need not be true;
> I might be lucky and implement it without a full understanding, too...)
Actually, I think it is not unusual for Lisp programming that you invent
something, implement it, and understand it later. The same is probably
true in some sense for Lisp itself.
Regards,
Michael.
next prev parent reply other threads:[~2015-07-21 21:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 17:09 How the backquote and the comma really work? Marcin Borkowski
2015-06-25 17:33 ` Michael Heerdegen
2015-06-25 18:06 ` Marcin Borkowski
2015-06-25 18:22 ` Michael Heerdegen
2015-06-25 18:39 ` Marcin Borkowski
2015-06-25 18:44 ` Marcin Borkowski
2015-06-25 19:06 ` Michael Heerdegen
2015-07-10 11:36 ` Marcin Borkowski
2015-07-12 15:54 ` Michael Heerdegen
2015-07-12 19:55 ` Marcin Borkowski
2015-07-12 20:33 ` Marcin Borkowski
2015-07-14 18:17 ` Marcin Borkowski
2015-07-14 22:08 ` Emanuel Berg
2015-07-21 22:08 ` Michael Heerdegen
2015-07-24 13:01 ` Michael Heerdegen
2015-08-11 11:41 ` Marcin Borkowski
2015-08-12 15:29 ` Michael Heerdegen
[not found] ` <mailman.8207.1439393377.904.help-gnu-emacs@gnu.org>
2015-08-12 16:30 ` Pascal J. Bourguignon
2015-08-23 8:30 ` Marcin Borkowski
[not found] ` <mailman.110.1440318650.11330.help-gnu-emacs@gnu.org>
2015-08-23 16:46 ` Pascal J. Bourguignon
2015-07-21 21:54 ` Michael Heerdegen
2015-08-11 10:15 ` Marcin Borkowski
2015-08-11 17:20 ` Thorsten Jolitz
2015-08-12 15:01 ` Michael Heerdegen
2015-07-21 21:50 ` Michael Heerdegen [this message]
2015-06-25 18:10 ` Drew Adams
2015-06-25 18:40 ` Michael Heerdegen
2015-06-25 18:53 ` Marcin Borkowski
2015-06-25 19:39 ` Michael Heerdegen
2015-06-25 20:05 ` Drew Adams
2015-06-25 20:18 ` Marcin Borkowski
2015-06-25 20:37 ` Drew Adams
2015-06-25 23:55 ` Robert Thorpe
[not found] ` <mailman.5697.1435276533.904.help-gnu-emacs@gnu.org>
2015-06-26 1:41 ` Rusi
2015-06-26 14:24 ` Michael Heerdegen
[not found] ` <mailman.5716.1435328741.904.help-gnu-emacs@gnu.org>
2015-06-26 14:35 ` Rusi
2015-06-26 14:51 ` Michael Heerdegen
2015-06-25 18:46 ` Marcin Borkowski
2015-06-26 7:31 ` tomas
2015-06-26 13:48 ` Drew Adams
2015-06-26 14:06 ` tomas
2015-06-26 15:06 ` Emanuel Berg
2015-07-12 17:38 ` Vaidheeswaran C
[not found] <mailman.5657.1435252169.904.help-gnu-emacs@gnu.org>
2015-06-30 16:27 ` sokobania.01
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=87fv4hnptd.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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.