From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: Obsoleting more progressively
Date: Wed, 03 Nov 2010 08:59:51 +0100 [thread overview]
Message-ID: <4CD11677.3030208@online.de> (raw)
In-Reply-To: <jwvwrovojnp.fsf-monnier+emacs@gnu.org>
Am 02.11.2010 16:10, schrieb Stefan Monnier:
> `make-obsolete' and friends are very useful to let us get rid of old
> features, but even after 10 years of something being declared obsolete,
> experience shows it's still in use "out there".
> So I'd like to be able to make things "more obsolete" (i.e. create
> a second level of obsolescence) before we actually remove them.
>
> I can think of 2 ways to do implement that second level of obsolescence:
> - Add warnings at runtime when obsolete stuff is used.
> for functions, commands and macros, make-obsolete that's reasonably
> easy to do; for variables it's more difficult.
> For hooks, we could let add-hook check the obsolescence property and
> emit a warning, and similarly for a few difference cases, but for
> the primitive get&set operations, this is not an option.
> - Actually remove the function/variable from the non-released code.
> I.e. remove/deactivate the functions/variables from trunk during
> development but put them back in when we start pretesting.
>
> Any thoughts?
>
>
> Stefan
>
>
Hi Stefan,
IMHO that would make things more complicated but don't solve the issue.
The issue is to establish a consistent rule what to do with `obsolete'
marked forms.
As from my limited perspective, it's quite simple:
don't allow them in new code.
Should someone insist, maybe remove `obsolete' again, as it might have
been an error.
Else remove the forms in old code.
So cure the problem rather than augmenting warnings.
Thanks
Andreas
--
https://code.launchpad.net/~a-roehler/python-mode/python-mode-components
https://code.launchpad.net/s-x-emacs-werkstatt/
next prev parent reply other threads:[~2010-11-03 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 15:10 Obsoleting more progressively Stefan Monnier
2010-11-02 16:13 ` Lennart Borgman
2010-11-02 16:56 ` Stephen J. Turnbull
2010-11-02 17:51 ` Drew Adams
2010-11-03 1:11 ` jasonr
2010-11-03 1:56 ` Stefan Monnier
2010-11-03 2:58 ` CHENG Gao
2010-11-03 4:49 ` Leo
2010-11-03 7:59 ` Andreas Röhler [this message]
2010-11-03 8:23 ` Kan-Ru Chen
2010-11-03 8:18 ` Glenn Morris
2010-11-03 13:41 ` Stefan Monnier
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=4CD11677.3030208@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).