Are predicates worth it?

[David Veeneman]

I've been looking at predicate delegates in connection with List<Tsearch
methods. My initial reaction is that the mechanism looks cumbersome, to the
point where I'm wondering if it's not just simpler to stick with a foreach
loop.

If I understand List<Tsearch predicates correctly, I'll need to write a
predicate, which is no big deal. But I will also need a member variable to
set the value of the search criteria that the predicate uses.

In other words, if my search criteria is fixed (like the 'ends in -saurus'
example in MSDN), then I only need the predicate. But if I want to create an
'ends in whatever' predicate, I have to create a string member variable to
contain the 'ends in' criteria that is to be used for the search. The
predicate uses the value of the member variable to make its comparison.

Here's my question: Is it worth it? What do I gain over writing a method
with a simple foreach loop to do the search? Thanks.

--
David Veeneman
Foresight Systems

[William Stacey [MVP]]

Guess it just depends on which you prefer:

private List<stringEndsIn(List<stringlist, string value)
{
// Using FindAll predicate
return list.FindAll(delegate(string s)
{
return s.EndsWith(value);
});
}

private List<stringEndsIn2(List<stringlist, string value)
{
// Using Foreach
List<stringlist2 = new List<string>();
foreach ( string s in list )
{
if ( s.EndsWith(value) )
list2.Add(s);
}
return list2;
}

--
William Stacey [MVP]

"David Veeneman" <da****@nospam.com (domain is my last name)wrote in
message news:e%***************@TK2MSFTNGP03.phx.gbl...
| I've been looking at predicate delegates in connection with List<Tsearch
| methods. My initial reaction is that the mechanism looks cumbersome, to
the
| point where I'm wondering if it's not just simpler to stick with a foreach
| loop.
|
| If I understand List<Tsearch predicates correctly, I'll need to write a
| predicate, which is no big deal. But I will also need a member variable to
| set the value of the search criteria that the predicate uses.
|
| In other words, if my search criteria is fixed (like the 'ends in -saurus'
| example in MSDN), then I only need the predicate. But if I want to create
an
| 'ends in whatever' predicate, I have to create a string member variable to
| contain the 'ends in' criteria that is to be used for the search. The
| predicate uses the value of the member variable to make its comparison.
|
| Here's my question: Is it worth it? What do I gain over writing a method
| with a simple foreach loop to do the search? Thanks.
|
| --
| David Veeneman
| Foresight Systems
|
|