From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
18059@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#18059: 24.3.92; defvar and special variables
Date: Thu, 8 Mar 2018 16:15:14 -0800 (PST) [thread overview]
Message-ID: <29316879-292c-4528-8bf7-57046f3730b7@default> (raw)
In-Reply-To: <87lgf216oc.fsf@gmail.com>
> >> Not to mention lots of vacuous defvars to quiet the byte-compiler:
> >>
> >> (unless (> emacs-major-version 22)
> >> (defvar display-buffer-reuse-frames))
> >
> > So here, what is the use of putting it below the toplevel? Why don't
> > you just write
> >
> > (defvar display-buffer-reuse-frames) ; For Emacs 22 and earlier.
>
> Hey Drew, I am actually interested in your answer to this question,
> sorry if it came across as rhetorical.
I didn't take it wrong, Noam; don't worry.
I don't have a good answer, in terms of "I _need_ to do it this
way because otherwise...".
My arguments:
1. Some users _will_ do it this way. Nothing says they shouldn't.
If that means they lose out on some functionality then they will
need to know that. And some users will have already done it,
so they will need to change.
Is that really necessary? Should it be? What's the real need
here?
2. As one user, I _prefer_ to do it the way I do it, for facility
of code maintenance, i.e., to document to myself which versions
need what. Yes, I could do that using only comments (but I find
this way clearer, as it's the same way I do it where it really
matters).
HTH - D.
next prev parent reply other threads:[~2018-03-09 0:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 3:23 bug#18059: 24.3.92; defvar and special variables Michael Heerdegen
2018-02-10 19:29 ` Noam Postavsky
2018-02-10 23:59 ` Michael Heerdegen
2018-02-11 0:17 ` Drew Adams
2018-02-11 0:43 ` Noam Postavsky
2018-02-11 0:38 ` Noam Postavsky
2018-02-11 1:32 ` Michael Heerdegen
2018-02-11 2:26 ` Noam Postavsky
2018-02-11 15:14 ` Stefan Monnier
2018-02-11 15:35 ` Noam Postavsky
2018-02-11 16:38 ` Michael Heerdegen
2018-02-11 17:00 ` Noam Postavsky
2018-02-14 0:27 ` Noam Postavsky
2018-02-18 22:28 ` Noam Postavsky
2018-02-19 1:44 ` Michael Heerdegen
2018-02-21 15:09 ` Noam Postavsky
2018-02-21 16:08 ` Drew Adams
2018-02-21 16:23 ` Noam Postavsky
2018-02-21 16:33 ` Noam Postavsky
2018-02-21 17:15 ` Drew Adams
2018-02-21 18:00 ` Noam Postavsky
2018-02-21 19:14 ` Drew Adams
2018-02-21 19:19 ` Stefan Monnier
2018-02-21 22:20 ` Michael Heerdegen
2018-02-23 14:05 ` Stefan Monnier
2018-02-23 14:55 ` Michael Heerdegen
2018-03-04 23:27 ` Noam Postavsky
2018-03-05 9:51 ` Michael Heerdegen
2018-03-07 13:00 ` Noam Postavsky
2018-03-09 9:58 ` Michael Heerdegen
2018-03-09 13:43 ` Stefan Monnier
2018-03-11 16:45 ` Noam Postavsky
2018-03-11 22:16 ` Drew Adams
2018-03-14 11:15 ` Noam Postavsky
2018-03-23 12:23 ` Noam Postavsky
2018-03-05 15:57 ` Eli Zaretskii
2018-03-08 23:36 ` Noam Postavsky
2018-03-09 0:15 ` Drew Adams [this message]
2018-02-21 17:11 ` Drew Adams
2018-02-11 15:57 ` Eli Zaretskii
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=29316879-292c-4528-8bf7-57046f3730b7@default \
--to=drew.adams@oracle.com \
--cc=18059@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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 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).