For because?

Syntax hilighting editors (scite) usually highlight the matching parens, ... programmers usually add newlines ...

ppi_dumper knows everything, PPI easily gets you a neat tree, and you can easily adjust the whitespace to your liking ( ppix_regexp_strip_comments )

PPI::Statement
  PPI::Structure::List        ( ... )
    PPI::Statement::Expression
      PPI::Token::Word        'ab'
      PPI::Token::Whitespace          ' '
      PPI::Token::Operator    '+'
      PPI::Token::Whitespace          ' '
      PPI::Structure::List    ( ... )
        PPI::Statement::Expression
          PPI::Token::Word    'fun1'
          PPI::Structure::List        ( ... )
            PPI::Statement::Expression
              PPI::Token::Word        'fun2'
              PPI::Structure::List    ( ... )
                PPI::Statement::Expression
                  PPI::Token::Number          '3'
                  PPI::Token::Whitespace      ' '
                  PPI::Token::Operator        '+'
                  PPI::Token::Whitespace      ' '
                  PPI::Token::Word    'fun3'
                  PPI::Structure::List        ( ... )
                    PPI::Statement::Expression
                      PPI::Token::Number      '4'
                      PPI::Token::Whitespace          ' '
                      PPI::Token::Operator    '+'
                      PPI::Token::Whitespace          ' '
                      PPI::Structure::List    ( ... )
                        PPI::Statement::Expression
                          PPI::Token::Number          '5'
                          PPI::Token::Whitespace      ' '
                          PPI::Token::Operator        '+'
                          PPI::Token::Whitespace      ' '
                          PPI::Token::Number          '6'
  PPI::Token::Structure       ';'

[download]

In reply to Re: paren formatter for function calls? by Anonymous Monk
in thread paren formatter for function calls? by iaw4

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.