unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44171@debbugs.gnu.org
Subject: bug#44171: Make cwarn.el obsolete
Date: Fri, 23 Oct 2020 12:12:49 +0000	[thread overview]
Message-ID: <CADwFkmmRrAscQqXQzxBe7Ndpsx-oJqvwZX0nyNQn2kOrcJaq8w@mail.gmail.com> (raw)
In-Reply-To: <83d019jisl.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> This was written in 1999, but is it useful today?
>
> I'm still using it, and it sometimes shows mistakes I'm about to make.
> Are there any alternatives that highlight such suspicious constructs?

I was under the impression that flymake was such a replacement?

> As a general rule, IMO we shouldn't lose a feature unless either
> (a) there is a replacement that does at least as well; or (b) the
> feature no longer makes sense at all, e.g. because the problem it
> tries to solve can no longer happen.

That looks like sound criteria, as a first approximation.

I'm not sure how to fit in things like obsoleting support for the Mosaic
web browser in browse-url.el, but I suppose we could say that "the
problem [of using that browser] can no longer happen".

To be clear, I'm not on a quest to remove actually useful features.  I
just stumbled across cwarn.el while looking for stuff that need tests
and/or should be converted to lexical-binding.





  reply	other threads:[~2020-10-23 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 10:53 bug#44171: Make cwarn.el obsolete Stefan Kangas
2020-10-23 11:14 ` Eli Zaretskii
2020-10-23 12:12   ` Stefan Kangas [this message]
2020-10-23 13:03     ` Eli Zaretskii
2020-10-23 13:20       ` Stefan Kangas

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=CADwFkmmRrAscQqXQzxBe7Ndpsx-oJqvwZX0nyNQn2kOrcJaq8w@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=44171@debbugs.gnu.org \
    --cc=eliz@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).