in reply to Module Naming Dilemma
I like this idea, but I'm not so crazy about it only working for OO modules (although I understand why it does). Typically I only call new() a small number of times and usually typing the full module name doesn't bother me much.
What does bother me is typing a long module name over and over for every subroutine of a non-OO module. Of course, exporting does address this, but I find that code that makes extensive use of exported subroutines is hard to read because I have to keep bouncing up to the top of the file to figure out where anything is defined (assuming they are good programmers and explicitly imported, rather than implicitly, in which case things are completely hopeless). In cases like this, it would be nice to have a short way of referring to the subroutines, but without losing all context.
|
|---|