8 deleted 267 characters in body

Windows PowerShell, 91 959798

($OFS='')+('Qnuux)x{um'|% t*y|%{"[convert]::"+([convert]|gm -s t*r).name+"($($_-9))"|iex})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

• Shortened a bit with a newer PowerShell version. No useful different way of creating the result emerged, though, sadly.

Windows PowerShell, 91 959798

($OFS='')+('Qnuux)x{um'|% t*y|%{"[convert]::"+([convert]|gm -s t*r).name+"($($_-9))"|iex})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

• Shortened a bit with a newer PowerShell version. No useful different way of creating the result emerged, though, sadly.

Windows PowerShell, 91 959798

($OFS='')+('Qnuux)x{um'|% t*y|%{"[convert]::"+([convert]|gm -s t*r).name+"($($_-9))"|iex})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

• Shortened a bit with a newer PowerShell version. No useful different way of creating the result emerged, though, sadly.

7 added 129 characters in body

Windows PowerShell, 9591959798

($OFS='')+('x'Qnuux)x{umQnuu'[-4..6]|%um'|% t*y|%{iex("[convert]::"+([convert]|gm -s *pet*r).name+"($($_-9),4)")"|iex})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

• Shortened a bit with a newer PowerShell version. No useful different way of creating the result emerged, though, sadly.

Windows PowerShell, 959798

($OFS='')+('x)x{umQnuu'[-4..6]|%{iex("[convert]::"+([convert]|gm -s *pe).name+"($($_-9),4)")})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

Windows PowerShell, 91959798

($OFS='')+('Qnuux)x{um'|% t*y|%{"[convert]::"+([convert]|gm -s t*r).name+"($($_-9))"|iex})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

• Shortened a bit with a newer PowerShell version. No useful different way of creating the result emerged, though, sadly.

Mod Removes Wiki by gnibbler
6 added 3 characters in body

Windows PowerShell, 9795 9798

($OFS='' ''+)+('x)x{umQnuu'[-4..6]|%{iex ("[convert]::"+([convert]|gm -s *pe).name+"($($_-9),4)")})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

Windows PowerShell, 9798

$OFS='' ''+('x)x{umQnuu'[-4..6]|%{iex ("[convert]::"+([convert]|gm -s *pe).name+"($($_-9),4)")})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char.

Windows PowerShell, 95 9798

($OFS='')+('x)x{umQnuu'[-4..6]|%{iex("[convert]::"+([convert]|gm -s *pe).name+"($($_-9),4)")})  Violates only Rule II. It's very evil that char violates two rules on its own already. And yikes, this one was hard to get working. • The first line sets $OFS to '' so when casting an array to a string no spaces appear between items.
• The string actually stores 'o WorldHell' because I either need [char[]] or .ToCharArray() or indexes to get the characters out of it. Was the first variant where the indexes wouldn't contain 0, 1, 2 or 7 (yes, at that time I was aiming to satify all rules).
• Casting to char actually was the hardest part of all and I spend around a day searching for a way. I got all the rest working nicely but once I do calculations on them I have ints, not chars. Putting those back in a string was kinda hard.
• The only way to cast to char I have found that doesn't use the word char is [Convert]::ChangeType which isn't too much nicer, but at least I can get there without having to use h.
• I found a way of invoking Invoke-Expression without needing the e as well:

&(gcm i?x)


but that still lacked the arguments. And I've thrown away my goal of satifying all three rules by then already. Also it didn't particularly help me in casting to char`.

5 added 1155 characters in body
Post Undeleted by Joey
4 added 12 characters in body; added 26 characters in body
3 added 3 characters in body
Post Deleted by Joey
Post Undeleted by Joey
2 added 92 characters in body
Post Deleted by Joey
1