If the block does not have a statement it belongs to then of course the opening curly will be the first and only thing on a line. Which is yet another reason not to put the ones that do belong to a statement on the beginning of a line. I'd rather know whether something is the body of a loop or other control structure or a bare block introduced to limit the scope of some variables. And if I ever need to comment out the whole block, I'll need to comment out the statement as well.
As for statements broken into multiple lines ... you may use different level of identation. Say two spaces for multiline statements and four for blocks. I do not find the need, I do not write that many multiline statements, those I do usually do not start with statements that have a block, and if they do I'll indent them somewhat line this:
while (some
very very
complex condition
) {
...
...
}
-
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.
|