Well ... the speed ... it's both right and wrong. If you translate some code statement-for-statement from C to Perl, then Perl will lose hands down. For a large group of tasks a well written Perl script will beat anything you could write in C in reasonable time to pulp. The built-ins of Perl had been hand-optimized for years so if you can implement the task by a few calls to those built-ins, your program will finish sooner than if you attempt to reimplement them in your own code. In most cases it simply doesn't matter though.
Enoch was right!
Enjoy the last years of Rome.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||