I can think of lots of reasons not to do this...
- There are lots of good styles and exposure to them all will help you develop your own.
- If someone needs to improve their style, but they can hide that fact with the push of a button, they may never receive some much needed advice and direction.
- Server load.
- Reading poorly formatted code will help you improve your maintenance skills.
- A disconnect between the code they are helped with and their actual code will make it harder for them to implement suggested changes.
- Just try getting all the editors to agree on one recommended style.
- Formatting code fragments would often not give desirable results anyway.
- I don't see an easy way to integrate this into the existing interface. We can have multiple code sections, for instance. They can be inline if we want. Etc. How can you decide which to run through perltidy?
- This would be a poor alternative to suggesting to someone that he download perltidy himself and learn to use it.
And, I don't see one good reason to do it.
Somewhere else in this thread you said, "Indentation isn't really standardized, but on a single message board (perlmonks.com), it should be." I disagree, but that's okay. You've expressed an opinion. Now, present an argument to support it.
-sauoq
"My two cents aren't worth a dime.";
-
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.
|