From ebe9a40baf270d657e451586492f512d41585dde Mon Sep 17 00:00:00 2001 From: NeilBrown Date: Sat, 20 Apr 2019 14:57:21 +1000 Subject: [PATCH] oceani: fix a couple of typos. There is always one more typo... Signed-off-by: NeilBrown --- csrc/oceani.mdc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/csrc/oceani.mdc b/csrc/oceani.mdc index 4f39775..3fd4d74 100644 --- a/csrc/oceani.mdc +++ b/csrc/oceani.mdc @@ -73,7 +73,7 @@ out the program from the parsed internal structure. This is useful for validating the parsing. So the main requirements of the interpreter are: -- Parse the program, possible with tracing +- Parse the program, possibly with tracing - Analyse the parsed program to ensure consistency - print the program - execute the program @@ -337,7 +337,7 @@ element where its type was set. For now we will assume that each line of an error message indicates one location in the file, and up to 2 types. So we provide a `printf`-like function which takes a format, a language (a `struct exec` which has not yet been introduced), and 2 -types. "`$1`" reports the first type, "`$2`" reports the second. We +types. "`%1`" reports the first type, "`%2`" reports the second. We will need a function to print the location, once we know how that is stored. As will be explained later, there are sometimes extra rules for type matching and they might affect error messages, we need to pass those -- 2.43.0