Re: Towards __deprecated in cdefs.h
"Poul-Henning Kamp" <[email protected]>
| Newsgroups | gmane.os.freebsd.architechture |
|---|---|
| Message-ID | <[email protected]> |
-------- Warner Losh writes: > So before I spend a ton of time on implementing the various options, I > thought I'd poll on arch@ to see if there's agreement that [4] is likely > best, and if not, which other option I should put my weight behind. We have a history of warning that something will be removed, and then not remembering to do so until much later, so I think we should also have a grep-able "when" argument which can be surveyed during the run-up to a release. Maybe something like: __deprecated_msg(16, "foobar() is going away, use snafu() instead") With suitable macro-magic, that can also be used to run ports-surveys and other tests in a "pretend this is RELENG16" mode. If you want a word distinct from "deprecated" you could use "retired" ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.