Hi Valerio

yes, I know about DProf, but I was looking for static analysis. DProf requires you to run the code, it then profiles it and you can look at e.g. which subroutines are slowest. It can also print out a subroutine call tree, however, I don't know that there are any ways of limiting this call tree to only show "my" code (not code from external modules I am using.)

While I'm on the subject, one more wish I forgot: use everywhere; - a way to import stuff to all my namespaces. Useful for quick development, e.g. use everywhere 'Data::Dumper', qw/Dumper/;

dave hj~

In reply to Re: Re: wishlist: static analysis of perl modules by dash2
in thread wishlist: static analysis of perl modules by dash2

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.