On Fri, Jul 01, 2005 at 02:30:53PM -0700, Ned Freed wrote:
The only feedback I got when I changed it from caseless to caseful was that
a regression test failed that used FILEINTO. That was easily fixed.
I was frankly surprised that I coded it using a case-sensitive comparison and
that nobody has complained about it. Had I thought about it I probably would
have used a case-insensitive comparison.
Sometimes you get lucky, that's all.
I do case-insensitive comparisons, because in general I prefer to ignore
differences in case unless there's a reason not to; however, our script
generation tools always generate lowercase. So changing to case-sensitive
wouldn't hurt here, and I wouldn't really object to it.
However, there has been other support for case-insensitivity in other
discussions; e.g. for variable names and in the Sieve language
definition itself. As I say, I don't particularly object to making
"require" case-sensitive, but consistency is always good (as is the "be
liberal in what you accept" tenet).