I remember once upon a time (in the mid 1980's) creating a bit of an embarrassment (resulting in the rapid production of a PTF) caused by my naivety. I had written some code which produced console messages (i.e., WTO's) in mixed case. Unbeknownst to me at the time, the EBCDIC character codes for the lower case letters (0x81:0x89, 0x91:0x99, 0xA2:0xA9) produced katakana graphics on an IBM 3278KN SBCS terminal. So, when my code was executed on a customer's system in Japan, the results were less than delightful.
This was not a Severity-1 situation (the customer was very willing to swap out the 3278KN and put in its place a "standard" 3278 Model 5, and, fortunately, everyone treated the issue lightheartedly). Of course, the situation could have been much more severe as perceived by the customer and my employer. And, YES, the code had undergone a successful code review. This is NOT intended to be an argument against using mixed case in coding. Rather, one must be aware of potential traps and pitfalls (borrowing a piece of the title of the book "C Traps and Pitfalls") by Andreww Koenig) and use mixed case appropriately. Bob
