C#

for (Int32 i = 0; i < 10; i++) {
    if (i == 8)
        break;
}

bool found = false;
int counter = 0;
do
{
  if (loop[counter] == 1)
    found = true;
} (while !found || ++counter == loop.Count);

pmarfleet wrote:

The second snippet looks like a property declaration for an Interface.

donsolms wrote:

it does, but you can use it in a normal class as well

Robert Rohde wrote:

You are wrong. What it does is to implicitely create a private field which is accessed (I think this was introduced with .Net 3.5). Up to there you could just create a public field instead but this one has the advantage that you can replace it with a real property/field pair at any time without having to change anything on accessing classes.

donsolms wrote:

Which is better according to coding standard for c#?

this:


public bool isDraggable
{
get { return _draggable; }
set { _draggable = value; }
}


or this:


public bool isDraggable{ get; set; }


without using private members? Or is this a matter of personal choice?

donsolms wrote:

Which is better according to coding standard for c#?

this:


public bool isDraggable
{
get { return _draggable; }
set { _draggable = value; }
}


or this:


public bool isDraggable{ get; set; }


without using private members? Or is this a matter of personal choice?

Matthew Cuba wrote:

the compiler would generate some private fields

Matthew Cuba wrote:

For Orcas, I thought that these were essentially identical

Scott Dorman wrote:

with the second one allowing the compiler to automatically generate the backing variable.