I can only wonder though, why you need cross-referencing to get a handle on your project. With a decent design using modern techniques of abstraction and encapsulation, you shouldn't even need it.
Oh!
Well - then probably the best we can do is to tell the B:xxx
authors stop wasting their time implementing such useless tools. While it is almost exactly 13 years since I used (and needed) Cross Referencing on some projects of mine, I completedly disagree, that "modern techniques" and discipline and cleverness (I've added that) are enough to carve complex large prototypes flawlessly in perl.
I had a dispute - long time ago - with a student about the
need of some parser-generator for perl. (Was before Parse::RecDescent, perlyacc etc.). He said:
"You don't need a parser-generator in perl, because you already have regexps. The rest is done in a while-loop."
Your argument seems pretty same to me.
Bye
PetaMem
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.