exit loop iteration case

[csharpula csharp]

Hello,

I am iterating through objects and have the following case:

foreach (classA objectA in classAList)
{
if (classA.count0)
{
//now I need to get out of the foreach loop if so,otherwise to keep
iterating
}

}

What is the best way to do it?

Thanks!

*** Sent via Developersdex http://www.developersdex.com ***

[Navid]

csharpula csharp wrote:

Hello,

I am iterating through objects and have the following case:

foreach (classA objectA in classAList)
{
if (classA.count0)
{
//now I need to get out of the foreach loop if so,otherwise to keep
iterating
}

}

What is the best way to do it?

Thanks!

*** Sent via Developersdex http://www.developersdex.com ***

to simply just get out of the iteration is some condition becomes true
you can use break;
foreach (classA objectA in classAList)
{
if (classA.count0)
{
break;
//now I need to get out of the foreach loop if so,otherwise to
keeiterating
}
}

[Jeff Johnson]

"csharpula csharp" <cs*******@yahoo.comwrote in message
news:u1**************@TK2MSFTNGP04.phx.gbl...

I am iterating through objects and have the following case:

foreach (classA objectA in classAList)
{
if (classA.count0)
{
//now I need to get out of the foreach loop if so,otherwise to keep
iterating
}

}

What is the best way to do it?

You've been given the answer, but just for completion, the opposite (so to
speak) of "break" is "continue." It's used far less and some would probably
argue that if you structure your code right you'll never need to use it.

[Jon Skeet [C# MVP]]

On Oct 23, 7:35*pm, "Jeff Johnson" <[e-mail]:

You've been given the answer, but just for completion, the opposite (so to
speak) of "break" is "continue." It's used far less and some would probably
argue that if you structure your code right you'll never need to use it.

Those are probably the same people who always use a single exit point
from a method, regardless of how much less readable that makes the
code ;)

Jon

[Peter Morris]

>
Those are probably the same people who always use a single exit point
from a method, regardless of how much less readable that makes the
code ;)
<

Despite people I know advocating having only a single exit point from every
method, I am always much happier doing this

public void DoSomethingIfNotNull(object instance)
{
if (instance == null)
return;

//lots of code here
}

than this

public void DoSomethingIfNotNull(object instance)
{
if (instance != null)
{
//lots of code here
}
}

--
Pete
====
http://mrpmorris.blogspot.com
http://www.capableobjects.com

[Jon Skeet [C# MVP]]

On Oct 24, 10:11*am, "Peter Morris" <[e-mail]:

> Those are probably the same people who always use a single exit point
from a method, regardless of how much less readable that makes the
code ;)

<

Despite people I know advocating having only a single exit point from every
method, I am always much happier doing this

<snip>

Exactly. It's just a case of being pragmatic.

Jon

[Jeff Johnson]

"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:45**********************************@c60g2000 hsf.googlegroups.com...

Exactly. It's just a case of being pragmatic.

<AOL>
Me too!
</AOL>

[Peter Morris]

Exactly. It's just a case of being pragmatic.
I tried it once;
but hated seeing;
text that looked
like this; // :-)
}
}
}
}
}
}