As you've written it, you aren't really saying code re-use is good, you're saying only code-reuse is good.
I don't think so, especially if it lets you draw the following
conclusion from that...
This is the same fabulous rhetoric, "Don't reinvent the wheel." There would be no Perl at all if Larry had taken these adages to heart b/c he could have re-used the shells, C, awk, and sed and pretty much covered what the first few versions of Perl did and then some.
The important difference between what Larry did to create Perl and what most people do when they "reimplement" a templating system or a CGI param parser is that Larry carefully studied prior art.
I have no problems with people reinventing things when they've already studied prior art. But 90% of the time, I see that people are merely reinventing things because it "wasn't invented here" or "I think I can do better" or "I didn't know something already existed" or "the author is not accepting my patches". Those reasons are insufficient for me, and I'm doing my best to stop that.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
-
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.
|