Some editors have “Perl Tidy” tools that will automatically reformat source-code without changing it, in order to improve visual consistency within the code. Yes, such changes can be a big improvement, because we are extremely visual creatures.
One thing can be a problem, though ... if you reformat an entire module, a source code control system will perceive that the entire module has been changed. Therefore, what I often prefer to do is to highlight a particular block of code, reformat it automatically, then check-in the file with an appropriate comment. Then, separately, make the changes that I am contemplating, and check those in again. This creates a much clearer history of what was changed and why. Gradually, over the course of time, but only in the areas currently receiving attention for other reasons, the visual quality of the code will improve.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||