From: Michael Heerdegen <michael_heerdegen@web.de>
To: Dave Goel <deego3@gmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 66940-done@debbugs.gnu.org
Subject: bug#66940: Dynamic scoping is all weird now?
Date: Wed, 08 Nov 2023 04:08:10 +0100 [thread overview]
Message-ID: <87fs1h7xid.fsf@web.de> (raw)
In-Reply-To: <CAOCW0DiJ8X8+3WOJxWKECze_P0Lg4_ij1SR97gi7J+0bCOW+gw@mail.gmail.com> (Dave Goel's message of "Tue, 7 Nov 2023 21:49:20 -0500")
Dave Goel <deego3@gmail.com> writes:
> Thank you
Then let's close this one.
What I still wanted to say (to you): no need to complicate things using
macros here in your example. Use functions, then variable references
are simple and clear.
If a macro (expansion) needs to refer to run-time values, use macro
arguments to pass an appropriate expression (like a variable).
But this is overkill in your case, no macros needed. The purpose of
Lisp macros is to extend the language and/or rewrite code (at compile
time). More or less, only that. Always think twice if you really need
macros, try to avoid using macros when possible. This will make the
code easier to understand and maintain. Only if a macro introduces an
abstraction that makes the code actually easier to understand justifies
using one.
Michael.
next prev parent reply other threads:[~2023-11-08 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 4:06 bug#66940: Dynamic scoping is all weird now? Dave Goel
2023-11-05 4:09 ` Dave Goel
2023-11-05 6:04 ` Gerd Möllmann
2023-11-05 6:58 ` Dave Goel
2023-11-05 7:25 ` Gerd Möllmann
2023-11-05 8:12 ` Dave Goel
2023-11-05 8:39 ` Gerd Möllmann
2023-11-05 19:07 ` Dave Goel
2023-11-05 20:21 ` Dave Goel
2023-11-06 1:52 ` Michael Heerdegen
2023-11-06 6:25 ` Gerd Möllmann
2023-11-06 16:49 ` Drew Adams
2023-11-06 6:57 ` Dave Goel
2023-11-07 5:59 ` Michael Heerdegen
2023-11-08 2:49 ` Dave Goel
2023-11-08 3:08 ` Michael Heerdegen [this message]
2023-11-08 3:21 ` Dave Goel
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=87fs1h7xid.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=66940-done@debbugs.gnu.org \
--cc=deego3@gmail.com \
--cc=gerd.moellmann@gmail.com \
/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.