From e06a3229d761020f7076fe022f350ba33892a62a Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Sun, 9 May 2004 22:32:43 +0000 Subject: [PATCH] Yest another page. --- doc/mad-manual.xml | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/doc/mad-manual.xml b/doc/mad-manual.xml index 1cff6f7..44c5da5 100644 --- a/doc/mad-manual.xml +++ b/doc/mad-manual.xml @@ -4734,7 +4734,7 @@ possibilities are suggested by the comment. in much greater detail in other Computing Center write-ups. However, the following sections should be sufficient for the general use of MAD. - + Subroutines which are written for use by MAD programsⅆwhether @@ -4998,6 +4998,30 @@ The interpretation of the mode is implicit in the operator and conversion definition programs. Mode declarations may occur anywhere, as before, except within operator and conversion definition programs. + +The DEFINE Statement + +The first statement of an operation definition program is + + + + + + + +where .NAME. is the name of the operator being defined (the operator +may be either binary or unary), and .OPER. is the name or symbol of +some exist­ing or previously defined operator. This statement +establishes the precedence (relative to the missing-parenthesis +convention) of the operator .NAME. as being (1) immediately above that +of .OPER. (but below all those already above .OPER.), (2) equal to +that of .OPER., or (3) immediately below that of .OPER. (but above all +those already below .OPER.). The name .OPER. could also be a single +character, such as *, +(binary), -(binary), or /. Unary minus can be +referred to in such statements by the name -U. Unary plus should not +be used. + + -- 2.43.0