in reply to Re: Printing an object when you only have the refaddr string for it
in thread [SOLVED] Printing an object when you only have the refaddr string for it

Yeah, I verified it's still allocated using Data::TreeDumper. Will give this a run through and let you know what happens.

LOOKING FOR ADDR ARRAY(0x7fa9bc68be78) . . . | | | | | | | | | | | | | | | |- 3 [ +A220] ARRAY(0x7fa9bc68be78)

Nested quite deep as you can see.
  • Comment on Re^2: Printing an object when you only have the refaddr string for it
  • Download Code

Replies are listed 'Best First'.
Re^3: Printing an object when you only have the refaddr string for it
by delias_ (Acolyte) on Nov 05, 2015 at 21:57 UTC
    Yeah this definitely does what I was wanting. Now to go read up on some perlguts, thanks :)
    LOOKING FOR ADDR: ARRAY(0x7faf34532148) PRINTING REF: $VAR1 = [ 'curItem', 0 ]; . . . | | | | | | | | | | | | | | | |- 3 [ +A220] <187> ARRAY(0x7faf34532148)
    The hex conversion throws a portable warning (to warn 32 bit users I guess) if you weren't aware, but that's neither here nor there.