If all the actions are in different scripts and these scripts are "called" by some marshalling application, it seems to me that this will involve numerous and repetitive starting of a Perl interpreter, loading a single script, running it and breaking it all down again, only to start all over again with the next script. This seems wasteful of CPU cycles and memory.

One refactoring approach could be to gather all these scripts in one module (that shouldn't be too difficult provided all these modules run under the strict pragma: you could then put each script's main code into a separate subroutine and probably factor out some common code between the scripts in basic/general "servicing" subroutines.

Then your Delphi code just has to start one main script which would perform all the actions of the job within the same invocation of the Perl interpreter. That should be more efficient.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

In reply to Re: SQL execution engine - best approach? by CountZero
in thread SQL execution engine - best approach? by Anonymous Monk

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.