On Fri, 19 May 2000, Doug MacEachern wrote:
> > C seems like serious overkill for something to simply generate plain text
> > output. How slow is making a string in perl compared to doing it in C?
> > I can't imagine there's to much of a difference.
>
> more like Perl is serious overkill :)
> SV's are BIG, notice the $unused variable and the B::TerseSize output
> (from Apache::Status) below, even before a string is copied into it,
> there's 48 bytes eaten.
Well, my point was that the decision to code something in C should be done
because it offers an overwhelming (orders of magnitude) improvement,
preferably on more than one front (speed, memory, ease of maintenance
(haha) ).
Really, if you feel that Perl is too memory hungry and slow for even
simple text output, then why use Perl at all?
My bias is against C because I don't like it and I think it makes the
module less accessible to people and therefore less likely to get improved
by the community at large, and more likely to only get worked on by 1
person.
-dave
/*==================
www.urth.org
We await the New Sun
==================*/
