Front page | perl.perl5.porters |
Postings from September 2016
On 22 September 2016 at 21:21, Abigail <abigail@abigail.be> wrote: > when the deprecated ones are scheduled to be >> removed, or that there is no current plan to remove them. > > I think we should eliminate the latter category. Disagree. That category mostly exists because we shouldn't be removing things "just because". We should be removing things because their presence is a tangible problem that blocks progress in other parts of Perl, like syntax we need to make available. Deprecating existing features in anticipation of new features we haven't thought of yet is like optimizing code for a problem that doesn't exist. Though clarifying this fact to the user instead of giving them a "eh, we just haven't gotten around to it yet" is important. For instance: ---- These features are deprecated, but have no scheduled removal date. These features/syntax are candidates for replacements by newer features, and are preserved in Perl as a kindness to the existing users, as to avoid breakage until absolutely necessary. However, people using these features are still encouraged to stop using them Post-Haste, as being listed here in a major Perl release is a clear indication that your code COULD be broken in any subsequent major release, if the need arises. --- -- Kent KENTNL - https://metacpan.org/author/KENTNLThread Previous | Thread Next