RE: spurious deaths in script execution due to read-only Config?

2011-02-24 Thread Jan Dubois
On Wed, 23 Feb 2011, Brian Raven wrote: > On Wed, 23 Feb 2011, Christian Walde wrote: > > Solution: Make sure $_ isn't pointing at %Config when Exporter.pm > > happens. This can be done as simple as this: > > > > map { require ActiveState::Path } 1; > > > > (Though i'm sure more elegant solut

RE: spurious deaths in script execution due to read-only Config?

2011-02-24 Thread Chris Wagner
I see what ur saying but I guess I see nothing wrong with %Config being read only and croaking if touched. At 05:18 PM 2/23/2011 -, Brian Raven wrote: >I do recall 'perldoc perlsub' warning about localising tied hashes & >arrays being broken, and %Config::Config is a tied hash, I believe. >

RE: spurious deaths in script execution due to read-only Config?

2011-02-23 Thread Brian Raven
-Original Message- From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Christian Walde Sent: 23 February 2011 15:57 To: perl-win32-users@listserv.activestate.com Subject: Re: spurious deaths in script execution due

Re: spurious deaths in script execution due to read-only Config?

2011-02-23 Thread Christian Walde
On Wed, 23 Feb 2011 16:33:49 +0100, Brian Raven wrote: >>> I remembered this morning that there is a bug tracker for ActivePerl, >>> started to write up an error report and in doing so ended up >>> formulating a possible for for ActiveState: >>> http://bugs.activestate.com/show_bug.cgi?id=89447 >

RE: spurious deaths in script execution due to read-only Config?

2011-02-23 Thread Brian Raven
-Original Message- From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Chris Wagner Sent: 23 February 2011 14:25 To: perl-win32-users@listserv.activestate.com Subject: Re: spurious deaths in script execution due to

Re: spurious deaths in script execution due to read-only Config?

2011-02-23 Thread Chris Wagner
It's the standard behavior of Perl. use Data::Dump "pp"; %a = qw/x 1 y 1 z 1/; grep { $_ } $a{bob}; pp %a; ^D ("y", 1, "bob", undef, "x", 1, "z", 1) At 02:18 PM 2/22/2011 +0100, Christian Walde wrote: >On Tue, 22 Feb 2011 13:46:55 +0100, Chris Wagner wrote: >> At 08:54 PM 2/21/2011 +0100, Chri

Re: spurious deaths in script execution due to read-only Config?

2011-02-22 Thread Christian Walde
On Tue, 22 Feb 2011 13:46:55 +0100, Chris Wagner wrote: > At 08:54 PM 2/21/2011 +0100, Christian Walde wrote: >> use Config; >> # print 1 if $Config{foo}; # enabling this removes the crash >> grep { $_ } $Config{bar}; # this crashes >> >> These two lines on their own will cause Acti

Re: spurious deaths in script execution due to read-only Config?

2011-02-22 Thread Chris Wagner
Hi. U can't do that because Perl must autovivify $Config{bar} in order to have a value to put into $_. HTH. At 08:54 PM 2/21/2011 +0100, Christian Walde wrote: > use Config; > # print 1 if $Config{foo}; # enabling this removes the crash > grep { $_ } $Config{bar}; # this crashes