From d8aade895eac0d1c971825f1e46e868568053bd3 Mon Sep 17 00:00:00 2001 From: bculkin2442 Date: Fri, 17 Jan 2020 18:49:35 -0500 Subject: Fix GroupDecree tokenizer bug When we were processing a nested closing decree, we were forgetting to add it to the current clause, thus causing confusion when someone later tried to parse that clause and missed their ending token. --- clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java | 2 ++ 1 file changed, 2 insertions(+) (limited to 'clformat/src/main/java/bjc') diff --git a/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java b/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java index d2ccfd2..1b9c90f 100644 --- a/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java +++ b/clformat/src/main/java/bjc/utils/ioutils/format/CLTokenizer.java @@ -231,6 +231,8 @@ public class CLTokenizer implements Iterator { } else if (curDecree.isNamed(desiredClosing)) { // Unnest nestingLevel -= 1; + + curClause.addChild(curDecree); } else { curClause.addChild(curDecree); } -- cgit v1.2.3