Who the heck is Elaine Ashton? And why are you asking me to listen closely to her without providing a single link to something she has said that relates to the topic at hand?
As for a formal relationship to CPAN, I think supporting a CPAN link tag and the CPAN search nodelet are enough. The code here is different from the code at CPAN-- and I'm sorry if you think that's somehow denigrating to either PM or CPAN, but it's not. I mean, this is a non-issue or someone would be spouting off about it in c.l.p.* (or have they and I didn't notice?). And yes, centralization of resources is a bad thing. Especially when the resources don't have that much in common. Sure they're both in Perl, but the scripts here are usually what I would consider application space (designed to be used by users) and exemplary code (designed to be learned from, not necessarily used as is) and CPAN is what I would consider perl space (code designed to extend perl for the programmer).
-
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.
|
