> On this course, I don't think anyone was trying to have literal > carriage returns in their programs, so \r\r\n isn't that relevant --- > but it's still an issue if you do newline canonicalization on Unix: > \r\r\n from browser -> \r\n when stored -> \n when parsed -> \n when > printed, but \r\r\n from browser -> \r\r\n when stored -> \r\n when > parsed -> \r\r\n when printed on Windows (textmode assumed). Right?
Well, my unorthodox/159.35 was an attempt to show that \r\r\n sequence can be abused, it chopped one stroke from my otherwise nearly identical 160.35. ;) -- Marko P. Nippula <[EMAIL PROTECTED]>, http://www.hut.fi/~mnippula/ while($|=$^T*=.9){sub _{@_<99&&($:=$_[0]**2+($;=$_[1]**2))<4?_($:-$;-$;+ $_[-2],2*$_[0]*$_[1]+$_[-1],@_):chr@_/2}for$.(-11..12){$\.=_$_/(9x9)*$^T -1.04,$./(6x9)*$^T-.35for-40..39};$\=~y//~ @-]a-m*-. /c;$\=!print"\e[H"}
