News for hackers. Stuff that matters.
Re:Brainfuck in one line of Python by benatkin on Sunday December 04, 2011 @04:56PM (#3311986)
That isn't the normal way of measuring the length of code in code golfing contests. It's number of normal-sized lines, for some measurement of normal that is less than 1400 characters. Pretty neat, though; just a misleading title.
Re:Brainfuck in one line of Python by rcthompson on Sunday December 04, 2011 @05:17PM (#3312045)
Maybe "in one Python statement" would be more appropriate.
Re:Brainfuck in one line of Python by mahmud on Sunday December 04, 2011 @05:32PM (#3312086)
Every Lisp program can be rewritten to be just "one expression"

  `(progn ,@program)
What have we achieved here?
Re:Brainfuck in one line of Python by tjoff on Sunday December 04, 2011 @05:38PM (#3312108)
I think the first paragraph explained it quite well.

Whether or not the feat itself is impressive or not I don't really know but the reason for the quest was motivated.

Re:Brainfuck in one line of Python by mahmud on Sunday December 04, 2011 @06:04PM (#3312195)
My point was that "one-line" is a faulty criterion for measuring compactness if we allow for arbitrarily long lines: or "long cat is long" considered harmful.
Re:Brainfuck in one line of Python by nknight on Sunday December 04, 2011 @06:20PM (#3312232)
I'm guessing you don't deal with Python much. Python actively discourages this sort of thing, it's actually hard to create obfuscated code of the kind you see in most other languages.

That this was even possible surprised me somewhat, that he actually figured it out I find quite impressive.

Re:Brainfuck in one line of Python by mahmud on Sunday December 04, 2011 @06:41PM (#3312294)
Fair point, and the magnitude of this feat was not lost on me. I was just speaking in general, we need a better metric for one-linerness than s/\n//g.