From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Robert Cochran <robert+Emacs@cochranmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [Patch] Enable byte-compile-error-on-wran for error-free files in lisp/
Date: Thu, 22 Feb 2018 00:24:37 -0500 [thread overview]
Message-ID: <jwvwoz5wqwh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87371tn2qg.fsf@cochranmail.com> (Robert Cochran's message of "Wed, 21 Feb 2018 19:05:11 -0800")
> I am trying to keep warnings from lingering. The
> string-{to,as}-{multi,uni}byte family of functions have been deprecated
> since June 2016, which are some of the functions I see the most in the
> deprecation warnings. Stuff like that.
Indeed, these turn out to be difficult to fix:
- the potential replacement code is subtly different and it usually
requires a detailed understanding of the code to know what's the right fix.
- in many places those function calls were added when Emacs's handling of
`eight-bit` chars was different and it's difficult to know how that's
affected by subsequent changes.
- there are various situations where there's no really good replacement.
I guess that means that while they are marked as obsolete we really
won't be getting rid of them any time soon. And we can probably just
silence the remaining warnings with `with-no-warnings` but only after
we clearly document the need to use this function and what it would
need to do otherwise.
> Hmm, sounds like its better to just not do that with files distributed
> in parallel. I don't have a problem with that (most files is better than
> no files after all), but I have no idea which ones are and are not 'core
> only' files. Guidance requested.
Good question. After contributing to Emacs for almost 20 years
I generally "just know", but it's not 100% and it's not written down
anywhere for those who don't have that 20 year head start.
I agree it would be useful to document it. Eli, John, any idea what
would be the best way to document those things? Should we just add
a "Unbundled: yes" to the pseudo-headers, or maybe just (ab)use the
typical "URL: ..." pseudo-header for that?
As for which files are affected, I can't remember offhand, but a first
approximation is: org/*, mh-e/*, cc-*, vhdl and verilog, antlr and
those files mentioned in elpa.git/externals-list?
Stefan
next prev parent reply other threads:[~2018-02-22 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 18:30 [Patch] Enable byte-compile-error-on-wran for error-free files in lisp/ Robert Cochran
2018-02-21 18:42 ` Eli Zaretskii
2018-02-22 2:51 ` Robert Cochran
2018-02-22 6:56 ` Eli Zaretskii
2018-02-21 19:24 ` Stefan Monnier
2018-02-22 3:05 ` Robert Cochran
2018-02-22 5:24 ` Stefan Monnier [this message]
2018-02-22 7:18 ` Eli Zaretskii
2018-02-23 9:47 ` Richard Stallman
2018-02-24 11:08 ` Eli Zaretskii
2018-02-24 23:33 ` Richard Stallman
2018-02-25 3:33 ` Eli Zaretskii
2018-02-25 13:13 ` Stefan Monnier
2018-02-25 15:33 ` Eli Zaretskii
2018-02-22 7:13 ` Eli Zaretskii
2018-02-21 19:26 ` Noam Postavsky
2018-02-22 2:29 ` Robert Cochran
2018-02-22 3:24 ` Noam Postavsky
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=jwvwoz5wqwh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=robert+Emacs@cochranmail.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.