Some may think that your code would benefit greately from an optimizing compiler. Leaving the minor, worldly details aside, one may envision your code similar in machinations and side effects to /bin/true. Yeah, True. Is this union with the Universe? Or that would be /bin/false? Or is it impossible to achieve such a feat, therefore we have to explore every nook and cranny of the absurd, the strange marriage between the conscious man and the hostile and meaningless world, never trying to elude what is given, our mortal condition... The absurd man says yes and his efforts will henceforth be unceasing. If there is a personal fate, there is no higher destiny, or at least there is but one which he concludes is inevitable and despicable. For the rest, he knows himself to be the master of his days.

Below is Perl's painstaking interpretation of the whole affair. One must imagine Perl happy. :)

$ perl -MO=Terse /tmp/censor.pl LISTOP (0x8185fc8) leave [1] OP (0x8123230) enter COP (0x8184320) nextstate BINOP (0x8185fa0) sassign SVOP (0x8185f80) const PV (0x812a9b4) "" UNOP (0x8185f60) null [15] SVOP (0x8127148) gvsv GV (0x812aa14) *Freedom COP (0x8186108) nextstate BINOP (0x81860e0) sassign SVOP (0x81860c0) const PV (0x812aa38) "" UNOP (0x81860a0) null [15] SVOP (0x8185ff0) gvsv GV (0x812a9a8) *Censorship COP (0x81231f0) nextstate UNOP (0x81231d0) null LOGOP (0x81231a8) cond_expr BINOP (0x81861a8) eq UNOP (0x8186168) null [15] SVOP (0x8186148) gvsv GV (0x812aa14) *Freedom SVOP (0x8186188) const IV (0x811f568) 1 LISTOP (0x8186298) leave OP (0x8123188) enter COP (0x8186258) nextstate BINOP (0x8186230) sassign SVOP (0x8186210) const IV (0x812a9e4) 0 UNOP (0x81861f0) null [15] SVOP (0x81861d0) gvsv GV (0x812a9a8) *Censors +hip UNOP (0x8123168) null LOGOP (0x8123140) and BINOP (0x812db50) eq UNOP (0x8184060) null [15] SVOP (0x81862c0) gvsv GV (0x812a9fc) *Cen +sorhip SVOP (0x81862f8) const IV (0x812aa08) 1 LISTOP (0x81230f8) leave OP (0x8123120) enter COP (0x81230b8) nextstate BINOP (0x8123090) sassign SVOP (0x8123070) const IV (0x812a9d8) 0 UNOP (0x8123050) null [15] SVOP (0x812db78) gvsv GV (0x812aa14) +*Freedom /tmp/censor.pl syntax OK


In reply to One must imagine Perl happy... by calin
in thread Poem about the FCC by shirkdog_perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.