develooper Front page | perl.perl5.porters | Postings from November 2010

Re: [PATCH] deprecate ?PATTERN?

Thread Previous | Thread Next
From:
Andy Dougherty
Date:
November 28, 2010 12:35
Subject:
Re: [PATCH] deprecate ?PATTERN?
Message ID:
alpine.DEB.2.00.1011281446040.2733@fractal.phys.lafayette.edu
Generally, we strive for balance.  The document pod/perlpolicy.pod 
contains an extensive, thoughtful discussion about our collective attempt 
to seek appropriate balance.

This particular usage is "vaguely deprecated" with a tongue-in-cheek
target date of 2168.  I don't think that counts as much of a warning.
I know I personally have used it on occasion without worrying about that
"impending" deadline, but I don't have a lot of uses of it lyling around.
If that syntax is indeed a significant impediment to real progress,
then I'd support an actual deprecation with a much closer deadline.

For me, the most frustrating aspect of these occasional discussions is
the occasional failure of some posters to even acknowledge that other's
situations may be significantly different from their own.  I often have
to remind myself that perl is used in so many different ways in so many
different environments that I can't reliably extrapolate my own experience
to cover even a significant fraction of all uses.

Deprecating something has a cost.  Not deprecating it also has a cost.
Too often one is ignored but the other is not.  Since the costs are often
borne by different entities, it is hard to make good balanced
judgments, but we do collectively strive to make them anyway.

So back to the topic at hand:  The request

> > > Please avoid deprecations. Always.

is not consistent with perl's current policy, but the underlying
sentiment is one thing we do try to respect.

Thanks,

-- 
    Andy Dougherty		doughera@lafayette.edu



Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About