[m-dev.] Deprecating stuff in builtin module
paul at bone.id.au
Tue Dec 1 09:24:41 AEDT 2015
On Tue, Dec 01, 2015 at 02:16:23AM +1100, Zoltan Somogyi wrote:
> On Tue, 1 Dec 2015 00:06:42 +1100 (AEDT), Julien Fischer <jfischer at opturion.com> wrote:
> > > No objection from me, but I don't think we have any facilities
> > > for marking a *mode*, as opposed to a *predicate*, as obsolete.
> > We don't, beyond documenting that the modes are deprecated (which is
> > what I intend to do).
> Yes, I figured that. The problem is that if someone has code
> that uses those modes, their code will continue to compile without
> incident, and they won't KNOW that they should read the new comment.
> The comment may therefore help people who look up the documentation
> before writing NEW code, but it won't help most people with existing code.
> For them. deprecating the mode now and deleting it later will be
> effectively indistinguishable from just deleting it later.
Some, but admittedly few, users may read the release notes and a smaller
sebset of these users might check their code for changes mentioned in the
release notes. It's not very much but it's something.
More information about the developers