If so, how bad is it just to edit perltidy's output yourself to fix these cases?
As I understand it, the ideal is to use Perltidy quite often, as one part of the edit cycle, cleaning up any unintentional goofs and restoring to the 'standard' formatting. Perltidy is not a one-time or once-a-month thing, rather it is supposed to be done at least before each time you check your changes back into the repository.
So you shouldn't have to clean up after the cleaner-upper. Indeed, it is this problem that has so far kept me from using Perltidy as intended.
-
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.
|