in reply to Re: The golf course looks great, my swing feels good, I like my chances (Part V)
in thread The golf course looks great, my swing feels good, I like my chances (Part V)
1. Can you further explain your "string of ord values", where you have "XXXXXXXXXXXX"? I'm hoping to run your code and I'm not clear on that point.To take a specific example of my 101 stroker:
where XXXXXXXXXXXX above is a string with ord values: 120, 47, 253, 22, 194, 9, 183, 44, 196, 55, 125, 246. A simple way to run this is:print$"x(318%$_/9),(($_-$`)%12?o:x)&($_%12^$'/5?o:'}'),$/x($_/85)for u +npack<>!~/:/.C12,'XXXXXXXXXXXX'
$X = pack 'C*', 120, 47, 253, 22, 194, 9, 183, 44, 196, 55, 125, 246; print$"x(318%$_/9),(($_-$`)%12?o:x)&($_%12^$'/5?o:'}'),$/x($_/85)for u +npack<>!~/:/.C12,$X
2. I like your attempt with "H|", and your final resignation(?) with "}".Using "}" was unfortunate because (unlike H, say) it needs to be quoted. My search program showed that a minimally short solution consisting only of unquoted characters was not available.
3. Does a line break really not count as a stroke, as in your print statement?Line breaks count as one character at the codegolf web site, so long as you submit your entry in a file in Unix format (LF) -- if you are silly enough to submit it in DOS format (CRLF) they count as two strokes. :) That is, your codegolf score is simply the size of the file submitted.
4. I humbly suggest warn instead of print to save another stroke.The codegolf test program checks what is written to stdout and ignores anything written to stderr. Since warn writes to stderr it would not pass the test program and would be rejected.