I tend to dislike the practice of splitting long lines before operators,
Well it depends on the situation in your example it is not such a big deal. However, problems occur when lines tend run long. Example:
# Long line
my $absolutely_very_long_value = $value_reference->{$first_record}{$se
+cond_key}{super_property} + $value_reference->{$second_record}{$secon
+d_key}{super_property};
# Split Line
my $absolutely_very_long_value
= $value_reference->{$first_record }{$second_key}{super_property}
+ $value_reference->{$second_record}{$second_key}{super_property};
I think the worst example for a long-line is something like this,
my $print = qq~
# HTML that goes on for 30+ lines
# This some more text here. text text text text text text text~ if $in
+s{save_changes};
I could have strung up the original programmer for this. This sort of syntax you may not even know you are working on a if statement. You don't see it unless you page down or you have to scroll all the way to the right.
-
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.
|