Fortsätt till huvudinnehåll

String comparison in C#

In C#, a string is a sequential read-only collection of Char objects. A Char object is an instance of a Char struct, which represents a character as a UTF-16 code unit.

Most programs, and programmers, do not care much about the internal representation of a string and a Char. As long as you know that strings are immutable and there is a big efficiency penalty involved in building up strings in loops without involving a mutable object, such as a StringBuilder, you are mostly fine.

However, there are some things that are good to know when working with strings. One of these things is comparison using methods such as String.CompareTo and String.Compare. By default the Compare and CompareTo methods are Culture sensitive. This means, that depending on the language and culture setting of the machine running the application, comparison and sorting of strings might be different than on your development machine. This might be exactly what you want, or it might come as a complete surprise.

The best thing to do here is to override the default behavior and be specific in your code on how you want your application to behave.

So, do not use the CompareTo method at all, instead use Compare, but not the default that only takes two strings, but the version where you explicitly define which type of comparison you want to use. This is, Compare(String, String, StringComparison).

For more info:
https://docs.microsoft.com/en-us/dotnet/api/system.string

Kommentarer

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i