Many thanks for the replies to my post. The first reply asked for some notes on what bits and pieces could be set up to start new code. I have included the command-line usage message printout. (USPTO is a contract I am working on.) And yes, it is strictly command-line, not a workspace as many assumed.

I have heard of github, but have not looked into it. I will do that.

MST 19:49:59.87 C:\temp:newpl Create a skeleton Perl script in the current directory. Usage: newpl [basename] ( optional function list ) ... If one or more function names are specified, the named function(s) will be copied, first by section then lowest priority first, from the master function scripts. Available functions are defined in \c\perl\function. Currently available master functions (p#=priority) include: p0: getargs test argument count and show usage message getopts parse command line arguments for -xx strings p1: envvar Expand an evironment variable in the form {VAR} uspto Extract 'uspto'-related user variable definitions uspto2 A new hash-based implementation of uspto uservars Create user variable hash %uservars log10 Return the base 10 logarithm of a number curdir Get the current working directory name p2: pi use the arctan function for useful multiples of pi time Various routines for dealing with date/time usetime More time demos and applications defext Add a default extension to a given path/file name defext2 Like defext, but includes the forceext function fread Open a file for reading fwrite Open a file for writing readdir Open a directory for reading readsrf Read an SRF file, saving field values in a 2D array psstuff The full Postscript pkg (for direct PS printing) ps_usefmt Include the Postscript pkg (using (pagefmt) run) pause Pause and continue or exit p3: strpack Convert between char strings and index lists cmdline A simple console-interactive command loop
Lloyd

In reply to Re: Starting a New Script by LloydRice
in thread Starting a New Script by LloydRice

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.