I was afraid you were going to say that :)
I might as well move ALL code into Plx.pm, then, and just always use that all my scripts.
This is disappointing because I like to separate code into libraries for solely administrative reasons. When I'm working on Language Services, for instance, I think about a set of concepts common to all linguistic functions. Even if there are no global variables, it helps if all references to space available on a disk is always called SpaceAvailable rather than some being called SpaceAvailable and others called AvailableSpace.
Is there any way in Perl to segregate collections of functions this way, or must they always be lumped into a single master library? | [reply] |
Usually, people use modules for that.
If you feel that there is no way to partition your code by functionality to keep it in separate packages, maybe you can show us some code which you have problems to untangle.
When dividing up functionality between modules, you will always have to strike the balance between separation and ease of use. The main advantage of putting everything into one module is that you only need one use statement at the top of your program to import all the functionality.
| [reply]
[d/l] |
If Plx needs functions from PlxHml, and PlxHml needs functions from Plx, how exactly do I implement this? Thanks.
| [reply] |