The following is not the proper way to modularize your code, but because you are just 'one yard before the finish line' you could use a script or Makefile to concatenate multiple files to a single program. That is easier and less error prone then the temporary "manually cut and paste" solution, that you are considering.

Assuming you have the following files:

-rw-r--r--  1 hadri  hadri   51 Feb 12 04:24 main_barack
-rw-r--r--  1 hadri  hadri   63 Feb 12 04:15 my-serial-library.src
-rw-r--r--  1 hadri  hadri   68 Feb 12 04:27 postlude_general.src

[download]

Your general libary routines are in my-serial-library.src and postlude_general.src. The 'main' program is the only customized part and is named after your client or location: main_barack.

With a simple Makefile you can generate your program serial_com_barak.pl:

$ make
cat my-serial-library.src main_barack postlude_general.src > serial_co
+mm_barack.pl

[download]

For another customer you create a new customized main and run 'make' again:

$ echo "This is for Bernie" > main_bernie

$ make CLIENT=bernie
cat my-serial-library.src main_bernie postlude_general.src > serial_co
+mm_bernie.pl

[download]

The Makefile:

 # -- sample Makefile
CLIENT          =       barack

NAME            =       serial_comm
PROG_NAME       =       ${NAME}_${CLIENT}.pl

PRELUDE         =       my-serial-library.src
MAIN            =       main_${CLIENT}
POSTLUDE        =       postlude_general.src

TAR_NAME        =       serial-comm_${CLIENT}.tgz
TAR_FILES       =       Makefile
TAR_FILES       +=      ${PRELUDE} ${MAIN} ${POSTLUDE}

${PROG_NAME}: ${PRELUDE} ${MAIN} ${POSTLUDE}  
        cat ${PRELUDE} ${MAIN} ${POSTLUDE} > ${PROG_NAME}

clean:
        rm -rf ${PROG_NAME}

archive:        
        tar cvzf ${TAR_NAME} ${TAR_FILES} 

# --- end of Makefile

[download]

Note: Make sure that you have a tab character (\x09, CNTRL-I or ^I) before the cat and other commands in the Makefile.Verify with 'cat -t Makefile':

${PROG_NAME}: ${PRELUDE} ${MAIN} ${POSTLUDE}  
^Icat ${PRELUDE} ${MAIN} ${POSTLUDE} > ${PROG_NAME}

[download]

In reply to Re^3: Proper way to create packages and re-usable code? by Hadrianus
in thread Proper way to create packages and re-usable code? by bt101

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.