News for hackers. Stuff that matters.
Re:Radiation-hardened quine by Cthulhu_ on Friday February 21, 2014 @10:31AM (#7277377)
I can't read this code at all, but, does this code basically contain the same code twice, so if something from the first half is removed the second half saves it?
Re:Radiation-hardened quine by hrjet on Friday February 21, 2014 @10:36AM (#7277401)
Yes, Line 15: /#{eval eval if eval==instance_eval}}/.i rescue##/

They are checking the two instances and rescuing the corrupted one. But how exactly it works is beyond me.

Re:Radiation-hardened quine by jonmrodriguez on Friday February 21, 2014 @07:47PM (#7280459)
Also, in line 17, I think it's running whichever of the two codes is longer (since the longer one is the one that didn't have a byte deleted)

    eval eval"[eval||=9,instance_eval||=9].max_by{|s|s.size}#"##"
See the max_by ... size part
Re:Radiation-hardened quine by Schwolop on Monday February 24, 2014 @09:27PM (#7294902)
Yes, and I was thoroughly disappointed by this result. So - new challenge: a radiation hardened quine in less than two times the characters of the equivalent non-radiation hardened version.
Re:Radiation-hardened quine by joi_degn on Friday February 21, 2014 @10:36AM (#7277398)
I didnt look at the code and am not knowledgeable in this kind of coding but unless I am wrong, if the program simply would contain the same code twice each of these 2 codes would have to contain the same code twice ad infinitum.
Re:Radiation-hardened quine by notimetorelax on Saturday February 22, 2014 @07:12AM (#7281838)
If we follow your reasoning than quine itself is not possible.