Henri Yandell <[EMAIL PROTECTED]> writes:
> I've submitted Frederik's patch with the new method. Only odd boundary
> case I can see is that:
>
> containsOnly("", anything but null) returns true.
This seems okay to me. A string object could contain the specified
characters (but doesn't).
> containsOnly(null, anything) returns false.
I could follow this on the grounds that a null string couldn't
possibly contain any characters, so should fail. Still, I find the
semantics confusing, since the same argument could be applied to the
previous case as well.
--
Daniel Rall <[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
