Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

gnat (29)

gnat
  (email not shown publicly)

Journal of gnat (29)

Thursday June 12, 2003
10:54 AM

What Things Cost

[ #12769 ]
What Things Cost is worth reading even if you aren't a .NET programmer.

--Nat

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Instead of looking at the cost in low-level ops, try system call tracing or malloc tracing (strace and e.g. valgrind in Linux) and see what kind of a pig "perl -le 'print 42' is". Compare with
    #include <stdio.h>
    int main() { printf("42\n"); return 0; }
    Not to mention comparing with chucking the include and going for write(1, "42\n", 3)... For a really scary output move up to, say, "perl -MCGI -e 1".