develooper Front page | perl.perl5.porters | Postings from January 2017

Re: Deprecation plans

Thread Previous | Thread Next
From:
Ricardo Signes
Date:
January 10, 2017 23:40
Subject:
Re: Deprecation plans
Message ID:
20170110234020.GA15945@debian
Cool, thanks for working on this!  A few notes:

* Sawyer X <xsawyerx@gmail.com> [2017-01-08T13:22:55]
> * Deprecated use of my() in false conditional: Deprecated in 5.10.0,
> remove in 5.30.0.

This came up in the past and "remove" seemed like not the straightforward and
preferred solution:

  http://markmail.org/thread/uslcig4mwn47pmyn

I am not presenting an opinion, only a link to history.

> * Use of assignment to $[ is deprecated: Deprecated in 5.12.0; list
> context deprecated in 5.14.0, fatal in 5.28 (unless you use arybase)

How does this interact with the array_base feature?  array_base continues to
work as it does now, implicitly loading arybase when $[ is used?

> * Use of inherited AUTOLOAD for non-method %s() is deprecated:
> Deprecated since 5.004, remove in 5.28.

I have quite a few times beaten the drum of "caller should be able to tell you
whether something was called as a method."  I want to pretend that this removal
is somehow releated to getting that feature added... ;)

> * dump() better written as CORE::dump(): Make it a deprecation warning;
> dump no longer available in 5.30.

What about CORE::dump()?  I never use it, but I know some folks use it as a
breakpoint in gdb or something?  That has come up in the past.

-- 
rjbs

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