From: Dave Goel <deego3@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 66940-done@debbugs.gnu.org
Subject: bug#66940: Dynamic scoping is all weird now?
Date: Tue, 7 Nov 2023 22:21:25 -0500 [thread overview]
Message-ID: <CAOCW0DhdXDvUPwa1FKxRrVmVe0V3G3_HJcFECddBtOGQp+vHBQ@mail.gmail.com> (raw)
In-Reply-To: <87fs1h7xid.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Most absolutely, and of course.
I was just trying macros here to improve my understanding.
Which it happened, thanks to all y'all's excellent explanations.
On Tue, Nov 7, 2023 at 10:07 PM Michael Heerdegen <michael_heerdegen@web.de>
wrote:
> 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.
>
[-- Attachment #2: Type: text/html, Size: 1911 bytes --]
prev parent reply other threads:[~2023-11-08 3:21 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
2023-11-08 3:21 ` Dave Goel [this message]
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=CAOCW0DhdXDvUPwa1FKxRrVmVe0V3G3_HJcFECddBtOGQp+vHBQ@mail.gmail.com \
--to=deego3@gmail.com \
--cc=66940-done@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).