Now I totally disagree. If you have several ten thousand lines of Perl code in a project. And a well written project I might add (at least as well as real-world circumstances allow). And you want to orient yourself and/or clean up....
To put it simple: Get more insight to the code
You will need cross reference.Period.
It is extremely hard to find anything usable for Perl that actually works. And I must - sorry - scoff on the old argument that Perl code can be generated at runtime and therefore all trials for Xreferencing perl are futile. Yes. So what? If I can solve/cover 95% of all perl code there is!?
I'm currently seeing two/three alternatives that could prove usable for Perl X-referencing:
Imenu tagging in Emacs works, but gives you only a hierarchy-popup that allows you fast browsing from a set of files down to the method/function level.
ECB is supposed to be able to utilize the Imenu tagging information and should then work well. Well...
I hope I will be able to find a *working* X-referencing system for Perl anytime soon, as you simply need it from a certain complexity and volume of your project.
Bye
PetaMem All Perl: MT, NLP, NLU
In reply to Re^2: x2 Perl Cross References REVISITED
by PetaMem
in thread Perl Cross References
by PetaMem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |