In perl.git, the branch rjbs/perlpolicy has been updated <http://perl5.git.perl.org/perl.git/commitdiff/bdac798792edac7f84abca5ec566ad6e3be16ece?hp=77da2084d59da28563359acd08b697b304124acd>
- Log ----------------------------------------------------------------- commit bdac798792edac7f84abca5ec566ad6e3be16ece Author: Ricardo Signes <[email protected]> Date: Thu Dec 18 21:25:27 2014 -0500 perlpolicy: clarify what "feature can be replaced" means M pod/perlpolicy.pod commit e8d3c11482996d31147c350daecc183226f64f1f Author: Ricardo Signes <[email protected]> Date: Thu Dec 18 21:21:58 2014 -0500 perlpolicy: the point is caution, not low stakes M pod/perlpolicy.pod ----------------------------------------------------------------------- Summary of changes: pod/perlpolicy.pod | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod index 683d62c..b6107af 100644 --- a/pod/perlpolicy.pod +++ b/pod/perlpolicy.pod @@ -155,13 +155,14 @@ We want to ensure that Perl continues to grow and flourish in the coming years and decades, but not at the expense of our user community. Existing syntax and semantics should only be marked for destruction in -very limited circumstances. If they can be easily replaced, are -believed to be very rarely used, and stand in the way of actual -improvement to the Perl language or perl interpreter, they may be -considered for removal. If both the cost and the gain are believed to -be low, backward compatibility wins. When a feature is deprecated, a -statement of reasoning describing the decision process will be posted, -and a link to it will be provided in the relevant perldelta documents. +very limited circumstances. If they believed to be very rarely used, +stand in the way of actual improvement to the Perl language or perl +interpreter, and if affected code can be easily updated to continue +working, they may be considered for removal. When in doubt, caution +dictates that we will favor backward compatibility. When a feature is +deprecated, a statement of reasoning describing the decision process +will be posted, and a link to it will be provided in the relevant +perldelta documents. Using a lexical pragma to enable or disable legacy behavior should be considered when appropriate, and in the absence of any pragma legacy -- Perl5 Master Repository
