![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 16 years ago
Closed 16 years ago
#13577 closed feature request (wontfix)
Pair Deprecated Function Warnings with New and Trunk Function Warnings
| Reported by: | hakre | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | General | Version: | 3.0 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
We have deprecated functions. The do a warning when used.
To complete that principle it would be nice to have new functions as well. New functions are those that were introduced in the current point release.
They should give warning until they are not new any longer.
Next to that there can be trunk functions as well that are those that exist in trunk only and have not used already.
This would complete the dynamic version control we offer in core.
Change History (1)
Note:
See TracTickets
for help on using tickets.
Why should we throw warnings on new functions? Should every function give a warning? When would it give a warning, when it is used? If it's being used, don't they already know it exists?
This sounds like opportunity for a Codex page or API reference that lists all new public functions with each release. Beyond that, this is code bloat.