Glad to hear that you got test code working. You are now well on your way!
Yes, putting package TEST_GIZMO inside of file TEST_GIZMO.pm would be the normal way. It is possible to have multiple packages within one file. The package is a name space. For what you are doing, that isn't necessary and can get confusing. I would recommend that you put some sort of test function within the package. In one of my libraries, I just put sub test{} in every .pm file and of course didn't export the name "test" as every module has a test sub and the names would conflict. Then to test my library, I just call with the fully qualified name TEST_GIZMO::test; ModuleB::test;, etc. on all the .pm files. It is really handy to have the name of the file the same as package inside. You will see that the .pm file can be run just like a .pl file. So you can have some sort of thing like "test if DEBUG"; DEBUG is a const flag. Anyway the idea is to get the package working with its own test routine before you start calling it from other programs. You should consider your naming convention for your packages. You don't want to use names that might conflict with CPAN packages, etc. Say you've got some project TLA, then you could use TLA_Parse for say the parsing routines for project TLA. You'll have to decide what makes sense for whatever it is that you are doing. |