in reply to Re: Adding or removing keys while iterating over a hash
in thread Adding or removing keys while iterating over a hash

guess perlmonk's docs must be from 5.005_3. I checked on perl.com as well beforehand, but they have the same answer. Does that mean that perl 5.6 isn't considered authoritative yet?
Most of us with real machines to run are holding at 5.5.3, waiting patiently for 5.6.1 to be released in a few more weeks (as they've kept saying for three months now {grin}), having considered 5.6.0 as only for "early adopters". And of course 5.7.0 was "over the bleeding edge".

-- Randal L. Schwartz, Perl hacker

  • Comment on on 5.5.3, waiting for 5.6.1 (was Re: Re: Adding or removing keys while iterating over a hash)

Replies are listed 'Best First'.
Re: on 5.5.3, waiting for 5.6.1 (was Re: Re: Adding or removing keys while iterating over a hash)
by mischief (Hermit) on Nov 30, 2000 at 15:39 UTC
    Why are you using 5.5.3 instead of 5.6.0? You say that 5.6.0 is for "early adopters", but personally I don't know any reasons for not using the later versions (not to say that there aren't any reasons; I'm just ignorant of what they are). I'm by no means a perl guru, so as far as I can see 5.6.0 just has some nice features that I would like to use. All the modules I want to use are compatible with 5.6.0, and there are a few little things that I have been using in my scripts like our(), use warnings and delete()ing array elements. None of these are really essential to what I'm doing of course, but they're nice.

    I'm quite happy to accept that 5.6.0 isn't ready for use on production machines, but could someone tell me why, or where to find out why? Thanks in advance for any pointers.

    (Apologies for the late reply, but I haven't really been in a position to until now.)

      Try this:
      perl -e 'my $x = 10; $x = "2" . $x; print $x + 0'
      With 5.6.0 this prints 10.

      There are many other things wrong with 5.6.0, but this one is generally good enough to make the point.

        Wow -- that's freaky. Dropping the my declaration makes the problem "go away", too.