You were a bit late posting... someone got there first.
And... what we now have is several scripts, surely? Especially without the use of a class...
I think we need to outline our own rules for this. A time limit would help of course. And also, the "Red Line Rule" which hasn't been used yet. This is used as so:
If the Red Line is set at 5, and the original script is 15, then no volleys can be above 20 or below 10.
Another rule, is the characters-per-line. This is a constant set at 80 chars such that no lines in any games can be longer than this except for lines in the original code.
PHP Tennis Match 2
Moderator: General Moderators
I know somebody posted while I was doing mine, but mine seems to me a legitimate change of his code, 5 lines exactly (comments and empty lines don't count, right?)
Now, as for the rules, I agree they need to be way stricter. I put up my code in an attempt to humorously end the thread. The rules listed on the other site gave a 25% redline, and I think that's a good rule. As for the 80 characters, like I said in a previous post, the original posting violated that, so I considered it null here. I think that allowing it in the original but not in further posts is a good rule.
Furthermore, I think that there should be a spirit of "optimization". That is, a spirit that each change should legitimately improve, in concept or implementation, the original code. This means that adding frivolous functions (as determined by the peer refereeing method) should be a fault. This would make the code i posted a fault
, but also force you to contemplate a volley harder before you hit it.
Now, as for the rules, I agree they need to be way stricter. I put up my code in an attempt to humorously end the thread. The rules listed on the other site gave a 25% redline, and I think that's a good rule. As for the 80 characters, like I said in a previous post, the original posting violated that, so I considered it null here. I think that allowing it in the original but not in further posts is a good rule.
Furthermore, I think that there should be a spirit of "optimization". That is, a spirit that each change should legitimately improve, in concept or implementation, the original code. This means that adding frivolous functions (as determined by the peer refereeing method) should be a fault. This would make the code i posted a fault