first_page the funky knowledge base
personal notes from way, _way_ back and maybe today

C#: “Direct casting vs ‘as’ operator?”; stackoverflow.com

void Handler(object o, EventArgs e) { // I swear o is a string string s = (string)o; // 1 //-OR- string s = o as string; // 2 // -OR- string s = o.ToString(); // 3 }

/*

  1. Throws InvalidCastException if o is not a string. Otherwise, assigns o to s, even if o is null.

  2. Assigns null to s if o is not a string or if o is null. For this reason, you cannot use it with value types (the operator could never return null in that case). Otherwise, assigns o to s

  3. Causes a NullReferenceException of o is null. Assigns whatever o.ToString() returns to s, no matter what type o is.

Use 1 for most conversions - it's simple and straightforward. I tend to almost never use 2 since if something is not the right type, I usually expect an exception to occur. I have only seen a need for this return-null type of functionality with badly designed libraries which use error codes (e.g. return null = error, instead of using exceptions).

3 is not a cast and is just a method invocation. Use it for when you need the string representation of a non-string object.

*/

mod date: 2009-09-08T03:16:46.000Z