Hi,

it's the 25% that bite us (both): 

rj@pollux:~/_ELRIC/implementation/src/examples> perl -MO=Xref -we 1
File -e
  Subroutine (definitions)
    Package UNIVERSAL
      &VERSION          s0
      &can              s0
      &isa              s0
    Package attributes
      &bootstrap        s0
-e syntax OK

[download]
and - btw. B::XRef works "good" for all smaller scripts I call it on as long as they aren't complicated and ~ 50 lines of code not more. Even then: 
Use of uninitialized value in string eq at /usr/lib/perl5/5.6.1/i586-l
+inux/B/Xref.pm line 117.
Use of uninitialized value in substitution (s///) at /usr/lib/perl5/5.
+6.1/i586-linux/B/Xref.pm line 124.
Use of uninitialized value in string eq at /usr/lib/perl5/5.6.1/i586-l
+inux/B/Xref.pm line 117.
Use of uninitialized value in substitution (s///) at /usr/lib/perl5/5.
+6.1/i586-linux/B/Xref.pm line 124.
Use of uninitialized value in concatenation (.) or string at /usr/lib/
+perl5/5.6.1/i586-linux/B/Xref.pm line 130.
Use of uninitialized value in string eq at /usr/lib/perl5/5.6.1/i586-l
+inux/B/Xref.pm line 117.
etc. etc. (cut for node readability)
Use of uninitialized value in substitution (s///) at /usr/lib/perl5/5.
+6.1/i586-linux/B/Xref.pm line 124.
Use of uninitialized value in concatenation (.) or string at /usr/lib/
+perl5/5.6.1/i586-linux/B/Xref.pm line 130.
Use of uninitialized value in concatenation (.) or string at /usr/lib/
+perl5/5.6.1/i586-linux/B/Xref.pm line 130.

[download]
Ugly isn't it? But after that the references spill out. So one must say: unusable for larger projects. Who needs cross references on small scripts???

Update:

I thought B::Xref spills out human readable output by default (no params).. :-) Is this considered human readable? 

  Subroutine deflate
    Package (lexical)
      $$eref            51
      $@$$eref          56
      $@$@$$eref        60
      $@$@$@$$eref      65
      $@$@$@$@$$eref    70
      $eref             i50, 51
      $i                i55, 56, 59, 59, 55, 70, 71
      $inner            i60, 62, 63, 64, 55, 69
      $j                i59, 60, 65, 66, 67, 59
      $key              i49
      $outer            i56, 62, 63, 64, 55, 69
      $size             i51, 66, 59, 55, 71
      @$$eref           51, 56
      @$@$$eref         56, 60
      @$@$@$$eref       60, 65
      @$@$@$@$$eref     65, 70
      @$@$@$@$@$$eref   70
    Package main
      @_                49, 50

[download]

Bye
 PetaMem

Edit by tye to change PRE tags to CODE tags

In reply to Re: Re: Perl Cross References by PetaMem
in thread Perl Cross References by PetaMem

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.