in reply to exactly 390 bytes

Well, here's the start of the ripping apart of this cool piece of text. I don't currently have the time to reverse engineer the whole thing, I may come back to it later if nobody else does so first:

s//ucfirst/e and s/c/ chr oct hex acdac/eg xor s/o/ study dive/eg and s/\n//g and s/r /oo do reverse / xor s/o do/chr reverse ord srand hyper/e and s/s/lcfirst/eee if s// ILwHChJwulrZrjqBkNAsAoXVcFMopbloPRZAcwJMcAcR ogctmccXVNgNLoorWVPvJoPocohNPoaccoSRcQWMcqwWAngtc ugnAKocovocoKxSLdiocEocTJTMYobcTJEcTcZocccDBcbEjc oWRABvGZoYoVcfAnaoooAQATJnbLcoCoHzuPyJQIaIWNLqSxs Lwr/x

Replies are listed 'Best First'.
Re^3: exactly 390 bytes
by Anonymous Monk on Mar 23, 2004 at 08:44 UTC

    My /eee foo is weak. I have absolutely no clue what a /eee switch does on a regex. Here's what I've worked the whole thing down to and I don't understand how it works its magic. I know that /eee is on the perl purity test, but I'm still clueless :|

    $_ = " ILwHChJwulrZrjqBkNAsA1XV8FM1pbl1PRZA8wJM 8A8R1g8tm88XVNgNL11rWVPvJ1P181hNP1a881SR8QWM8qw WAngt8ugnAK181v181KxSLdi18E18TJTMY1b8TJE8T8Z188 8DB8bEj81WRABvGZ1Y1V8fAna111AQATJnbL81C1HzuPyJQ IaIWNLqSxsLwo^ reverse ILwHChJwulrZrjqBkNAsA1XV 8FM1pbl1PRZA8wJM8A8R1g8tm88XVNgNL11rWVPvJ1P181h NP1a881SR8QWM8qwWAngt8ugnAK181v181KxSLdi18E18TJ TMY1b8TJE8T8Z1888DB8bEj81WRABvGZ1Y1V8fAna111AQA TJnbL81C1HzuPyJQIaIWNLqSxsLwr"; s/\n//g; s/s/lcfirst/eee;