Fast Case Insensitive String Comparisons

[Merk]

What are some alternatives to using .ToUpper() to perform case insensitive
string comparisons?

The reason I'm asking is that I'm comparing strings in a long loop, looking
for equality; and I want for this loop to run as fast as possible. So I'm
looking for a method that would be faster than .ToUpper().

Thanks!

[Andy]

Did you try specifying case insensitivity in the .Compare method?

Merk wrote:

What are some alternatives to using .ToUpper() to perform case insensitive
string comparisons?

The reason I'm asking is that I'm comparing strings in a long loop, looking
for equality; and I want for this loop to run as fast as possible. So I'm
looking for a method that would be faster than .ToUpper().

Thanks!

[Marc Gravell]

In 2.0, IIRC, from tests (now deleted) I believe that
string.Equals(l hs,rhs, ComparerOptions .OrdinalIgnoreC ase) is the
fastest.

You can also use StringComparer. OrdinalIgnoreCa se.Equals(...) but I
beleive that this is a little slower.

Your best bet is to try every option in a tight loop to test;
you could try:

lhs.ToUpper() == rhs.ToUpper()

lhs.Equals(rhs, StringCompariso n.OrdinalIgnore Case); // or
InvariantCultur eIgnoreCase

string.Equals(l hs, rhs, StringCompariso n.OrdinalIgnore Case) // or
InvariantCultur eIgnoreCase

StringComparer. OrdinalIgnoreCa se.Equals(lhs, rhs); // or invariant case
insensitive

etc

Marc

[Marc Gravell]

ComparerOptions .OrdinalIgnoreC ase
I meant StringCompariso n.OrdinalIgnore Case, but intellisense would have
told you that...

Marc

[bob.abrahamian]

Merk wrote:

What are some alternatives to using .ToUpper() to perform case insensitive
string comparisons?

The reason I'm asking is that I'm comparing strings in a long loop, looking
for equality; and I want for this loop to run as fast as possible. So I'm
looking for a method that would be faster than .ToUpper().

Thanks!

System.String.C ompare(string a, string b, bool ignoreCase);

or

System.Collecti on.CaseInsensit iveComparer.Def aultInvariant.C ompare(string
a, string b);

anyone have any ideas about my mulitple browser problem?

[Bruce Wood]

Merk wrote:

What are some alternatives to using .ToUpper() to perform case insensitive
string comparisons?

The reason I'm asking is that I'm comparing strings in a long loop, looking
for equality; and I want for this loop to run as fast as possible. So I'm
looking for a method that would be faster than .ToUpper().

Are you comparing the same string over and over again? For example, are
you sorting an array? If you are, then store the strings in both their
uppercase and mixed case versions, and compare only the uppercase
versions. You'll incur the cost of uppercasing them only once, and then
get the payback on the comparisons. Trade memory for more speed.

If you test each string only once then, of course, this won't help.

Usually you gain efficiencies when you step back and look at the
overall problem, and how you can avoid doing the same work over and
over again, rather than trying to figure out how to do that work faster.

[Jon Skeet [C# MVP]]

Marc Gravell <ma**********@g mail.comwrote:

In 2.0, IIRC, from tests (now deleted) I believe that
string.Equals(l hs,rhs, ComparerOptions .OrdinalIgnoreC ase) is the
fastest.

You can also use StringComparer. OrdinalIgnoreCa se.Equals(...) but I
beleive that this is a little slower.

Your best bet is to try every option in a tight loop to test;
you could try:

lhs.ToUpper() == rhs.ToUpper()

Note that this test is not a culture-safe one. For instance, in Turkey,
I believe (if I remember the bug I had to fix in a system a while ago
:) that "mail".ToUpper( ) != "MAIL".

Using a StringComparer is a much better way, IMO.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Mark Wilden]

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************** *@msnews.micros oft.com...

>
Note that this test is not a culture-safe one. For instance, in Turkey,
I believe (if I remember the bug I had to fix in a system a while ago
:) that "mail".ToUpper( ) != "MAIL".

Just out of curiosity, did "mail".ToUpper( ) == "MAIL".ToUpper( )?

///ark

[Jon Skeet [C# MVP]]

Mark Wilden <mw*****@commun itymtm.comwrote :

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************** *@msnews.micros oft.com...

Note that this test is not a culture-safe one. For instance, in Turkey,
I believe (if I remember the bug I had to fix in a system a while ago
:) that "mail".ToUpper( ) != "MAIL".

Just out of curiosity, did "mail".ToUpper( ) == "MAIL".ToUpper( )?

Nope :)

using System;
using System.Globaliz ation;
using System.Threadin g;

class Test
{
static void Main()
{
CultureInfo info = CultureInfo.Cre ateSpecificCult ure("tr-TR");

Thread.CurrentT hread.CurrentCu lture = info;

Console.WriteLi ne ("mail".ToUpper ()=="MAIL");
Console.WriteLi ne ("mail".ToUpper ()=="MAIL".ToUp per());
}
}

ToLower() doesn't work either.

Isn't i18n fun? :)

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Marc Gravell]

Good to know; cheers for the input Jon.

For ref, I only mentioned the ToUpper() as a performance comparison
(since the OP explicitely mentioned it) to the StringComparer and
string.Equals() [with stated comparison], but thanks for the heads-up
and "proof positive" example.

Marc