in reply to How can I turn an op address into the right kind of B::OP?

Crossposted to StackOverflow, with more details there. Crossposting is acceptable, but it is considered polite to inform about it so that efforts are not duplicated. (I understand the crosspost, because you didn't get any responses here - although feel free to add the additional information here as well.)

  • Comment on Re: How can I turn an op address into the right kind of B::OP?

Replies are listed 'Best First'.
Re^2: How can I turn an op address into the right kind of B::OP?
by rockyb (Scribe) on Jul 17, 2018 at 11:53 UTC

    Yes, I understand. Thanks for pointing that out both here and on StackOverflow.

    I will update this as soon as there is some sort of closure on this.

    Note that I waited a day for some response here; currently there is nothing much to report either here or in StackOverflow. In StackOverflow though, there was a little more verbiage if only to get more clarification. So right now see StackOverflow if this question is as confusing to you as appearently it was (is?) to Mike Schwern.

    Again, I will update with condensed summary information here when there is something to report, as I have done in the past where I have received help on StackOverflow but also asked on PerlMongers first. To do it while things are in the air doesn't seem like a worthwhile use of time and and may be confusing for folks as well.

    Similarly, if there is activity here, I'll update the StackOverflow side when there is some sort of closure.

    Of course, monks and others can just follow one place if that's what they prefer. Ultimately, you'll find the same information (albeit in condensed form) in either place.

[reply]
      So right now see StackOverflow for this if this question is as confusing to you as appearently it was (is?) to Mike Schwern.

      I'm not an expert on the internals, so I just don't have an answer to your question in this case (at least not yet, maybe someday ;-) ). Also, I'm not sure what your use case is, that is, I can't judge if this might be an XY Problem or not.

[reply]
[d/l]

        Use case: Devel::Trepan currently reports offsets when it is stopped. It gets this from Devel::Callstack currently. However in the past it didn't, although I can't remember the details, other than it was by some other means as an undocumented feature (which means it is not guarenteed to work in the future).

        More generally, if the full OP were available, more information could be gleaned about where Perl is at any given time. It also might be used as a way in decompilation to walk around the point of interest rather than starting from the top and decompiling everything.

        I'll be giving a talk on this at Glasgow YAPC 2018, so come see me there for more information. ;-)

[reply]

In Section Seekers of Perl Wisdom