in reply to Source-Code Analysis?

Ok, this is no help, but I ++ your node for one reason:

"Please, no ready answers, I need to figure things out by myself, and maybe roll my own solution out-of-the-box"

this is an attitude which I believe embraces the spirit of the Monastary. Some will reply with the reinventing the wheel arguement, but I still think learning for yourself how things work before going to ready solutions is a good thing to do.


"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!

Replies are listed 'Best First'.
When reinventing the wheel, examine the wheel you're reinventing
by PodMaster (Abbot) on May 18, 2004 at 03:42 UTC
    Module::ScanDeps is one wheel that comes to mind. When reinventing the wheel, it's best to seek out existing wheels for ideas.

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
Re: Re: Source-Code Analysis?
by andyf (Pilgrim) on May 19, 2004 at 13:24 UTC
    *Agrees Rex, Just enough of a pointer, or it spoils the fun, healthy attitude. @Mnsr. Champs, <spelling nazi> Analize. No No No! Analyse. Analize is _something_quite_different_altogether_. </spelling nazi>
[reply]

In Section Seekers of Perl Wisdom