develooper Front page | perl.perl5.porters | Postings from July 2009

Re: Don't dump autodie from core (was Re: Coring Variable::Magic / autodie fights with string eval in Perl 5.10.x)

Thread Previous | Thread Next
From:
David Golden
Date:
July 5, 2009 08:03
Subject:
Re: Don't dump autodie from core (was Re: Coring Variable::Magic / autodie fights with string eval in Perl 5.10.x)
Message ID:
5d4beb40907050802w799b6749t20d734862e874f35@mail.gmail.com
I took it as "pull for 5.10.1" which may be sensible if there are still some
major wrinkles not well understood or if the fix seems hasty or hackish.

(Let's assume 5.10.2 soon will have it.)

David

On Jul 5, 2009 10:39 AM, "Aristotle Pagaltzis" <pagaltzis@gmx.de> wrote:

* Paul Fenwick <pjf@perltraining.com.au> [2009-07-05 15:05]:
> So regardless of whether or not %^H triggering object
> destruction was an accidental or intentional feature, it's
> now being depended upon by a lot of code, including
> Catalyst::Runtime.

Your defensiveness is not becoming.

Just because it got used by a bunch of code does not make it a
good idea, any more than `my $foo if 0` was, which has certainly
seen far wider use.


* Paul Fenwick <pjf@perltraining.com.au> [2009-07-05 15:50]:

> I certainly didn't expect it to move to "let's boot autodie > from the
core" territory.
That rather surprised me too.

> I don't want to see autodie get pulled from the core
+1

> I'm happy to document the bug and its workarounds
I think at this this time this is the best option.

Next on the agenda: an actual discussion about the needs of
autodie and similar modules. The current reliance on unspecified
behaviours, namely incidental stringification of values at scope
boundaries and respect for magic attched to a special global,
which strike me as very shaky, seems indicative of the fact that
%^H as provided is underpowered for practical use. Let’s figure
out what needs have to be covered and how an explicit, sane and
supported API might look like.

It is reliance on implementation accidents that makes the DarkPAN
(in fact, the mere DarkPAN *meme*) a problem of the magnitude it
currently represents.

Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>

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