#!/usr/bin/perl sub x{(caller())[ob-//]} sub ob{x}_(&fu.a)._(&te.&sc)._(&te.&ob)._(&te.&fu)._(&ob-//.$%); sub fu{x}_(&at.//)._(&at.e)._(&at.f)._(&te.&fu)._(&at.&d_)._(&at.&sc); sub sc{x}_(&te.&ob-//)._(&ob-//.$%)._(&sc.$%)._(&at.&sc); sub at{x}_(&te.&ob-//)._(&at.c)._(&ob-//.$%)._(&at.&d_)._(&at.//); sub te{x}_(&at.&ob)._(&at.b)._(&at.&sc)._(&te.&ob-//)._(&ob-//.c); sub d_{x}sub _{vec($_,$%,d_)=eval"$%x$_[$%]";print chr vec($_,$%,d_)}

Replies are listed 'Best First'.
Re: Call .. Call ... Call ..
by de_cristian_izer (Initiate) on May 27, 2005 at 10:03 UTC
    Considering the fact that cristian is being a mad man about obfu , always posting the most amazingly unreadable code, WE , a collective of rebel obfu solvers , decided to stand up for CLEAN CODE and FREE PIZZA and BEER and CLEAN CODE !!! ( and also for fun ! )

    So here goes for this one :

    Phew ! Wicked !

      Excellent , i not to explain best. very good. I will try to create other code more more obfu. je je je. Greeting to yours monks.
      Note that in this last line &ob is used, while in the definition of the sub x it is plain ob that is used in ob-// returning -1 and not 2 for some unclear reason ...
      In the definition of sub x the subroutine ob is not yet declared so the bareword ob is interpreted as an unquoted string. Then 'ob'-1 interprets 'ob' as 0 since it's not a number.