Anonymous user
Talk:Calendar: Difference between revisions
→Calendar versus CALENDAR: new section
(→Calendar versus CALENDAR: new section) |
|||
Line 18:
While generating a particular year is fine, a Real Programmer would not have written their calendar generator to handle arbitrary widths of display. Instead, it would have either produced for 132-char wide line printers or 80-char wide terminals. In this day and age, nobody's got line printers any more so formatting for an 80-char terminal is what we must put up with. Given that, I propose that the task should state that the calendar should be tested by generating a calendar for the current year suitable for an 80-column device. Adaptation to other widths, other years and other languages are all to be extra-credit items. –[[User:Dkf|Donal Fellows]] 08:36, 4 June 2011 (UTC)
: Note also that the 132-column requirement would fit entirely within the scope of the dual [[CALENDAR]] task. :-) –[[User:Dkf|Donal Fellows]] 08:47, 4 June 2011 (UTC)
== Calendar versus CALENDAR ==
This task had the sentence: "For further Kudos see task [[Calendar - for "real" programmers|CALENDAR]], for printing on a 132 character width [[wp:IBM 1403|IBM 1403]] printer. Where all code and output is to be in UPPERCASE."
This sentence was wrong, because CALENDAR only requires uppercase code, not uppercase output. Also, CALENDAR is identical to Calendar (except uppercase), so if Calendar requires 80x43 output, then CALENDAR also requires 80x43 output. Before 12 June 2011, Calendar specified "a width of 132 characters". At 12 June 2011, Calendar began to require 80x43 output. This new 80x43 requirement broke the relationship between Calendar and CALENDAR, squeezed Snoopy, and ignored the line-printer Snoopy calender that inspired the task. So, I am now changing Calendar to accept either 132-wide output or 80x43 output. --[[User:Kernigh|Kernigh]] 02:00, 20 August 2011 (UTC)
| |||