jepri has asked for the wisdom of the Perl Monks concerning the following question:

I've exhausted every other avenue so now I'm posting. I want to tweak B::Deparse to get some different output and I am completely lost. I don't know exactly how perl implements the perl parse tree but I want to find out.

I went to the perl websites, I downloaded the source, but there's no design guide around or anything. I can't read the C that Perl is written in (not at that level)

From what I can see in B::Deparse it gets a bunch of objects and then builds output based on some kind of semi-functional programming methodology. I'm looking for 'what structure does it get handed from the parser and how can I tweak it'

Is there a document detailing what I want to know or should I start on the sauce?

____________________
Jeremy
I didn't believe in evil until I dated it.

Replies are listed 'Best First'.
Re: Perl parse tree inquiry
by stefp (Vicar) on Sep 12, 2001 at 12:47 UTC
    If you want to know the parse tree format (that is really gruesome) you should read Gille Aas aptly named illguts and Simon Cozens internals.

    -- stefp

Re: Perl parse tree inquiry
by Zaxo (Archbishop) on Sep 12, 2001 at 08:32 UTC

    B::Deparse has a -uPACKAGE option allowing you to load runtime resolved subs. You could try loading some pry ant print subs through that.

    After Compline,
    Zaxo