In RE: RE: Re: Perl secrets, I muse:
It would be nice if someone at work coded some, specifically Perl, ya' know, someone to peruse my code on occassion, but there's nobody.
But think of the experts you have here! Maybe I need to get vroom to create
a section called Code Review, where we could post snippets (perhaps anonymously, with a private feedback link) and let others issue code review, but
telling still others that this is perhaps questionable code.
|
Hmm. An interesting idea. A place for monks to get honest, open feedback about
their code, flagged in a sense that this "might not be the best way to do it", or even
"this may be a pretty narrow application". Nobody posts here unless they want
direct feedback.
Any takers? Any interest? Can the everything code already handle some sort of
private feedback, or would it all have to be public nodes?
-- Randal L. Schwartz, Perl hacker
Edit: 2001-03-03 by neshura
-
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.
|
