CODEWITHSUNDEEP
c#.netstringnullconcatenation
knittl
knittl

Reputation: 265231

Converting objects to string by prepending empty string in C#

Recently, I've seen the following statement quite a lot:

object o;
// assign o
return "" + o;

(Basically the same as return String.Concat(o);)

Why would anyone want to do that? Why not just call .ToString() on the object (after checking object is not null, of course)?

Sure, the code is shorter and does away with the null check, but I find it confusing to read. Are there any other benefits to this? I've also seen the same statement with regard to integer values.

I expect to see above code in loosely typed languages such as JavaScript or PHP – but not in C#.

Upvotes: 5

Views: 161

Answers (2)

Habib
Habib

Reputation: 223267

IMO, Just a bad approach to avoid Null Reference Exception.

Probably the original developer's intent was to use as less code as possible in returning string without checking null or Type

Upvotes: 4

Scott
Scott

Reputation: 1876

No, you would not want to do that in C#. You are better off with calling the ToString method on the object. There are some languages where that is the preferred syntax, such as with JavaScript. So you might be seeing some cross-language leak.

Upvotes: 3

Related Questions