In article <[EMAIL PROTECTED]>, Rick Klement <[EMAIL PROTECTED]> writes: > Stephen Turner wrote: >> >> On Sat, 8 Jun 2002, Ton Hospel wrote: >> > >> > I suppose it's the \0 => binary zero ? >> > >> > If so, neither Eugene nor me missed that (see our comments), but solutions >> > with binary zero were not allowed this round. >> > >> >> Right. I was very surprised if either of you missed it, but when I found >> that you both had, I assumed it wasn't allowed for some reason. >> >> But why didn't the referees allow it? There's nothing in the rules about it, >> is there? And surely it wasn't just the problems with submitting it, because >> other non-printable characters are as bad. Did they give a reason? > > I am also interested in the reason why the refs disallowed it. > > I would have a tendency to disallow a byte that matched [^ -~\n\t] > if I were in charge (oh, wait, I will be :) >
That means you disallow things like $^X, $^T, $^F written the short way too. Blech. I'd prefer every valid perl program to be acceptable. It has the advantage of stopping the pack attacks in their track though.
