Considering adding Blank Lines options to the specify the number of blank lines before and after the various conditional and looping constructs such as the following:
Around if [0..n]
Around for [0..n]
Around lock [0..n]
Around try/catch/finally [0..]
Around using [0..n]
Around while [0..n]
...
This may be somewhat complex because this should also allow exceptions if the conditional is at the top or bottom of the method and for nested conditionals. In our code standards, we place blank lines before and after conditionals and looping constructs except at the beginnning and end of methods and for nested conditionals and looping constructs, but I understand other developers may want to alter this code style to fit their needs.
private void Test
{
[exception: no blank line here?]
if(this == that)
{
[exception: no blank line here?]
for(i = 0; i < 10; i++)
{
DoSomething();
}
[blank line here?]
DoSomethingElse();
}
[exception: no blank line here?]
}
Description
Considering adding Blank Lines options to the specify the number of blank lines before and after the various conditional and looping constructs such as the following:
Around if [0..n]
Around for [0..n]
Around lock [0..n]
Around try/catch/finally [0..]
Around using [0..n]
Around while [0..n]
...
This may be somewhat complex because this should also allow exceptions if the conditional is at the top or bottom of the method and for nested conditionals. In our code standards, we place blank lines before and after conditionals and looping constructs except at the beginnning and end of methods and for nested conditionals and looping constructs, but I understand other developers may want to alter this code style to fit their needs.
private void Test
{
[exception: no blank line here?]
if(this == that)
{
[exception: no blank line here?]
for(i = 0; i < 10; i++)
{
DoSomething();
}
[blank line here?]
DoSomethingElse();
}
[exception: no blank line here?]
}