Tom Schneider wrote:
So, what's best now, "varying capitalisation", "varying capitals", "mismatched caps"?
"varying capitalisation" would be my choice "varying letter-cases" may be clearer, and it avoids the ambiguity on "cases" that started the discussion
Keep it short. Maybe "varying id letter case: <oldid> <thisid>"?
Perhaps "mismatched <oldid> <thisid>"?
It has to be CLEAR which means things like 'caps' won't do because it is not obvious that this is an abbreviation.
How about straightforward English:
The capitalization of the definition <original> does not match <current>.
or more tightly:
Capitalization of definition <original> does not match <current>.
"Definition" is generally not correct, since it can also be an applied occurrence of an identifier.
This way there would be no question as to what the message means. I think that a few extra bytes for clarity is worthwhile.
I'd prefer to have it in two lines, so the file names/line numbers can refer to both points of usage. But breaking a sentence in such a way, with a (generally) different line number in between, might be confusing. So I'd then suggest something like:
foo.pas:42: capitalization of identifier <current> does not match previous one foo.pas:17: previous capitalization <original>
or
foo.pas:42: msimatched capitalization of identifier <current> foo.pas:17: previous capitalization <original>
Adriaan van Os wrote:
The compiler will have to look at the date first and, if that happens to be April 1, issue the message "I don't like your cap".
LOL. :-)
Frank