PROCEDURE command - Revision history

Dme: /* Usage notes */

2018-04-27T01:46:11Z

Usage notes

← Older revision		Revision as of 01:46, 27 April 2018
Line 92:		Line 92:
	.		.
	.		.
	<b>END PROCEDURE</b>		<b>END PROCEDURE PAY</b>
	<b></b>*** M204.1146: PROCEDURE PAY DEFINITION ENDED		<b></b>*** M204.1146: PROCEDURE PAY DEFINITION ENDED
	</p></li>		</p></li>

Dme: /* Syntax */

2018-04-27T01:44:45Z

Syntax

← Older revision		Revision as of 01:44, 27 April 2018
Line 8:		Line 8:

	==Syntax==		==Syntax==
	<p class="syntax">PROCEDURE { <span class="term">procnumber</span> \| <span class="term">procname</span>		<p class="syntax">PROCEDURE {<span class="term">procnumber</span> \| <span class="term">procname</span>} [ALIAS=<span class="term">alias</span>[,<span class="term">alias</span>]...] [PCLASS=<span class="term">pclass</span>]
	[ALIAS=<span class="term">alias</span>[,<span class="term">alias</span>]...]		[procedure input line]
	[PCLASS=<span class="term">pclass</span>] }		[procedure input line]
	END PROCEDURE</p>		...
			END PROCEDURE [<span class="term">procnumber</span> \| <span class="term">procname</span>] </p>

	Where:		Where:

JAL: /* Usage notes */ add info re END PROCEDURE

2018-04-26T21:39:46Z

Usage notes: add info re END PROCEDURE

← Older revision		Revision as of 21:39, 26 April 2018
Line 94:		Line 94:
	<b></b>*** M204.1146: PROCEDURE PAY DEFINITION ENDED		<b></b>*** M204.1146: PROCEDURE PAY DEFINITION ENDED
	</p></li>		</p></li>

			<li>The procedure definition concludes with the line that precedes either of these (whichever of them occurs first):
			<ul>
			<li><code>END PROCEDURE <i>procName</i></code>, where <var class="term">procName</var> matches the name specified on the <var>PROCEDURE</var> command </li>

			<li><code>END PROCEDURE</code> with no name specified </li>
			</ul></li>

	<li>A file or group must be open at the time that a permanent procedure is entered. If a procedure is associated with a file, it is stored in that file for subsequent use. If a procedure is associated with a group, it is stored in that group's procedure file, if one is available. The <var>INCLUDE</var> command is used to execute the procedure, and the <var>DELETE</var> command is used to delete it. </li>		<li>A file or group must be open at the time that a permanent procedure is entered. If a procedure is associated with a file, it is stored in that file for subsequent use. If a procedure is associated with a group, it is stored in that group's procedure file, if one is available. The <var>INCLUDE</var> command is used to execute the procedure, and the <var>DELETE</var> command is used to delete it. </li>

JAL: /* Syntax */ add END PROCEDURE

2018-04-26T21:26:42Z

Syntax: add END PROCEDURE

← Older revision		Revision as of 21:26, 26 April 2018
Line 11:		Line 11:
	[ALIAS=<span class="term">alias</span>[,<span class="term">alias</span>]...]		[ALIAS=<span class="term">alias</span>[,<span class="term">alias</span>]...]
	[PCLASS=<span class="term">pclass</span>] }		[PCLASS=<span class="term">pclass</span>] }
	</p>		END PROCEDURE</p>

	Where:		Where:

ELowell at 16:13, 22 March 2017

2017-03-22T16:13:39Z

← Older revision		Revision as of 16:13, 22 March 2017
Line 121:		Line 121:
	Only the file manager can desecure a procedure. See [[DESECURE PROCEDURE command: Removing procedure security\|DESECURE PROCEDURE: Removing procedure security]].</p>		Only the file manager can desecure a procedure. See [[DESECURE PROCEDURE command: Removing procedure security\|DESECURE PROCEDURE: Removing procedure security]].</p>

	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Syntax */

2016-08-18T16:50:11Z

Syntax

← Older revision		Revision as of 16:50, 18 August 2016
Line 53:		Line 53:
	<li>The procedure name can begin with a zero. And the procedure name "0123" is different from the procedure name "00123".		<li>The procedure name can begin with a zero. And the procedure name "0123" is different from the procedure name "00123".
	<p>		<p>
	However, names with only zeroes will all be treated as temporary procedure 0: <code>[[EDIT command\|EDIT]] 000</code> is identical to <code>E 0</code>. </p></li>		However, names with only zeroes will all be treated as temporary procedure 0, so <br /><code>[[EDIT command\|EDIT]] 000</code> is identical to <code>EDIT 0</code>. </p></li>

	<li>Alphanumeric procedure names can begin with a minus sign character (<tt>-</tt>), which is interpreted as a hyphen. For example, <code>-1myproc</code> and <code>-myproc</code> are valid procedure names.		<li>Alphanumeric procedure names can begin with a minus sign character (<tt>-</tt>), which is interpreted as a hyphen. For example, <code>-1myproc</code> and <code>-myproc</code> are valid procedure names.

JAL: /* Syntax */ misc formatting

2016-07-21T18:04:03Z

Syntax: misc formatting

← Older revision		Revision as of 18:04, 21 July 2016
Line 61:		Line 61:
	</ul>		</ul>

	<p>While procedure names up to 255 characters are technically valid, very long names will create challenges in maintaining the procedures, because the procedure name must fit on the same line as commands that reference the procedure. <br />Rocket recommends keeping procedure names shorter than 210 characters. Note ~~that~~ SirLib users <b>must</b> keep procedure names shorter than 229, and even then, SirPro will not be able to display procedure names longer than the supported screen width.</p>		<p>While procedure names up to 255 characters are technically valid, very long names will create challenges in maintaining the procedures, because the procedure name must fit on the same line as commands that reference the procedure. </p>
			<p>
			Rocket recommends keeping procedure names shorter than 210 characters. </p>
			<p class="note"><b>Note:</b> [[SirLib]] users <b>must</b> keep procedure names shorter than 229, and even then, [[SirPro]] will not be able to display procedure names longer than the supported screen width.</p>
	</td></tr>		</td></tr>

ELowell: /* Syntax */

2016-07-07T16:52:19Z

Syntax

← Older revision		Revision as of 16:52, 7 July 2016
Line 61:		Line 61:
	</ul>		</ul>

	<p>Rocket ~~Software~~ recommends ~~that you limit the length of your~~ procedure ~~name to less~~ than 210 ~~bytes~~. ~~Although a name in excess of 210 bytes is not incorrect and will not cause compile errors, it could be truncated by~~ <~~var~~>~~MSGCTL~~</~~var~~> ~~processing~~.</p>		<p>While procedure names up to 255 characters are technically valid, very long names will create challenges in maintaining the procedures, because the procedure name must fit on the same line as commands that reference the procedure. <br />Rocket recommends keeping procedure names shorter than 210 characters. Note that SirLib users <b>must</b> keep procedure names shorter than 229, and even then, SirPro will not be able to display procedure names longer than the supported screen width.</p>
	</td></tr>		</td></tr>

JAL: add details to zero in proc names

2016-07-06T23:59:23Z

add details to zero in proc names

← Older revision		Revision as of 23:59, 6 July 2016
Line 51:		Line 51:
	<li>Most of the above characters are permitted if <code>CUSTOM=42</code> is turned on. Names containing special characters must be enclosed in single quotes for all procedure commands. See [[CUSTOM parameter#Using CUSTOM=(42)\|Using CUSTOM=(42)]] for details.</li>		<li>Most of the above characters are permitted if <code>CUSTOM=42</code> is turned on. Names containing special characters must be enclosed in single quotes for all procedure commands. See [[CUSTOM parameter#Using CUSTOM=(42)\|Using CUSTOM=(42)]] for details.</li>

	<li>The procedure name can begin with a zero.</li>		<li>The procedure name can begin with a zero. And the procedure name "0123" is different from the procedure name "00123".
			<p>
			However, names with only zeroes will all be treated as temporary procedure 0: <code>[[EDIT command\|EDIT]] 000</code> is identical to <code>E 0</code>. </p></li>

	<li>Alphanumeric procedure names can begin with a minus sign character (-), which is interpreted as a ~~dash~~. For example, <code>-1myproc</code> and <code>-myproc</code> are valid procedure names.</li>		<li>Alphanumeric procedure names can begin with a minus sign character (<tt>-</tt>), which is interpreted as a hyphen. For example, <code>-1myproc</code> and <code>-myproc</code> are valid procedure names.
	</ul>		<p>
	</li>		Numeric procedure names that begin with a minus sign are treated as temporary procedures, and leading zeroes after the minus sign are ignored if they are followed by a non-zero digit (<code>E -1</code> is identical to <code>E -001</code>). </p></li>
			</ul></li>
	</ul>		</ul>

Line 75:		Line 78:
	<li>The <var>PROCEDURE</var> command lets you create a new procedure or replace an existing one. A procedure can contain SOUL requests, commands, or nonexecutable text. The name or number specified in this command is used to refer to this procedure in subsequent procedure commands such as <var>INCLUDE</var>, <var>DELETE</var>, and <var>DISPLAY</var>.</li>		<li>The <var>PROCEDURE</var> command lets you create a new procedure or replace an existing one. A procedure can contain SOUL requests, commands, or nonexecutable text. The name or number specified in this command is used to refer to this procedure in subsequent procedure commands such as <var>INCLUDE</var>, <var>DELETE</var>, and <var>DISPLAY</var>.</li>

	<li>The following example illustrates the use of the PROCEDURE command:		<li>The following example illustrates the use of the <var>PROCEDURE</var> command:
	<p class="code"><b>PROCEDURE PAY ALIAS=PAYCHECK</b>		<p class="code"><b>PROCEDURE PAY ALIAS=PAYCHECK</b>
	<b></b>*** M204.1144: DEFINE PROCEDURE PAY		<b></b>*** M204.1144: DEFINE PROCEDURE PAY

JAL: misc formatting

2016-07-06T00:30:02Z

misc formatting

Show changes