[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Scheme-reports] Boolean hemlines

On Thu, Apr 12, 2012 at 10:22:59AM +0100, Alaric Snell-Pym wrote:
> The reason for them, as I saw it, was that #t and #f are easy to confuse
> in many fonts, which is an accident waiting to happen!

That's just silly.  The user can get a proper font, this is not
something the language needs to work around.  Next you'll say we need to
force uppercase identifiers because the number 1 and the letter l can be
confused too easily otherwise!

Also, what the hell kind of font confuses these two letters?  t looks
like an upside-down f in most fonts, which is a very clear difference.
If you're afraid they get confused, allow them to be case-insensitive:
#T is very different from #F, and that's already supported by most

"The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music."
							-- Donald Knuth

Scheme-reports mailing list