Do you really need to access all those commands? E.g. perl can do anything awk can do, you might use DBI/DBD::Oracle instead of sqlplus, File::Find instead of find; opendir, readdir, and maybe stat or one of the -X operators (I see more code that does 'ls -l' and cuts out the file size than I care to) instead of ls; @INC and -x instead of which...
I do write scripts occasionally which access unix commands, but the last time I did that, the command was 'patch', and there didn't seem to be anything on CPAN, and it saved alot of perl programming. And maybe if you have a sqlplus script which outputs a formatted report, I might keep that, since it would be alot of work to redo it in perl. Otherwise I'd look at what you really need.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|