unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 43780@debbugs.gnu.org
Subject: bug#43780: 27.1; defvaralias and define-obsolete-variable-alias
Date: Sat, 3 Oct 2020 11:16:25 -0700 (PDT)	[thread overview]
Message-ID: <d3a13330-e8ba-40d3-8b69-b11fe8a194c3@default> (raw)

I have code that uses `inhibit-null-byte-detection'.  Emacs 27 has
(unfortunately) used `define-obsolete-variable-alias' to declare that
variable obsolete, in favor of the much more erudite and sophisticated
`inhibit-null-byte-detection'.

I don't want my code to forever give a compiler warning for that, and I
don't want to change my code to use (if (boundp...)(...)(...))
everywhere.  And I do want it to continue to be compatible with releases
before Emacs 27.

So I added this, hoping to get back `inhibit-null-byte-detection'
without the annoying gratuitous warning:

(when (> emacs-major-version 26)
  (defvaralias 'inhibit-null-byte-detection
               'inhibit-nul-byte-detection))

The `define-obsolete-variable-alias' is done by `emacs -Q', and my
`defvaralias' comes after that.  So I was hoping it would simply make
`inhibit-null-byte-detection' a recognized alias of the existing new
variable `inhibit-nul-byte-detection' (no?).  Alas, the byte-compiler
still warns that `inhibit-null-byte-detection' is obsolete.

Seems like a bug to me.  Why shouldn't the last alias declaration win?

Please tell me the best way to leave my code alone, using
`inhibit-null-byte-detection', and yet eliminate (only) this
byte-compiler warning.

Should I just use (put 'inhibit-null-byte-detection
'byte-obsolete-variable nil)?

Ideally I'd want to affect only byte-compilation of the given file, and
not want to globally change whether `inhibit-null-byte-detection' is
considered obsolete.

This is a serious question, not rhetorical.

(And please don't perform any more such gratuitous renamings that don't
really help anyone.  There are other, more important things to rename,
if someone is overeager enough to really want to start renaming names
that aren't perfect.)

In GNU Emacs 27.1 (build 1, x86_64-w64-mingw32)
 of 2020-08-12 built on CIRROCUMULUS
Repository revision: 86d8d76aa36037184db0b2897c434cdaab1a9ae8
Repository branch: HEAD
Windowing system distributor 'Microsoft Corp.', version 10.0.18362
System Description: Microsoft Windows 10 Pro (v10.0.1903.18362.1082)





             reply	other threads:[~2020-10-03 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03 18:16 Drew Adams [this message]
2020-10-05  7:47 ` bug#43780: 27.1; defvaralias and define-obsolete-variable-alias Lars Ingebrigtsen
2020-10-05 16:27   ` Drew Adams
2020-10-06 21:41 ` Michael Heerdegen
2020-10-06 22:54   ` Drew Adams
2020-10-06 23:15     ` Michael Heerdegen
2020-10-07  0:06       ` Drew Adams
2020-10-07 23:13         ` Michael Heerdegen

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=d3a13330-e8ba-40d3-8b69-b11fe8a194c3@default \
    --to=drew.adams@oracle.com \
    --cc=43780@debbugs.gnu.org \
    /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).