NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Interesting... (Score:1)

by jplindstrom (594)

I tried something similar in PerlySense, but I consider it a failed experiment.

In the Overview, there is (well, was) a Signature Survey [cpan.org] of the file, i.e. a char for each type of "thing" in the file (pod blocks, subs, statements, string literals, etc). Like this:
* Structure * ;;;';;;;;;;{;";}{;;;;{}"";{}"";";}{;;;';';";;;{;'";;';;; };';}S{;";"";;}S{;' {}{"};;;}S{;;;;";";;};

I got the idea in an interesting article about Software Archeology [pragprog.com].

I had hoped it would give me a kind of ambient feel of the structure
Something simpler (Score:1)

by sigzero (5768)

I have only seen something that breaks code into a flow chart. Nothing so fancy as what you want to see.
Swoosh, swoosh (Score:1)

by jplindstrom (594)

I saw this [whitney.org] on Reddit just now.

More cool than useful perhaps, but definitely very cool :)
Here's a kinda-sorta solution (Score:2)

by drhyde (1683)

Many years ago I was having trouble remembering how my code interacted with itself, so wrote this [cantrell.org.uk]. It produces a text report of what subroutines call what subroutines, and what subroutines are called by what subroutines.
The code is hideous, and I wouldn't dream of writing it that way now, but on the other hand it does mostly work, and might make a good starting point. If anyone wants to have a go at improving it, be my guest.