in reply to Dynamically inspecting Regex OP-Codes at runtime?

I asked in Rx-0.53/dump_regexes.pl as a module because I wanted it to simplify YAPE::Regex::Explain -- easier to extend if perl does the tokenizing

I did come accross re::engine::Hooks and Devel::RegExp, but couldn't compile either at the time ... and its all perlreguts to me, but t/re-engine-Hooks-TestDist/TestDist.xs does look promising

  • Comment on Re: Dynamically inspecting Regex OP-Codes at runtime?

Replies are listed 'Best First'.
Re^2: Dynamically inspecting Regex OP-Codes at runtime?
by LanX (Saint) on Jan 30, 2013 at 11:44 UTC
        Thx for the links but thats Chinese for me.

        I'm not a versatile C programmer and AFAIK even C gurus get depressed when diving into perlguts.

        (BTW: the first link is defunc)

        > I imagine you might be able to peek at a regex structure using B,

        that would be nice...

        > but you can't get at the debug messages, they're not stored, and you can't hook DEBUG_COMPILE macros

        What exactly do you mean with "debug messages"? The token tree with commands like OPEN1?

        Or just message like

        anchored "1234" at 0 (checking anchored) minlen 4 Freeing REx: "(?<C>1)(?<D>2)(3)(?<A>4)"

        The latter I don't need! =)

        Cheers Rolf

        forgot the :)