Hmm! Am I right in assuming you want to source those shell scripts in order to set environment variables or declare shell functions so they will be inherited by your Perl process and any child processes you spawn?

If so, I don't think it can be done, but I would love for someone to correct me.

However, if your "my.ini" is just a confusingly named Perl script, it's possible to run it using require "my.ini"; but I would definitely not recommend this.

Instead, use proper modules. They're not hard to write, and they will save you lots of backtracking later.

-- FloydATC

Time flies when you don't know what you're doing

In reply to Re: Sourcing another Scripts using perl script by FloydATC
in thread Sourcing another Scripts using perl script by farha89

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.