Talk:Calendar: Difference between revisions

m
→‎Improving the task description: added closing bracket. -- ~~~~
m (→‎Improving the task description: added my 2¢ worth. -- ~~~~)
m (→‎Improving the task description: added closing bracket. -- ~~~~)
Line 19:
: 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)
 
:: I disagree about a "Real Programmer" wouldn't have written code to handle arbitrary widths of display terminals. I consider myself a real programmer, and had exposure to different terminals and/or printers. Even if I didn't have that exposure, I still would've written the code to handle various sizes of display and/or different printer widths. Almost all my programs have that type of logic from the get-go, so it makes it much easier to enhance the program when thinking of solving the task problematically. Also, whether line printers are used (printing a line at a time) or those that print a "page" at a time (my laser printer does a "line" at a time even though it may only print part of a line), the printed output still has "lines" (at least, for normal-sized text). Since I wrote the CALENDAR program from ground up, so to speak, the days on the calendar were thought of as a cell with "stuff" in it, such as the day-of-month of course, and optional day-of-year, optional moon phase, and optional highlighting of the "today"'s date, it was easy to code the program to adjust for different size cells, and things like spacing between months and other such niceties, including re-sizing of the cells. [As an aside, the company that I worked for was small enough (about 30 programmers plus support staff), so everyone's birthday was also shown, letting people know that there is cake and ice cream in the breakroom --- but I digress.] Originally, it's primary purpose was to just show the current month's calendar when users logged on (but only when using a display terminal). You couldn't believe the requests for modifications to add this & that to the program by the company's programmers. The CALENDAR program is in actuality, just a part of my general-purpose "DATE" routine, with the CALendar option as, ... well, an option.
 
:: I wish the original task had stated the obvious (but didn't) that instead of "a" calender, it would've said a Gregorian calendar. Almost everyone has shown a Gregorian calender, except for those that mixed a Julian calendar with a Gregorian calendar ([in a failed attempt to show the "missing days" when (whoever) switched from the Julian calendar to a Gregorian calendar]. There are no missing days. When the Gregorian calendar was implemented (wherever the locality), it was designed as being proleptic. That is, when the Gregorian calendar was adopted by a country, the previous day wasn't missing, it just was the previous day, way back to day one of year one (as if the Gregorian calendar had been in effect all the time). -- [[User:Gerard Schildberger|Gerard Schildberger]] 01:46, 14 April 2012 (UTC)
<br>Below is an extract from the newsgroup bit.listserv.ibm-main (unfortunately, I have lost the author and date it was posted) which addresses the 10 or 11 missing days holy war:
<pre>