On Sat, Feb 21, 2009 at 09:03:30PM -0800, Guillermo J. Rozas wrote: > - The great inconvenience and lack of respect for existing users > which the change causes/caused. Even though I much prefer case > insensitivity, I would not argue for C to change. It would be > too disruptive. > Why are Scheme users afforded any less consideration?
This is the bit that I don't understand. I thought that the argument for case-insensitivity was to prevent (presumably 'other') programmers from using symbols that differ only incase, because that would be confusing. So it follows that good, existing code does *not* use symbols that differ only in case, because that would be confusing. So from the point of view of existing code, case-sensitive or case-insensitive ought not to matter. Are there any existing scheme style guides that advocate specific change of symbol case for any particular purpose? All of the scheme that I've read to date has, I think, had universally lower-case identifiers. I don't buy the arguments to discussion in English sentences: that is clearly out of the context of the parser, and you can do whatever you like to be understood. English is insufficiently precise to not require a few helper words now and then. Neither do I think that change mark-up is much of an argument these days, either. Change management systems are close to ubiquitous, and almost always provide font and colour based ways of showing changes in context. Cheers, -- Andrew _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
