On Sat, Mar 26, 2005 at 11:31:07AM +0100, Juerd wrote:
: Perhaps good administration would be to introduce a generic Deprecated::
: namespace. Module authors can move their own old modules there if they
: want, and there can be Deprecated::P5 for stuff like dbmopen,
: Deprecated::Perl5::File::Find.
:
: Deprecated::Perl5 could export everything it has to Deprecated, with a
: symbol group ("tag"), so you can
:
: use Deprecated :perl5;
:
: and even
:
: use Deprecated :all;
:
: And Perl can have built-in warnings, as one huge refactoring of all
: those warnings you'd otherwise have. The 'deprecated' category should
: warn for use of any symbol in Deprecated::.
:
: use warnings :deprecated;
: no warnings :deprecated;
:
: (Explicit 'use Deprecated' would export symbols, and because then the
: symbols are used from ::, no warning is emited.)
Maybe I'm just being dense, but I don't see any particular reason to
make it easy to use deprecated features en masse. If they want a Ponie,
they want a whole Ponie, and not large chunks of a Ponie.
Larry
