I am in the midst of porting a custom module as well as some boilerplate code that we currently use on a Unix box to help us run an automated file transfer system. Primarily it connects the Intel side of the house with the Unix side (and vice versa). Even with an off the shelf solution, we still need to customize the some of what gets down (i.e. zip/unzip, de/encrypt with PGP, and so forth). Currently on the Unix side we are running everything with Perl programs. The guts of which is a module that I have put together. There is also a template of boilerplate code that incorporates the basics of what we need down with a minimum of customization on an as needed basis. On the Intel/Windows side, we also need to do some of the same type of work on a per transfer basis but at the moment it is in Batch scripts (which in my opinion are the weakest link in the whole chain). I am investigating using Perl on the Windows side and have had good luck so far and hopefully will be able to move into our test environment by the end of the week (if not sooner).

In porting the Unix code over to Windows, I have learned a few new tricks that will also help make the Unix code better. However, given some of the differences that need to be put into the module for use on the Windows side, I am wondering about issues of maintainability between the Unix and Windows versions of the code. Only 3 of the routines used in the module need major revisions in order to be useful on the Windows side of the shop. I think maybe I'm looking for some direction in keeping the modules reasonably consistent across the two platforms.

The question may have more to do with personal preference or style I suppose than anything else, but I'm curious to see how others respond and if anyone has pointers for a direction that I can look so that the code is fairly straightforward for someone else to be able to maintain if/when I should leave this position. Any thoughts would be appreciated.

"Ex libris un peut de tout"

"Ex libris un peut de tout"

In reply to Of Perl Ports and Maintainability by nimdokk

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.