The notational conventions I adopted, and why
At a given moment, the concept of polite mathematics emerged, the underlying idea of which is that, even if you have only 60 readers, it pays to spend an hour if by doing so you can save your average reader a minute. By inventing an idealized "average reader", we could translate most of the lofty, human goal of politeness into more or less formal criteria we could apply to our texts. This note is devoted to the resulting notational and stylistic conventions that were adopted as the years went by.
We don't want to baffle or puzzle our readers, in particular it should be clear what has to be done to check our argument and it should be possible to do so without pencil and paper. This dictates small, explicit steps. On the other hand it is well known that brevity is the leading characteristic of mathematical elegance, and some fear that this ideal excludes the small, explicit steps, but one of the joys of my professional life has been the discovery that this fear is unfounded, for brevity can be achieved without committing the sin of omission.
I should point out that my ideal of crisp clarity is not universally shared. Some consider the puzzles that are created by their omissions as spicy challenges, without which their texts would be boring; others shun clarity lest their work is considered trivial.
Infix notation and expressions
Without much hesitation I have decided to stick to the usual infix operators. They have the disadvantage of requiring parentheses to distinguish (p+q)/r from p+(q/r) which prefix notation would have rendered as /+pqr and +p/qr respectively.
Remark One of the names of prefix or Polish notation is "parenthesisfree" notation, but that is a little bit misleading, for though no longer needed, the parentheses are still permissible: we could have written /(+pq )r and +p(/qr ) respectively. (End of Remark).
A little hesitance was induced when my late colleague Wouter Peremans remarked in passing that infix notation was of course "a notational relic". It made me realize why I like it so much for associative operators: it allows us to write p+q+r without being forced to choose between (p+q )+r and p+(q+r ); in prefix notation, the choice between ++pqr and +p+qr would have been unavoidable.
The main reason to stick to the infix notation for the usual operators was, of course, that we are so terribly used to it, but the associativity does play an honest role: I did introduce —with great satisfaction!— infix operators for what I used to denote by max(x,y ) and gcd(x,y ) , and find that I don't introduce anymore infix operators that are not associative.
Priority rules, i.e., rules of relative binding power, are the standard way of reducing the number of parenthesis pairs that would otherwise be needed, but we should remember that we are not obliged to reduce them to the absolute minimum. We learned to appreciate the following customs.
• Only use priority rules that are frequently appealed to, and hence are familiar. I would not hesitate to write p+q∙r, but would avoid p/q∙r and p ⇒ q ⇒ r .
• Do not introduce priority rules that destroy symmetry. I remember how much more pleasant the predicate calculus became to work with after we had decided to give con and disjunction the same binding power and thus to consider p ∧ q ∨ r an illformed formula.
• When introducing new infix operators, parenthesize so as to postpone decisions about binding powers until experience justifies a preference.
• When you have the freedom, choose the larger symbol for the operator with the lower binding power.
• Surround the operators with the lower binding power with more space than those with a higher binding power. E.g.,
p ∧ q ⇒ r ≡ p ⇒ (q ⇒ r )
is safely readable without knowing that ∧ ⇒ ≡ is the order of decreasing binding power. This spacing is a vital visual aid to parsing and the fact that nowadays it is violated in many publications means that these publications do a disservice to the propagation of formal techniques. (The visual aid is vital because the mathematician does not do string manipulation but manipulation of parsed formulae: when substituting equals for equals, identifying subexpressions is essential.)
• For unary operators, give them the highest binding power and stick to prefix operators.
• For the relation/predicate calculus we settled on the following order of decreasing binding power
¬ 
~ 

(negation, relational converse) 
; 


(relational composition) 
∧ 
∨ 

(conjunction, disjunction) 
⇒ 
⇐ 

(implication, consequence 
≡ 


(equivalence) 
As time went on, I learned to appreciate expressions built with operators as a way of avoiding functional notation. We can write the difference a−b as dif.(a,b) or exc.(b,a), where min and exc are functions of an ordered pair. (I believe that the notion of "function of 2 arguments" is now obsolete.) But we can also write the "curried" versions (min.a).b and (sub.b).a in which , for instance, sub is a higherorder function such that sub.b decreases its argument by b (so that sub.(−1) would be the successor function). Functions dif, exc, min and sub are different functions and as soon as the operation of functional composition enters the game, the distinctions are essential. But as long as we don't do functional composition, the choice between the four options is irrelevant and writing the expression a−b is a lovely way of avoiding being overspecific. (Not making superfluous distinctions should always be encouraged; it is bad enough that we don't have a canonical representation for the unordered pair.)
3½ 3y 32 .
Is it a wonder that little children (many of whom have a most systematic mind) get confused by the mathematics they are taught? One would like the little kids to spend their time on learning the techniques of effective thought, but regrettably they spend a lot of it on familiarizing themselves with odd, irregular notational conventions whose wide adoption is their only virtue.
The much heavier price is that the invisible multiplication all but rules out the introduction of multipleletter identifiers, thus creating the need of symbols of other alphabets (which —and Whitehead should have known that!— significantly contributed to the pain of typing mathematics). And when the multipleletter identifiers could no longer be avoided, they were admitted at the price of ambiguity, as
sin (s + i + n)
illustrates.
Remark I also think that Whitehead made another error of judgement. Brevity is much more effectively obtained by macroscopic measures such as avoiding duplication, case analysis and superfluous nomenclature, than by such microscopic measures as making the multiplication invisible. (End of Remark.)
I now avoid invisible infix operators almost entirely. I do remember a few texts dealing with theorems about strings in which concatenation was denoted by juxtaposition. I could afford that because at the beginning I had declared the types of my oneletter variables: x, y, z were of type character, X, Y, Z were of type (possibly empty) character string: in xX, x would stand for the leading character of the string xX.
The most farreaching consequence is the introduction of a visible infix operator for function application. I have given it the highest binding power and therefore I have chosen the smallest symbol I could think of: the infix dot "." . So, instead of the traditional f (x) I now write f.x . I have started doing this very tentatively in 1984; I have stuck to the convention and I see more and more people adopting it. One of its attractions is the way in which it caters for λabstraction: in 1973 I wrote "wp(S,R)" for the weakest precondition such that statement S establishes postcondition R, but wp.S.R is much more attractive, wp.S now being the predicate transformer associated with statement S. Note that we have chosen the function application dot to be left associative: wp.S.R is short for (wp.S).R .
Remark The convention that function application is leftassociative has been adopted almost universally. Note that the parentheses then necessary in
f.(g.x)
can be eliminated by writing the above as
f◦g . x
and postulating that functional composition has a greater binding power than functional application. Please note that
f◦g◦h . x
is semantically unambiguous, functional composition being associative. (End of Remark.)
Quantification
I had three major desires with respect to quantification, (i) unambiguous identification of the dummy, (ii) clear delineation of the scope, and (iii) range as a uniform ingredient.
ad(i) The need for unambiguous dummy identification becomes clear when we consider the list of sets, which starts with the set of the first 10 squares:
{ i ^{2}  i <10 }, { i ^{3}  i <10 }, { i ^{n}  i < 10 }, { i ^{n}  i < n }
where {i ^{i+1}, i ^{i+2}, i ^{i+3}, .... } would be a possible interpretation of the last set.
ad(2) It is already an ambiguity with the traditional summation; compare
3 




3 



3 



3 

∑ 
n^{2} 
, 

1 + 
∑ 
n^{2} 
, 

∑ 
n^{2} + 1 
, 

∑ 
1 +n^{2} 
n=1 




n=1 



n=1 



n=1 

possible interpretations being, in order, 14, 15, 15 or 17, 17 or 3+n^{2} . But even logicians write
∀x P(x) ∧ Q
without making clear whether they mean
(∀x P(x)) ∧ Q or (∀x P(x) ∧ Q)
which differ if the range for x is empty.
ad(3) Although the properties of the underlying (symmetric and associative) operators may differ —addition and multiplication are not idempotent and maximum and minimum may lack a neutral element— we would like a uniform format. There is, for instance, no reason why summation should have a dummy ranging over consecutive integers.
The format is based on our format for set notation. The set that we formerly described as
{ i ^{2}  i < 10 }
is denoted by
〈 i : i < 10 : i ^{2 }〉
where "i" is the dummy —if there are more dummies, we separate them by commas—, "i < 10" is the range and "i ^{2}" is the term. The semicolons around the range are only separators, the "angle brackets" delineate the scope of the dummies. The explicit enumeration of the dummies between 〈 and the first : acts like ALGOL 60's declaration of the local variables of an inner block. The convention enables us to distinguish between
〈 i : i < n : i ^{n }〉 , 〈 n : i < n : i ^{n }〉 and 〈 i,n : i < n : i ^{n }〉 ;
The last one is the set of all powers for which the exponent exceeds the base, the first two are subsets thereof.
In ALGOL 60, the declaration of a local variable includes the type of that variable, and I see no logical objection against adopting that convention: we could have written
〈 i ∈ℕ : i < 10 : i ^{2}〉 ,
but we have never done so: I have always found it preferable to supply such information in the surrounding text.
Remark It took many years before I introduced the angle brackets 〈 〉 ; all that time I used the standard parentheses ( ) . The transition to angle brackets for scope delineation was a great improvement. (End of Remark).
When a quantified operator is applied to the set
〈 i : r.i : t.i 〉 ,
we write it just after the opening angle bracket:
〈∑ i : r.i : t.i 〉 , 〈∏ i : r.i : t.i 〉 , 〈∀ i : r.i : t.i 〉 , 〈∃ i : r.i : t.i 〉 ,
〈↑ i : r.i : t.i 〉 and 〈↓ i : r.i : t.i 〉 .
For the first two, the type of the term t.i must admit addition and multiplication, for the next two, universal and existential quantification respectively, the type of the term t.i had better be Boolean, while for the supremum and the infimum the surrounding text had better specify the partial order with respect to which these extremes have been defined.
From a logical point of view, universal and existential quantification don't need a variable range parameter since it can be absorbed in the term:
〈∀ i : r.i : t.i 〉 ≡ 〈∀ i : true : r.i ⇒ t.i 〉
〈∃ i : r.i : t.i 〉 ≡ 〈∃ i : true : r.i ∧ t.i〉
But the range parameter allows more elegant formulae, such as the defining property of the supremum
〈↑ i : r.i : k.i 〉 ⊑ z ≡ 〈∀ i : r.i : k.i ⊑ z 〉
The explicit range parameter is also welcome from a practical point of view. During many manipulations, the range can remain constant, as is for instance illustrated by de Morgan's Law
¬〈∀ i : r.i : t.i 〉 ≡ 〈∃ i : r.i : ¬t.i 〉
and we shall show below the notational exploitation of such range constancy.
The proof format
When, for transitive → , we conclude A → C from A → B and B → C , we wish for brevity's sake to write down the intermediate result B only once. We therefore present the calculation in the following format

A 

→ 

{hint why A → B} 

B 

→ 

{hint why B → C} 

C 

We shall return to the role of the hints later; we now only report that it is absolutely essential that at least one line is available for each hint, so as to discourage economizing on them.
Another, purely editorial way of reducing duplication is declaring something, once and for all, to hold for all intermediate results of a calculation rather then repeating it each time. We do this for the type specification of variables and the range of dummies. This is a special case of "embedding the calculation in a context". To illustrate some of these matters, let me show a few ways of proving the following the following simple
Theorem 0. For associative • , we have for all x, y, z
x • y = y ∧ y • z = z ⇒ x • z = z
Proof 0. This proof uses Leibniz's Principle in the form
p = q ∧ f.p ⇒ f.q
and has the structure of a weakening chain of boolean expressions.
We prove Theorem 0 by observing for any x, y, z and associative •

x • y = y ∧ y • z = z 
≡ 
{ predicate calculus } 

y • z = z ∧ x • y = y ∧ y • z = z 
⇒ 
{ Leibniz } 

y • z = z ∧ (x • y ) •z = z 
≡ 
{ • associative } 

y • z = z ∧ x • (y • z) = z 
⇒ 
{ Leibniz } 

x • z = z 
Here the calculation is embedded in the context of • being associative, a proof shape that is suggested by the formulation of theorem 0.
Proof 1 This proof uses Leibniz's principle in the form
p = q ⇒ f.p = f.q
We prove Theorem 0 by observing for associative • and x, y, z satisfying the antecedent

x • z 
= 
{ y • z = z from antecedent } 

x • (y • z) 
= 
{ • associative} 

(x • y ) • z) 
= 
{ x • y = y from antecedent } 

y • z 
= 
{ y • z = z from antecedent } 

z 
In proof 1, we have been very —one could argue: too !— explicit in our hints: we could have started with
x •z
= { antecedent }
x • (y • z )
because the observed equality is obviously justified by y • z = z , which fortunately is one of the conjuncts of the antecedent. But personally I am in favour of making the hints as clear and helpful as possible. And in the style of Proof 1 we can afford it, for we have embedded our calculation in a more elaborate context —viz. that of the antecedent— from which the hint selects a conjunct only when it is needed. This is more concise than the style of proof 0, in which conjuncts —e.g. y • z = z— are dragged along as long as they are needed. In the next example we'll show another way of how "context" can be used to avoid repetition of the same subexpression.
We recall the defining property of the supremum ↑ with respect to the complete partial order ⊑:
〈↑ i : r.i : k.i〉⊑ z ≡ 〈∀i : r.i : k.i ⊑ z 〉 for all z
Part of the Theorem of KnasterTarski states that with h defined by
h = 〈↑ y : y ⊑ f.y : y 〉
we have
h ⊑ f.h
if f is monotonic with respect to ⊑ , i.e.,
p ⊑ q ⇒ f.p ⊑ f.q for all p, q .
(In another language: "fapplication is ⊑ preserving".)
Proof In this proof y ⊑ f.y is understood to be the range of the dummy y.
To begin with we conclude from the definitions of ↑ and h that h's defining property is that
(0) h ⊑z ≡ 〈∀y :: y ⊑z 〉 for all z .
And now we observe

h ⊑ f.h 
≡ 
{ (0) with z := f.h } 

〈∀y :: y ⊑ f.h 〉 
⇐ 
{ ⊑ transitive ; ∀ monotonic } 

〈∀y :: ⊑ f.y ∧ f.y ⊑ f.h 〉 
≡ 
{∀ distributes over ∧} 

〈∀y :: y ⊑ f.y 〉 ∧ 〈∀y :: f.y ⊑ f.h 〉 
≡ 
{ range is y ⊑ f.y, predicate calculus } 

〈∀y :: f.y ⊑ f.h 〉 
⇐ 
{ f monotonic; ∀ monotonic } 

〈∀y :: y ⊑ h 〉 
≡ 
{ (0) with z := h } 

h ⊑ h 
≡ 
{ ⊑ reflexive } 

true 
Remark As an aside I would like to point out that the second step, which strengthens
y ⊑ f.h
to
y ⊑ f.y ∧ f.y ⊑ f.h
is absolutely standard. In the original relation the operands differ in two respects: y versus h and the number of fapplications, in the strengthened version each of the differences has been localized in one of the conjuncts, so that they can be dealt with separately. We could have tried the separation the other way round
y ⊑ h ∧ h ⊑ f.h
but as that choice reintroduces the original poof obligation it is not helpful.
(End of Remark)
The role of the hints
With suitable formalization, the hints would fully define the manipulations, and we could omit all the intermediate results, as they would follow. Clearly we have not done so; we consider the intermediate results an essential ingredient of the proof since it is the "intermediate" result that indicates whether we are done or, if not, suggests what to do next.
Our hints were intended to be helpful, and as time went by, we made up our mind how we wanted to help the reader. The most important property of the hint became that it restrict and delineate the search space where the justification should be found. So, if the hint is
{predicate calculus} ,
then this means that the rules of the predicate calculus suffice. When anything beyond that is needed, it is something, a rule or a property , from the context in which the calculation is embedded; in that case the hint should identify that context element uniquely. For this purpose we commonly number formulae (like "(0)" in the last example).
Remark For the formula number's place the left margin is to be preferred over the right margin, because then it is easier to maintain a small distance between the number and the formula it numbers. (A similar remark applies to page numbers in tables of contents.)
(End of Remark.)
In the hints, in our last example, that referred to (0), we gave the instantiations —"z := f.h"and "z := h" respectively— though in a simple example like this it is perhaps a little bit overdone. As soon as the pattern matching might become a problem, however, the instantiation is really helpful and we therefore don't omit it: our texts should not pose puzzles to the reader.
To save space we sometimes combine two manipulations within a single step. We do not hesitate to do so in the case of independent commuting operations on disjoint subexpressions of the intermediate result. We never combine nested substitutions, for that would be asking for trouble. For such microscopic space savings, the general advice is "In dubio abstine."; the space savings that can be obtained by proper proof structure —such as effective disentanglement and avoided case analyses— are greater and intellectually more satisfying.
Overloading and an unsolved dilemma
Derivation distributes over addition, i.e.,
Usually we don't consider this an example of overloading, but if x+y stands for a speed and t is time, than the + at the righthand side adds accelerations. Yet we don't feel obliged to introduce two different + signs and to write something like
primarily because the absence of a notational distinction between the two additions did not introduce any ambiguity.
Let now x and y be two functions which, when applied to t yield two addable values. Then it is customary to define the function that is denoted by x+y by
(x+y ).t = x.t + y.t for all t,
Note that, formally, ".t " now distributes (to the left) over + . (In our former example the distribution of d/dt was "to the right", so we are still on reasonably familiar ground.)
But now the question arises what meaning to ascribe to x = y . The traditional interpretation is that x = y is a boolean expression stating that x and y are the same function, i.e.,
x = y ≡ 〈 ∀t :: x.t = y.t 〉
(Here we have used ≡ for equality between boolean operands.) But in analogy to our previous example x = y could also be interpreted as a boolean function given by
(1) (x = y ).t ≡ x.t = y.t for all t ,
i.e., the boolean function that yields true wherever x and y coincide, and false everywhere else.
In many of my writings I have chosen interpretation (1). In addition I have chosen to use a pair of square brackets to denote for a boolean function universal quantification over its domain:
(2) [b] ≡ 〈 ∀t :: b.t 〉
The great advantage of the square brackets is that one does not need to introduce a dummy argument. And now one proceeds

( x and y are the same function ) 
≡ 
{ definition of the functional equality } 

〈 ∀t :: x.t = y.t 〉 
≡ 
{ (1) } 

〈 ∀t :: (x = y ).t 〉 
≡ 
{ (2) with b := x = y } 

[x = y ] ; 
the annoying moral of the story is that to express what we know and appreciate as plain and honesttoGod equality may require an extra pair of square brackets. All this is not very satisfactory, but I don't know enough of type theory to try to improve the scene.
prof. dr. Edsger W. Dijkstra
Department of Computer Sciences
The University of Texas at Austin
Austin, TX 78712–1188
USA
transcribed by Mario Béland and Hamilton Richards
revised Mon, 6 Dec 2010