On Thursday, August 1, 2002, at 11:08 , Paul Tremblay wrote:
[..]
> Certainly, a perl script would be easier to maintain and debug.
>
> Thoughs on how C, java, and perl compare on speed?
I think what you are running into here is that
'c' as is, was not built to do 'regular expression'
work - as 'strings' are not a 'native' "data type".
Some folks compile their c programmes using a
perl embedding trick that allows them to access
some of perl's parsing capability.
So one of your first concerns may well be that you
are timing against badly written 'c' code to begin with.
{ a problem that exists through much of the 'open sourced'
code I have seen - where what is out there is what someone
put out as they were learning... }
As for the other comparatives - you started to answer
your own question with the line:
> Certainly, a perl script would be easier to maintain and debug.
assuming that you have done it reasonably well, and
modular enough, so that you essentially validate it
component wise and build it appropriately.
But as some have noticed, the moment that you start
various types of modularizations you wind up with
the 'overhead' of having 'functions' - hence the
need to stash stuff on the stack, make the jump to
the code segment, and return... Which can lead to
what had been a 'really fast' 'linear' script
becoming slower....
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
