Talk:Calendar - for "REAL" programmers: Difference between revisions
Talk:Calendar - for "REAL" programmers (view source)
Revision as of 18:17, 31 May 2011
, 12 years agono edit summary
No edit summary |
mNo edit summary |
||
Line 3:
:Looks like maybe it's just for fun maybe. I suggest removing the task tag and moving it to a subpage of the user who made it's user page. --[[User:Mwn3d|Mwn3d]] 03:45, 31 May 2011 (UTC)
I kind of disagree. Programming on a 6-bit (aka UPPERCASE only) platform is a legitimate pursuit. The K&R C programming language specifically permitted it, so to also PL/I, FORTRAN, COBOL... etc. There were and are still many legitimate CPU architectures that are intrinsically 6-bit, hence UPPERCASE.
: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)▼
===Examples===
Line 51 ⟶ 49:
:Not decision, discussion. And you`ve made a great case! --[[User:Paddy3118|Paddy3118]] 05:43, 31 May 2011 (UTC)
Secretly I'm looking forward to the [[wp:Qubit#Bit_versus_qubit|Qubit]] and [[wp:Qutrit|Qutrit]] computers... When 32-bit and 64-bit computers will become old hat. :-) [[User:NevilleDNZ|NevilleDNZ]] 05:55, 31 May 2011 (UTC)
▲: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)
=== Create another algorithm? ===
:The task description says "Create another algorithm", yet the Algol solutions are identical (except for the case).--[[User:Abu|Abu]] 15:06, 31 May 2011 (UTC)
| |||