in reply to Re: Proper way to create packages and re-usable code?
in thread Proper way to create packages and re-usable code?
WOW, thanks everyone for the great responses.
I understand what you are saying...
Packages should have a narrow purpose and be self contained.
I think I see the error of my ways as the code that I want to re-use does not really fit that mold. Basically I have a bunch of routines that do low level serial communication. All of the routines form a whole program that does the communication, error handling, logging etc. At the top level, there is one routine to call to send/receive a message. I then want to use this code for (let's say) 10 different programs where each program only differs by the main loop which loops and calls the re-usable routines for communication. All I "really" want is to house the re-usable code in a separate "file" so there is only one set of re-usable code to maintain. From what I read on the internets, I gathered that the way to split perl into different files was with a package. However my code doesn't really fit the mold of having singular purpose. I'll do some research on the links provided. I understand that if the whole program was destined to be a 1 million line ERP system, the it would be worth re-organizing and rewriting everything to fit into modules. However I'm aiming at just splitting things into "two" files, and I'm 1 yard from the finish line. So cut/paste into 10 scripts may be the way to go.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Proper way to create packages and re-usable code?
by Hadrianus (Novice) on Feb 12, 2016 at 06:40 UTC | |
by bt101 (Acolyte) on Feb 13, 2016 at 01:47 UTC | |
Re^3: Proper way to create packages and re-usable code?
by Anonymous Monk on Feb 12, 2016 at 01:07 UTC |
In Section
Seekers of Perl Wisdom