Why do you need to find them? There's a while, for, eval, if, sub or something like that at the start of the line and the following ones are indented.
| [reply]
[d/l]
[select] |
Many times there is. But blocks do not always have control structures. And there are often times when you need to break the control up into multiple lines for readability.
If you ever want to comment out those lines or even the whole block, it is much nicer to have the open curly on its own line.
| [reply] |
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
) {
...
...
}
| [reply]
[d/l] |
