Calendar - for "REAL" programmers: Difference between revisions

Line 37:

This is for real programmers who code only in assembler :). The code could have been run in april 1964, punched on

80-column cards, read on a card reader, and printed with a 132-column line printer on fan-folded paper with perforated edges.

<~~lang~~ 360asm>* CALENDAR FOR REAL PROGRAMMERS 05/03/2017

<syntaxhighlight lang=360asm>* CALENDAR FOR REAL PROGRAMMERS 05/03/2017

CALENDAR CSECT

USING CALENDAR,R13 BASE REGISTER

Line 217:

DA DS 12CL144

YREGS

END CALENDAR</~~lang~~>

END CALENDAR</syntaxhighlight>

<pre> INSERT SNOOPY HERE

Line 243:

Instead of doing that, the implementation below reuses the package "PRINTABLE_CALENDAR" (same as "Printable_Calendar" or "printable_calendar") from [[Calendar#Ada|the calendar task]]:

<~~lang~~ Ada>WITH PRINTABLE_CALENDAR;

<syntaxhighlight lang=Ada>WITH PRINTABLE_CALENDAR;

PROCEDURE REAL_CAL IS

Line 263:

C.NEW_LINE;

C.PRINT(1969, "NINETEEN-SIXTY-NINE");

END REAL_CAL;</~~lang~~>

END REAL_CAL;</syntaxhighlight>

Line 296:

Note: to run this code with [[ALGOL 68G]] you need to use the '''--quote-stropping''' option.

<~~lang~~ algol68>'PR' QUOTE 'PR'

<syntaxhighlight lang=algol68>'PR' QUOTE 'PR'

'PROC' PRINT CALENDAR = ('INT' YEAR, PAGE WIDTH)'VOID': 'BEGIN'

Line 403:

LINE PRINTER WIDTH = 132; # AS AT 1969! #

PRINT CALENDAR(MANKIND STEPPED ON THE MOON, LINE PRINTER WIDTH)

'END'</~~lang~~>

'END'</syntaxhighlight>

<pre>

Line 428:

=={{header|AutoHotkey}}==

<~~lang~~ AutoHotkey>CALENDAR(YR){

<syntaxhighlight lang=AutoHotkey>CALENDAR(YR){

LASTDAY := [], DAY := []

TITLES =

Line 466:

STRINGREPLACE, RES, RES,%A_SPACE%0,%A_SPACE%%A_SPACE%, ALL

RETURN RES

}</~~lang~~>

}</syntaxhighlight>

Examples:<~~lang~~ AutoHotkey>EXAMPLES:

Examples:<syntaxhighlight lang=AutoHotkey>EXAMPLES:

GUI, FONT,S8, COURIER

GUI, ADD, EDIT, VYR W40 R1 LIMIT4 NUMBER, 1969

Line 482:

GUICLOSE:

EXITAPP

RETURN</~~lang~~>

RETURN</syntaxhighlight>

<pre> 1969

Line 525:

=={{header|BaCon}}==

Choosing 132 character output. Same as the "Calendar" from [[Calendar#BaCon|the calendar task]] but using all capitals:

<~~lang~~ freebasic>DECLARE MON$[] = { "JANUARY", "FEBRUARY", "MARCH", "APRIL", "MAY", "JUNE", "JULY", "AUGUST", "SEPTEMBER", "OCTOBER", "NOVEMBER", "DECEMBER" }

<syntaxhighlight lang=freebasic>DECLARE MON$[] = { "JANUARY", "FEBRUARY", "MARCH", "APRIL", "MAY", "JUNE", "JULY", "AUGUST", "SEPTEMBER", "OCTOBER", "NOVEMBER", "DECEMBER" }

DECLARE MON[] = { 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 }

Y$ = "1969"

Line 557:

PRINT D;

NEXT</~~lang~~>

NEXT</syntaxhighlight>

Line 582:

=={{header|BBC BASIC}}==

<~~lang~~ bbcbasic> VDU 23,22,1056;336;8,16,16,128

<syntaxhighlight lang=bbcbasic> VDU 23,22,1056;336;8,16,16,128

YEAR = 1969

Line 628:

WHEN 4,6,9,11: = 30

OTHERWISE = 31

ENDCASE</~~lang~~>

ENDCASE</syntaxhighlight>

<pre>

Line 670:

tcc -DSTRUCT=struct -DCONST=const -DINT=int -DCHAR=char -DVOID=void -DMAIN=main -DIF=if -DELSE=else -DWHILE=while -DFOR=for -DDO=do -DBREAK=break -DRETURN=return -DPUTCHAR=putchar UCCALENDAR.c

</pre>

<~~lang~~ c>/* UPPER CASE ONLY VERSION OF THE ORIGINAL CALENDAR.C, CHANGES MOSTLY TO AVOID NEEDING #INCLUDES */

<syntaxhighlight lang=c>/* UPPER CASE ONLY VERSION OF THE ORIGINAL CALENDAR.C, CHANGES MOSTLY TO AVOID NEEDING #INCLUDES */

/* ERROR MESSAGES GO TO STDOUT TO SLIGHTLY SIMPLIFY THE I/O HANDLING */

/* WHEN COMPILING THIS, THE COMMAND LINE SHOULD SPECIFY -D OPTIONS FOR THE FOLLOWING WORDS: */

Line 835:

}

RETURN RESULT;

}</~~lang~~>

}</syntaxhighlight>

=={{header|COBOL}}==

Line 842:

=={{header|Common Lisp}}==

<~~lang~~ lisp>(QL:QUICKLOAD '(DATE-CALC))

<syntaxhighlight lang=lisp>(QL:QUICKLOAD '(DATE-CALC))

(DEFPARAMETER *DAY-ROW* "SU MO TU WE TH FR SA")

Line 916:

(LAMBDA (&REST HEADS)

(FORMAT T FORMAT-STRING HEADS))

ROW))))</~~lang~~>

ROW))))</syntaxhighlight>

<pre>CL-USER> (PRINT-CALENDAR 1969)

Line 1,012:

Then in another source code file there is a little loader, that imports it and mixes-in it (for safety this program must be compiled with <code>-Jsomepath</code>):

<~~lang~~ d>import std.string;mixin(import("CALENDAR").toLower);void main(){}</~~lang~~>

<syntaxhighlight lang=d>import std.string;mixin(import("CALENDAR").toLower);void main(){}</syntaxhighlight>

<pre> [Snoopy Picture]

Line 1,055:

=={{header|Elena}}==

ELENA 5.0 :

<~~lang~~ elena>import system'text;

<syntaxhighlight lang=elena>import system'text;

import system'routines;

import system'calendar;

Line 1,215:

console.readChar()

}</~~lang~~>

}</syntaxhighlight>

<pre>

Line 1,257:

=={{header|Fortran}}==

Alas, the header "FORTRAN" is not recognised - REAL programmers were absent that day? Even upon the apperance of lower case, I have preferred to use shouting for programme source, and normal upper/lower case for commentary. Aside from petty details such as 1 and l being nowhere as distinct as 1 and L, this allows the two sorts of blather to be identifiably different without ratiocination as the hours drag past. Further, the names of variables can easily be distinguished from the same word in discussion, as in ... the text in TEXT will be printed as the subtitle to the text in TITLE ... Anyway, in the spirit of old, herewith the source without tedious commentary:

<~~lang~~ FORTRAN>

MODULE DATEGNASH

Line 1,433:

END DO

END

</syntaxhighlight>

</lang>

And for output, the wide form:

Line 1,458:

=={{header|FreeBASIC}}==

<~~lang~~ freebasic>' VERSION 16-03-2016

<syntaxhighlight lang=freebasic>' VERSION 16-03-2016

' COMPILE WITH: FBC -S CONSOLE

Line 1,554:

PRINT : PRINT "HIT ANY KEY TO END PROGRAM"

SLEEP

END</~~lang~~>

END</syntaxhighlight>

<pre> INSERT YOUR SNOOPY PICTURE HERE

Line 1,584:

This is realcal_UC.txt:

<~~lang~~ go>PACKAGE MAIN

<syntaxhighlight lang=go>PACKAGE MAIN

IMPORT (

Line 1,654:

FMT.PRINTLN()

}

}</~~lang~~>

}</syntaxhighlight>

and this is realcal.go:

<~~lang~~ go>package main

<syntaxhighlight lang=go>package main

import (

Line 1,696:

cmd.Stderr = os.Stderr

check(cmd.Run())

}</~~lang~~>

}</syntaxhighlight>

which produces (as expected) this output:

Line 1,745:

In Graphical User Interface Support Script, we utilize applications that are already written. So for this task, we shall just display the calendar that sets the system clock.

<~~lang~~ guiss>RIGHTCLICK:CLOCK,ADJUST DATE AND TIME,BUTTON:CANCEL</~~lang~~>

<syntaxhighlight lang=guiss>RIGHTCLICK:CLOCK,ADJUST DATE AND TIME,BUTTON:CANCEL</syntaxhighlight>

=={{header|Icon}} and {{header|Unicon}}==

Line 1,768:

Also it makes me go all nostalgic for my old [[WATFIVE]] compiler. And an IBM 129 keypunch. And 5 hole paper tape.

<~~lang~~ Unicon>$include "REALIZE.ICN"

<syntaxhighlight lang=Unicon>$include "REALIZE.ICN"

LINK DATETIME

Line 1,816:

IF M = 2 & ISLEAPYEAR(YEAR) THEN SUSPEND (DAY +:= 1, 29)

EVERY DAY TO (6*7) DO SUSPEND ""

END</~~lang~~>

END</syntaxhighlight>

Where REALIZE.ICN would be something like this (this example is incomplete but sufficient for this program):

<~~lang~~ Icon>$define PROCEDURE procedure

<syntaxhighlight lang=Icon>$define PROCEDURE procedure

$define END end

$define WRITE write

Line 1,846:

$define BY by

$define DATETIME datetime

$define RETURN return</~~lang~~>

$define RETURN return</syntaxhighlight>

Line 1,854:

For added "real"ness, we also only use 1 character names:

<~~lang~~ J>B=: + 4 100 400 -/@:<.@:%~ <:

<syntaxhighlight lang=J>B=: + 4 100 400 -/@:<.@:%~ <:

M=: 28+ 3, (10$5$3 2),~ 0 ~:/@:= 4 100 400 | ]

R=: (7 -@| B+ 0, +/\@}:@M) |."0 1 (0,#\#~41) (]&:>: *"1 >/)~ M

Line 1,863:

L=: |."0 1~ +/ .(*./\@:=)"1&' '

E=: (|."0 1~ _2 <.@%~ +/ .(*./\.@:=)"1&' ')@:({."1) L

F=: 0 _1 }. 0 1 }. (2+[) E '[INSERT SNOOPY HERE]', ":@], D</~~lang~~>

F=: 0 _1 }. 0 1 }. (2+[) E '[INSERT SNOOPY HERE]', ":@], D</syntaxhighlight>

B: given a year returns a number which when added to numeric values indexing days that year, mod 7, index the proper day names within a week. (In other words 7 | 0 + B 1969 gives the day of week index for the first day of 1969.)

Line 1,885:

Here's an example calendar (the first line <code>132 F 1969</code> being the command that build this calendar):

<lang> 132 F 1969

<syntaxhighlight lang=text> 132 F 1969

[INSERT SNOOPY HERE]

1969

Line 1,907:

│ │31 │ │ │30 │ │

└────────────────────┴────────────────────┴────────────────────┴────────────────────┴────────────────────┴────────────────────┘

</syntaxhighlight>

</lang>

Note that this version of F will work fine with a left argument of 20 (why anyone felt that this was important to mention is perhaps best thought of as an issue lost in history).

Line 1,914:

Julia code is a valid data type in Julia. Executable code can be created from a String with Meta.parse() and run with eval.

This example does require a small function with Julia's lowercase keywords, perhaps loaded on startup from a separate file.

<~~lang~~ julia>

# IF THIS SMALL FUNCTION IS PLACED IN THE STARTUP.JL

# FILE, IT WILL BE LOADED ON STARTUP. THE REST OF

Line 1,972:

RUNUPPERCASECODE(CODE)

</~~lang~~> {{output}} <pre>

</syntaxhighlight> {{output}} <pre>

1969

JANUARY FEBRUARY MARCH APRIL MAY JUNE

Line 2,004:

This is calendar_UC.txt:

<~~lang~~ scala>IMPORT JAVA.TEXT.*

<syntaxhighlight lang=scala>IMPORT JAVA.TEXT.*

IMPORT JAVA.UTIL.*

IMPORT JAVA.IO.PRINTSTREAM

Line 2,055:

FUN MAIN(ARGS: ARRAY<STRING>) {

SYSTEM.OUT.PRINTCALENDAR(1969, 3, LOCALE.US)

}</~~lang~~>

}</syntaxhighlight>

and this is real_calendar.kt:

<~~lang~~ scala>// version 1.1.3

<syntaxhighlight lang=scala>// version 1.1.3

import java.io.File

Line 2,142:

br.close()

println(out.toString())

}</~~lang~~>

}</syntaxhighlight>

which generates (on disk) calendar_NC.kt:

<~~lang~~ scala>import java.text.*

<syntaxhighlight lang=scala>import java.text.*

import java.util.*

import java.io.PrintStream

Line 2,197:

fun main(args: Array<String>) {

System.out.PRINTCALENDAR(1969, 3, Locale.US)

}</~~lang~~>

}</syntaxhighlight>

which when compiled and run produces output of:

Line 2,249:

The upper case Lua source - stored in a file called UCCALENDAR.LUU:

<~~lang~~ lua>FUNCTION PRINT_CAL(YEAR)

<syntaxhighlight lang=lua>FUNCTION PRINT_CAL(YEAR)

LOCAL MONTHS={"JANUARY","FEBRUARY","MARCH","APRIL","MAY","JUNE",

"JULY","AUGUST","SEPTEMBER","OCTOBER","NOVEMBER","DECEMBER"}

Line 2,312:

PRINT_CAL(1969)

</syntaxhighlight>

</lang>

The following "one-liner" standard Lua source will down-case and run the program in the source file specified as it's parameter (file luu.lua):

<~~lang~~ lua>do io.input( arg[ 1 ] ); local s = io.read( "*a" ):lower(); io.close(); assert( load( s ) )() end

<syntaxhighlight lang=lua>do io.input( arg[ 1 ] ); local s = io.read( "*a" ):lower(); io.close(); assert( load( s ) )() end

</syntaxhighlight>

</lang>

The following command will execute the UCCALENDAR.LUU source (replace lua532 with the appropriate command for your system):

Line 2,368:

Console 132 characters by 43 lines. Six columns for months.

<~~lang~~ M2000 Interpreter>

\\ Calendar - for "REAL" programmers

\\ All statements in UPPERCASE

Line 2,516:

END WHILE

RETURN

</syntaxhighlight>

</lang>

=={{header|Nim}}==

Line 2,527:

Here is the helper program:

<lang>import strutils

<syntaxhighlight lang=text>import strutils

const progUpper = staticRead("calendar_upper.txt")

Line 2,557:

static: writeFile("calendar_transformed.nim", prog)

include "calendar_transformed.nim"</~~lang~~>

include "calendar_transformed.nim"</syntaxhighlight>

Here is the actual program in uppercase.

<lang>IMPORT TIMES

<syntaxhighlight lang=text>IMPORT TIMES

IMPORT STRFORMAT

Line 2,598:

ECHO ""

PRINTCALENDAR(1969, 5)</~~lang~~>

PRINTCALENDAR(1969, 5)</syntaxhighlight>

Line 2,637:

at the top level, we need to abuse backticks in order to print anything, as in [http://www.perlmonks.org/?node_id=43797 the infamous JAPH with no letters or numbers]. Consequently, the calendar is printed to standard error instead of standard output.

<~~lang~~ perl>$PROGRAM = '\'

<syntaxhighlight lang=perl>$PROGRAM = '\'

MY @START_DOW = (3, 6, 6, 2, 4, 0,

Line 2,680:

$L = ',' | '@';

`${E}${C}${H}${O} $PROGRAM | ${T}${R} A-Z ${A}-${Z} | ${P}${E}${R}${L}`;</~~lang~~>

`${E}${C}${H}${O} $PROGRAM | ${T}${R} A-Z ${A}-${Z} | ${P}${E}${R}${L}`;</syntaxhighlight>

Although, if we are abusing the backticks and other innocent programs, why not just: <~~lang~~ Perl>$_=$ARGV[0]//1969;`\143\141\154 $_ >&2`</~~lang~~>

Although, if we are abusing the backticks and other innocent programs, why not just: <syntaxhighlight lang=Perl>$_=$ARGV[0]//1969;`\143\141\154 $_ >&2`</syntaxhighlight>

=={{header|Phix}}==

Line 2,687:

So, the first task is to take a copy of [[Calendar#Phix|Calendar]] and make it output uppercase. Change the line

return repeat(' ',left)&s&repeat(' ',right)

in routine centre to:

return repeat(' ',left)&upper(s)&repeat(' ',right)

(That's that done.) Now, Phix is case-sensitive, and many of the keywords and builtins are in lower case, which presents a bit of a challenge - but we can cope.

It is too tedious and not particularly helpful to present a completed solution, instead I shall outline the (relatively simple) steps this would require. I have limited my tests to INCLUDE and INTEGER.

In psym.e you can find the line

initialSymEntry("integer", S_Type,"TI",opInt, E_none) -- #01 / 0b0001 integer

Immediately after that (it should now be there commented out) add:

Alias("INTEGER",symlimit)

Add similar lines for length, floor, repeat, upper, day_of_week, sequence, string, sprintf, append, printf, join, at the appropriate places.

Keywords are handled slightly differently: In pttree.e we need a new alias routine (you should find this one commented out, from when I was testing all this):

procedure tt_stringA(sequence text, integer alias)

tt_string(text,-2)

tt[pcurr] = alias

end procedure

and you can find the line

global constant T_include = 596 tt_stringF("include",T_include)

Sometime after that, in fact after the very last use of tt_stringF, add (likewise you should find this one commented out):

tt_stringA("INCLUDE",T_include)

Add similar lines for function, end, iff, for, to, do, if, or, then, else, return, procedure, but this time all some ways away from the originals. Quickly run "p p" and make sure you get a normal prompt, without any "T_include should be 624(not 596)" or suchlike (which would happen alot if you put the aliases anywhere other than last).

Line 2,728:

Currently ptok.e recognises <code>\n</code> but not <code>\N</code>. Search for all references to <code>escchar</code> (there should be one definition and two references) and make sure the character being

checked is mapped to lower case, ie change (twice)

Ch = find(Ch,escchar)

to

Ch = find(lower(Ch),escchar)

Lastly, the calendar example includes builtins\timedate.e, which contains some lower-case definitions. So copy it to (say) TIMEDATEUPPER.E and change adjust_timedate, timedelta, days (the 2nd param to timedelta), and format_timedate to their uppercase equivalents, and of course change that include to <code>INCLUDE BUILTINS\TIMEDATEUPPER.E</code>.

Line 2,748:

While PHP functions are case-sensitive (aside of <code>_()</code>), this isn't the case for language constructs.

<~~lang~~ php><?PHP

<syntaxhighlight lang=php><?PHP

ECHO <<<REALPROGRAMMERSTHINKINUPPERCASEANDCHEATBYUSINGPRINT

JANUARY FEBRUARY MARCH APRIL MAY JUNE

Line 2,767:

28 29 30 31 25 26 27 28 29 30 31 29 30 27 28 29 30 31 24 25 26 27 28 29 30 29 30 31

REALPROGRAMMERSTHINKINUPPERCASEANDCHEATBYUSINGPRINT

; // MAGICAL SEMICOLON</~~lang~~>

; // MAGICAL SEMICOLON</syntaxhighlight>

=={{header|PicoLisp}}==

The "CALENDAR.L" source file:

<~~lang~~ PicoLisp>(DE CAL (YEAR)

<syntaxhighlight lang=PicoLisp>(DE CAL (YEAR)

(PRINL "====== " YEAR " ======")

(FOR DAT (RANGE (DATE YEAR 1 1) (DATE YEAR 12 31))

Line 2,784:

(CAL 1969)

(BYE)</~~lang~~>

(BYE)</syntaxhighlight>

Then it can be executed with this command line:

<pre>$ pil -'load (list "awk" "{print tolower($0)}" "CALENDAR.L")'</pre>

Line 2,814:

=={{header|PL/I}}==

<~~lang~~ PL/I>(SUBRG, SIZE, FOFL):

<syntaxhighlight lang=PL/I>(SUBRG, SIZE, FOFL):

CALENDAR: PROCEDURE (YEAR) OPTIONS (MAIN);

DECLARE YEAR CHARACTER (4) VARYING;

Line 2,865:

END PREPARE_MONTH;

END CALENDAR;</~~lang~~>

END CALENDAR;</syntaxhighlight>

See CALENDAR for result.

=={{header|Racket}}==

<~~lang~~ racket>

#CI(MODULE NAME-OF-THIS-FILE RACKET

(REQUIRE RACKET/DATE)

Line 2,905:

(CALENDAR 1969))

</syntaxhighlight>

</lang>

=={{header|Raku}}==

Line 2,911:

Uppercase is no challenge, who needs letters at all?

[Requires the year to be supplied as a command-line argument, and Unixish cal command.]

<lang ~~perl6~~>$_="\0".."~";<

<syntaxhighlight lang=raku line>$_="\0".."~";<

115 97 121 32 34 91 73 78 83 69 82 84 32 83 78 79 79 80 89 32 72 69 82 69 93 34

59 114 117 110 32 60 99 97 108 62 44 64 42 65 82 71 83 91 48 93 47 47 49 57 54 57

>."$_[99]$_[104]$_[114]$_[115]"()."$_[69]$_[86]$_[65]$_[76]"()</~~lang~~>

>."$_[99]$_[104]$_[114]$_[115]"()."$_[69]$_[86]$_[65]$_[76]"()</syntaxhighlight>

=={{header|REXX}}==

Line 2,937:

(but the second REXX version sure as heck looks

like it was beat with a big ole ugly stick ─── and pardon the strong language).

<~~lang~~ rexx>/*REXX PROGRAM TO SHOW ANY YEAR'S (MONTHLY) CALENDAR (WITH/WITHOUT GRID)*/

<syntaxhighlight lang=rexx>/*REXX PROGRAM TO SHOW ANY YEAR'S (MONTHLY) CALENDAR (WITH/WITHOUT GRID)*/

@ABC=

PARSE VALUE SCRSIZE() WITH SD SW .

Line 3,109:

PUT:_=ARG(1);_=TRANSLATE(_,,'_'CHK);IF \GRID THEN _=UNGRID(_);IF LOWERCASE THEN _=LOWER(_);IF UPPERCASE THEN UPPER _;IF SHORTEST&_=' ' THEN RETURN;CALL TELL _;RETURN

TELL:SAY ARG(1);RETURN

UNGRID:RETURN TRANSLATE(ARG(1),,"│║─═┤┐└┴┬├┼┘┌╔╗╚╝╟╢╞╡╫╪╤╧╥╨╠╣")</~~lang~~>

UNGRID:RETURN TRANSLATE(ARG(1),,"│║─═┤┐└┴┬├┼┘┌╔╗╚╝╟╢╞╡╫╪╤╧╥╨╠╣")</syntaxhighlight>

Programming note:   This REXX program makes use of   '''SCRSIZE'''   REXX program (or

BIF) which is used to determine the screen

Line 3,218:

=={{header|Ring}}==

<~~lang~~ ring>

# PROJECT : CALENDAR - FOR "REAL" PROGRAMMERS

# DATE : 2018/06/28

Line 3,377:

</syntaxhighlight>

</lang>

Output:

Line 3,388:

* <code>loadup.rb</code> is the program loader.

<~~lang~~ ruby># loadup.rb - run UPPERCASE RUBY program

<syntaxhighlight lang=ruby># loadup.rb - run UPPERCASE RUBY program

class Object

Line 3,413:

_PROGRAM = ARGV.SHIFT

_PROGRAM || ABORT("USAGE: #{$0} PROGRAM.RB ARGS...")

LOAD($0 = _PROGRAM)</~~lang~~>

LOAD($0 = _PROGRAM)</syntaxhighlight>

* <code>CAL.RB</code> is an UPPERCASE RUBY translation of [[Calendar#Ruby]].

<~~lang~~ ruby># CAL.RB - CALENDAR

<syntaxhighlight lang=ruby># CAL.RB - CALENDAR

REQUIRE 'DATE'.DOWNCASE

Line 3,500:

PROC {80}) }) })

PUTS CAL(ARGV[0].TO_I, _COLUMNS)</~~lang~~>

PUTS CAL(ARGV[0].TO_I, _COLUMNS)</syntaxhighlight>

* A local variable must start with a lowercase letter or an underscore, so we have many leading underscores (_YEAR, _COLUMN, _DATE and so on).

Line 3,585:

Then in another program the file CALENDAR.TXT is [http://seed7.sourceforge.net/libraries/getf.htm#getf%28in_string%29 read], converted, [http://seed7.sourceforge.net/libraries/progs.htm#parseStri%28in_string,in_parseOptions,in_array_string,in_string%29 parsed] and [http://seed7.sourceforge.net/libraries/progs.htm#execute%28in_program,in_array_string,in_parseOptions,in_string%29 executed]:

<~~lang~~ seed7>$ include "seed7_05.s7i";

<syntaxhighlight lang=seed7>$ include "seed7_05.s7i";

include "getf.s7i";

include "progs.s7i";

Line 3,597:

source := replace(source, "daysinmonth", "daysInMonth");

execute(parseStri(source));

end func;</~~lang~~>

end func;</syntaxhighlight>

Line 3,640:

=={{header|Sidef}}==

<~~lang~~ ruby>-> DT { ('DATE'.("\LWC") + 'TIME'.("\LWC")).("\LREQUIRE") }

<syntaxhighlight lang=ruby>-> DT { ('DATE'.("\LWC") + 'TIME'.("\LWC")).("\LREQUIRE") }

-> MONTHS_PER_COL { 6 }

Line 3,698:

}

FMT_YEAR(ARGV ? ARGV[0].("\LTO_I") : 1969).("\LPRINT")</~~lang~~>

FMT_YEAR(ARGV ? ARGV[0].("\LTO_I") : 1969).("\LPRINT")</syntaxhighlight>

<pre>

Line 3,722:

The program starts implementing aliases for all built-in commands. This is done without using any letters at all ;).

CALENDER takes arguments of year and optional terminal width to use.

<~~lang~~ tcl>

\146\157\162\145\141\143\150 42 [\151\156\146\157 \143\157\155\155\141\156\144\163] {

\145\166\141\154 "

Line 3,771:

CALENDAR

</syntaxhighlight>

</lang>

<pre>

Line 3,812:

=={{header|UNIX Shell}}==

<~~lang~~ shell>CAL=CAL

<syntaxhighlight lang=shell>CAL=CAL

TR=TR

A=A

Z=Z

LANG=C ${CAL,,} 1969 | ${TR,,} ${A,}-${Z,} A-Z</~~lang~~>

LANG=C ${CAL,,} 1969 | ${TR,,} ${A,}-${Z,} A-Z</syntaxhighlight>

<pre>

Line 3,861:

Vedit macro language is case insensitive, but it is normal practice to write short commands in upper case.

<~~lang~~ vedit>BS(BF)

<syntaxhighlight lang=vedit>BS(BF)

CFT(22)

#3 = 6 // NUMBER OF MONTHS PER LINE

Line 3,925:

REG_EMPTY(#20)

NUM_POP(4,20)

RETURN </~~lang~~>

RETURN </syntaxhighlight>

<pre>

Line 3,958:

Copied from [[Calendar#Visual_Basic_.NET]] and converted to uppercase. See entry there for description.

<~~lang~~ vbnet>OPTION COMPARE BINARY

<syntaxhighlight lang=vbnet>OPTION COMPARE BINARY

OPTION EXPLICIT ON

OPTION INFER ON

Line 4,288:

RETURN S.PADLEFT(((TOTALWIDTH - S.LENGTH) \ 2) + S.LENGTH, PADDINGCHAR).PADRIGHT(TOTALWIDTH, PADDINGCHAR)

END FUNCTION

END MODULE</~~lang~~>

END MODULE</syntaxhighlight>

{{out|input=COLS:132 ROWS:25 MS/ROW:6 HSTRETCH:FALSE VSTRETCH:FALSE}}

Line 4,324:

<~~lang~~ ecmascript>IMPORT "/DATE" FOR DATE

<syntaxhighlight lang=ecmascript>IMPORT "/DATE" FOR DATE

IMPORT "/FMT" FOR FMT

IMPORT "/SEQ" FOR LST

Line 4,371:

}

CALENDAR.CALL(1969)</~~lang~~>

CALENDAR.CALL(1969)</syntaxhighlight>

We then create a script called ''calendar_real.wren'' which takes the above text file as input, changes those items which cannot be upper case into their normal casing and compiles and runs the result:

<~~lang~~ ecmascript>import "io" for File

<syntaxhighlight lang=ecmascript>import "io" for File

import "/str" for Str

import "meta" for Meta

Line 4,393:

for (format in formats) text = text.replace(Str.upper(format), format)

Meta.compile(text).call()</~~lang~~>

Meta.compile(text).call()</syntaxhighlight>

Line 4,440:

ASSEMBLE WITH: TASM CALENDAR; TLINK /t CALENDAR

<~~lang~~ asm> .MODEL TINY

<syntaxhighlight lang=asm> .MODEL TINY

.CODE

.486

Line 4,626:

DAYS DB 0, 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31

DAY DB ?, ?, ?, ?, ?, ?

END START</~~lang~~>

END START</syntaxhighlight>

Line 4,654:

=={{header|XLISP}}==

XLISP isn't case-sensitive, so in principle it would be possible just to reproduce the solution given in the "ordinary" Calendar task. But that program makes use of recursion, "fancy" data structures, long variable names, pretty-printy indentation, and a whole host of other features that I don't think REAL programmers like any better than they like lower case: so, instead, here is a version using only global variables and "<tt>DO</tt> loops like God meant them to be".

<~~lang~~ lisp>(SETQ YR 1969)

<syntaxhighlight lang=lisp>(SETQ YR 1969)

(SETQ M #("JANUARY" "FEBRUARY" "MARCH" "APRIL" "MAY" "JUNE" "JULY" "AUGUST" "SEPTEMBER" "OCTOBER" "NOVEMBER" "DECEMBER"))

(SETQ ML #(31 28 31 30 31 30 31 31 30 31 30 31))

Line 4,689:

(SETQ D (+ D 1))

(IF (> D 6) (TERPRI))

(IF (> D 6) (SETQ D 0))))</~~lang~~>

(IF (> D 6) (SETQ D 0))))</syntaxhighlight>

<pre> SNOOPY CALENDAR 1969

Line 4,787:

The calendar code, file UPCAL.zkl (upper cased version of [[Calendar#zkl]]):

<~~lang~~ zkl>VAR [CONST] D=TIME.DATE, DAYS="SU MO TU WE TH FR SA";

<syntaxhighlight lang=zkl>VAR [CONST] D=TIME.DATE, DAYS="SU MO TU WE TH FR SA";

FCN CENTER(TEXT,M) { STRING(" "*((M-TEXT.LEN())/2),TEXT) }

Line 4,798:

.PUMP(LIST,T(VOID.READ,DAYS.LEN()/3,FALSE),STRING.CREATE));

}

...</~~lang~~>

...</syntaxhighlight>

And the pre-processor, hand rolled for the above code (file bbb.zkl):

<~~lang~~ zkl>code:=File(vm.arglist[0]).read();

<syntaxhighlight lang=zkl>code:=File(vm.arglist[0]).read();

code=Data(Void,code.text.toLower());

mixed:=T("string","String", "list","List", " t("," T(",",t(",",T(",

Line 4,810:

);

mixed.pump(Void,Void.Read,'wrap(up,down){ code.replace(up,down) });

Compiler.Compiler.compileText(code)();</~~lang~~>

Compiler.Compiler.compileText(code)();</syntaxhighlight>

<pre>