Refactor front-end error-handling

This refactors the front-end to use a tree for capturing errors, instead
of throwing exceptions.

This has the benefit that you will receive notifications about all of
the error messages you have, instead of only the first.

I'm a bit fuzzy on the details, since it's been a while since I wrote
these changes.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/main/java/bjc/rgens/parser/RegexRuleCase.java b/src/main/java/bjc/rgens/parser/RegexRuleCase.java
index 3c57489..1712d57 100755
--- a/src/main/java/bjc/rgens/parser/RegexRuleCase.java
+++ b/src/main/java/bjc/rgens/parser/RegexRuleCase.java
@@ -1,8 +1,8 @@
 package bjc.rgens.parser;
 
 import bjc.rgens.parser.elements.CaseElement;
-import bjc.utils.funcdata.IList;
 
+import java.util.List;
 import java.util.regex.Pattern;
 import java.util.regex.PatternSyntaxException;
 
@@ -12,7 +12,7 @@ import java.util.regex.PatternSyntaxException;
  * Actually implement this
  */
 public class RegexRuleCase extends RuleCase {
-	public RegexRuleCase(IList<CaseElement> elements) {
+	public RegexRuleCase(List<CaseElement> elements) {
 		super(elements);
 
 	}
@@ -21,7 +21,7 @@ public class RegexRuleCase extends RuleCase {
 
 	}
 
-	public RegexRuleCase withElements(IList<CaseElement> elements) {
+	public RegexRuleCase withElements(List<CaseElement> elements) {
 		return new RegexRuleCase(elements);
 	}
 }