Anonymous user
Talk:Calendar - for "REAL" programmers: Difference between revisions
Talk:Calendar - for "REAL" programmers (view source)
Revision as of 04:42, 1 June 2011
, 12 years ago→Discussion Cont.
m (→Create another algorithm?: rewording task: Provide an algorithm ... presented entirely without lowercase.) |
|||
Line 51:
:But 6 bit could just as easily be all lower case as all uppercase. And there are other characters that would also be eliminated if this were really being targeted at a 6 bits-per-character platform. Meanwhile, some languages become unusable with this "all uppercase" constraint. Mind you, it's a cute constraint. But it's also silly. --[[User:Rdm|Rdm]] 18:15, 31 May 2011 (UTC)
Actually - kind of - I agree with you... 6-bit is the criteria. Although I have never heard of a strictly lower case hardware platform.
BTW: The first time I encountered such a computer, it was a [[wp:Prime Computer|Pr1me]] I remember trying being rather bamboozled about how to get the damned thing out of uppercase, including looking for a toggle under the keyboard. It took a little while to dawn on me that it could ''only'' '''do''' upper case. The [[wp:ZX80|ZX80]] code was also UPPERCASE, the ZX was so nice to program that the UPPERCASE restriction didn't seem to matter.
There are a couple of other legacy options in unix that throw back to the UPPERCASE heritage.
* Unix provides the /bin/stty '''and''' the /bin/STTY command for chance where the keyboard only generates uppercase.
* On Unix, if you do a console login and accidentally type your name in UPPERCASE the getty assumed you were on a 6 bit terminal. Linux still retains the "stty xcase" option for prefixing "\" on uppercase characters. I do not recall any "stty sane" option. ;-)
I wonder if K&R C ever handled UPPERCASE programs by mapping only characters prefixed with "\" to uppercase? Hmm... I have my suspicions.
[[User:NevilleDNZ|NevilleDNZ]] 04:42, 1 June 2011 (UTC)
=== Create another algorithm? ===
| |||