HP3000-L Archives

September 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Sat, 8 Sep 2001 21:00:27 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
"Duane R. Larkin" wrote:
>
>   I am interested in feedback on performance differences between CI scripts
> and Perl scripts.  Is there a speed advantage, one over the other?  I'm new
> to CI programming and am also wondering about it's limitations (if any)
> when compared to Perl.  Can anyone speak to that?  My initial general
> scripting requirements are around job management and simple file I/O.  As
> an example I am trying to automate logging of information created in a
> STDLIST by many of the jobs we run.  From an ease of use and performance
> standpoint, which may be better, CI/UDC or Perl?

"It depends."  ;-)

If your script needs to execute zillions of MPE commands, then a CI script will
be faster than Perl, unless you use Ken Hirsch's HPCICOMMAND Perl module.

If you need to do complicated pattern matching and string manipulation, Perl
will kick butt on the CI.  If you will be scanning $STDLIST spoolfiles, I
suspect you'll want to use Perl for it's pattern matching abilities.

Since you have a Unix background, you will probably be productive faster using
Perl.  And of course you can tap into the glory that is CPAN for zillions of
add-on Perl modules.
--
[log in to unmask]
Remainder of .sig suppressed to conserve scarce California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2