Empty program: Difference between revisions

m
→‎{{header|REXX}}: elided versions that specified which type of scripting language it is.
(Kotlin snippet replaced)
m (→‎{{header|REXX}}: elided versions that specified which type of scripting language it is.)
Line 877:
 
=={{header|REXX}}==
An empty (or blank) file is a valid REXX program.
===version 0===
<lang rexx></lang>
 
Some REXX implementations require a special comment &nbsp; [(1<sup>st</sup> word in the comment
<br>must be &nbsp; REXX &nbsp; (in upper/lower/mixed) case] &nbsp; to distinguish from other types of
<br>scripting languages, but a null program (or a program with only blanks in it) &nbsp; in those
<br>other scripting languages are also considered an empty program.
===version 1===
This program can be empty (no characters), &nbsp; or a program with (only) one or more blanks.
However, for some REXX implementations the first line has to begin with a REXX comment (that is, &nbsp; '''/*''' &nbsp; --- namely a ''slash'' followed by an ''asterisk'') &nbsp; in order to recognize that the file is a REXX script/EXEC/program:
<lang rexx>/*comment*/</lang>
Some environments &nbsp; (TSO under "MVS", certain IBM SAA environments, and possibly others) &nbsp; require that the first line begin with a (REXX) comment, and the (four) letters &nbsp; '''REXX''' &nbsp; be somewhere on the first line (within the comment).
<br>The &nbsp; ''REXX'' &nbsp; character string may be in any case (lower/upper/mixed) and cannot contain imbedded whitespace.
<br><br>SAA: &nbsp; (IBM's) &nbsp; '''S'''ystems '''A'''pplication '''A'''rchitecture
 
===version 2===
<lang rexx>/**/</lang>
 
===version 3===
REXX on MVS/TSO requires REXX to be in within a REXX comment that begins on the first line:
<lang rexx>/*REXX*/</lang>
<lang rexx>/*this REXX program calculates if a date is a workday for the XYZ Company.*/</lang>
 
=={{header|Rhope}}==