Padding a string with integers on its right keeping string length fixed

[realJSOP]

string x = string.Format("T{0}", number.ToString("00000"));

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

[Richard Deeming]

Even simpler:

string x = string.Format("T{0:D5}", number);

Or:

string x = $"T{number:D5}";

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[realJSOP]

isn't the "$" notation for PHP or some other stupid language? Or is it a new pointless operator in C#?

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

[Richard Deeming]

It's been a C# feature since v6: $ - string interpolation - C# reference | Microsoft Docs[^] What's New in C# 6 - C# Guide | Microsoft Docs[^]

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[realJSOP]

Let's obfuscate C# even more than it already is...

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

[Richard Deeming]

String interpolation was a pretty good addition, IMO. Especially when you compare it to the abomination that became of default interface methods[^]. X|

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[OriginalGriff]

I agree - I use string interpolation precisely because it de-obfuscates code:

Console.WriteLine("({2},{1}):({0},{3})={4}", destX, y, x, destY, dist);

Isn't as obvious as

Console.WriteLine($"({x},{y}):({destX},{destY})={dist}");

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

[Lost User]

OriginalGriff wrote:

precisely because it de-obfuscates code:

Except when you use random ordering of your variables. ;P

[OriginalGriff]

:laugh: I've seen code like that before: when the variable list order is wrong, and it was easier to renumber than juggle the names ... Not that I'd write code like that, oh no.

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

[realJSOP]

For me, the numbers have to be in order, so I juggle the names. :)

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

[Daniel Pfeffer]

A legitimate use case for unordered variables might be when writing output in different languages. In one language you might want to write "Page 1 of 10", but in another it might be "10 pages, No. 1" or some such. You would read the template from the resource file, filling in the values as necessary.

Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.