in reply to Re^3: perl5.10 Devel::Size behaviour changed?
in thread perl5.10 Devel::Size behaviour changed?

I'm still stuck without any clue as to how to handle this. :( Any ideas?
  • Comment on Re^4: perl5.10 Devel::Size behaviour changed?

Replies are listed 'Best First'.
Re^5: perl5.10 Devel::Size behaviour changed?
by BrowserUk (Patriarch) on Sep 09, 2009 at 08:53 UTC

    Sorry no. Except petition p5p to back out the core change that causes this and revert to 5.8.9 until they do.

    Beyond that, realise that this is a few tens of extra bytes per array; if the array holds more than half a dozen scalars, then this new overhead just gets lost in the noise.

    And Devel::Size is a development/testing tool. Once you've sorted out whatever malady caused you to go looking, and stop using D::S, then for the most part you won't be getting those extra bytes any more.

    Finally, go through your code and change any references to $#array to ( scalar( @array ) - 1 ) and litter your code with large comments explaining why these should not be reverted.

    I don't think that there is anything you can do to an ex-OSS programmer, if they leave behind time bombs :)


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
Re^5: perl5.10 Devel::Size behaviour changed?
by Anonymous Monk on Sep 09, 2009 at 07:31 UTC

      It will show the exact same symptoms as it uses the exact same core macros to to test if there is any magic attached to the AV*--which since 5.10 causes there to be magic attached whether it is needed or not.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.