comment on

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

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks