I think you're arguing against a point I didn't make.
(Though, in fairness, I might have been arguing against
a point you didn't make.) I didn't suggest that
optimization was unimportant or even undesirable; rather,
that given a program almost entirely written in Perl,
there's usually no point in speeding up the C bits. The
key word is "usually", BTW; my main point is that
optimization should only be attempted when profiling shows
that the effort will be rewarded.
UPDATE: The following complaints are wrong;
please ignore them. I've left them here for hysterical
raisins, and so replies don't seem confusing.
BTW, you don't help your case when you use punctuation
marks that are neither ASCII nor Latin-1; it makes your
comments hard to read. Let me guess:
You're using Windows, right? You ought to look at your
comment from a Unix system; it has lots of question marks
where they don't belong.
-- Chip Salzenberg, Free-Floating Agent of Chaos
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|