Skip to content

Commit 2d99962

Browse files
committed
Few style fixes
- Change 'We denote X = Y' to 'Let A be Y' (suggested in WebAssembly#180 (comment)) - Remove uses of 'we' pronouns (suggested in WebAssembly#180 (comment))
1 parent b7cf92c commit 2d99962

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

document/core/exec/runtime.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -554,7 +554,7 @@ If there is no :ref:`tag address <syntax-tagaddr>`, the instructions of that tar
554554
555555
Intuitively, for each target :math:`\{\tagaddr^?~\instr^\ast\}` of a |CATCHadm|, :math:`\instr^\ast` is the *continuation* to execute
556556
when the handler catches a thrown exception with tag |tagaddr|, or for any exception, when a target specifies no tag address.
557-
In that case, we say that the exception is handled by the exception handler |CATCHadm|.
557+
In that case, the exception is handled by the exception handler |CATCHadm|.
558558
If this list of targets is empty, or if the tag address of the thrown exception is not in the handler's mapping and there is no |CATCHALL| clause, then the exception will be rethrown.
559559

560560
.. todo::
@@ -679,7 +679,7 @@ In order to specify the reduction of :ref:`branches <syntax-instr-control>`, the
679679
680680
This definition allows to index active labels surrounding a :ref:`branch <syntax-br>` or :ref:`return <syntax-return>` instruction.
681681

682-
In order to be able to break jumping over exception handlers and caught exceptions, we must allow for these new structured administrative control instructions to appear after labels in block contexts, by extending block context as follows.
682+
In order to be able to break jumping over exception handlers and caught exceptions, these new structured administrative control instructions are allowed to appear after labels in block contexts, by extending block context as follows.
683683

684684
.. math::
685685
\begin{array}{llll}
@@ -741,7 +741,7 @@ Throw contexts allow matching the program context around a throw instruction up
741741
\stepto & S;~F;~\LABEL_m\{\} (\CATCHadm\{a~\RETURN\}~\val^n~(\THROW~x)~\END)~\END \\
742742
\end{array}
743743
744-
We denote :math:`\val^n = \val^{n-m} \val^m`.
744+
Let :math:`\val^n` be :math:`\val^{n-m} \val^m`.
745745
:ref:`Handling the thrown exception <exec-throwadm>` with tag address :math:`a` in the throw context
746746
:math:`T=[val^{n-m}\_]`, with the exception handler :math:`H=\CATCHadm\{a~\RETURN\}` gives:
747747

@@ -752,11 +752,11 @@ Throw contexts allow matching the program context around a throw instruction up
752752
\end{array}
753753
754754
755+
When a throw of the form :math:`val^m (\THROWadm~a)` occurs, search for the maximal surrounding throw context :math:`T` is performed,
756+
which means any other values, labels, frames, and |CAUGHTadm| instructions surrounding the throw :math:`val^m (\THROWadm~a)` are popped,
757+
until an exception handler (corresponding to a try block) that :ref:`handles the exception <syntax-handler>` is found.
758+
Then the values :math:`val^m:[t^m]` are appended to the tag address :math:`a` into a new |CAUGHTadm| instruction, which is pushed onto the stack.
755759

756-
When a throw of the form :math:`val^m (\THROWadm~a)` occurs, we search for the maximal surrounding throw context :math:`T`,
757-
which means we pop any other values, labels, frames, and |CAUGHTadm| instructions surrounding the throw :math:`val^m (\THROWadm~a)`,
758-
until we find an exception handler (corresponding to a try block) that :ref:`handles the exception <syntax-handler>`.
759-
We then append the values :math:`val^m:[t^m]` to the tag address :math:`a` into a new |CAUGHTadm| instruction which we push on the stack.
760760

761761
In other words, when a throw occurs, normal execution halts and exceptional execution begins, until the throw
762762
is the continuation (i.e., in the place of a :math:`\_`) of a throw context in a catching try block.

0 commit comments

Comments
 (0)