Survey Results

rickyvj wrote:

I don't think the time you save by typing less is worth the readability you give up

rickyvj wrote:

IntelliSense is so great

rickyvj wrote:

I think we need to learn and leverage the tools we already have before asking for new ones

rickyvj wrote:

I'm surprised to see how most developers don't take the full advantage of VS or C# advanced features.

pane.YAxis = new YAxis{
 IsVisible = true,
 Type = AxisType.Linear,
 Scale.FontSpec.Size = 9, 
 Scale.FontSpec.IsAntiAlias = true
};

rickyvj wrote:

or create object references and deal with those directly, for example:

string s;
myObject.
{
    s = .ToString();
}

Dim s as String
With myObject
    s = .ToString()
End With

PIEBALDconsult wrote:

the same as the Turbo Pascal with, which I never used

Don Kackman wrote:

I find statements with with harder to read

Jeremy Falcon wrote:

$20 says it's mainly because you're not used to it. After using it for years I can say it's not that hard.

with myObject
   .field1 = 0
   .field2 = 1
end with

with myObject
   .field1 = 0
   if someBool then
     .DoSomething
   end if

[20 lines later]

   .DoSomethingElse

[20 lines later still]

   .field3 = .field1 + .field2

[at the bottom of a 500 line method with a bunch of other logic intertwingled]
end with

Don Kackman wrote:

Sweet! You owe me $20!

Don Kackman wrote:

All of the above mixed in with loops, branches and other objects being used.

Don Kackman wrote:

I think the with statement is really nothing more than a reaction to VB's excess verbosity, saving some keystrokes and sacrificing readability and maintainability.

Jeremy Falcon wrote:

I reckon to each his own, but methinks the abuse of it is the real issue more than having it available to use when needed.

Don Kackman wrote:

But you still owe me $20!