Add more documentation

Also, changed my mind on the way DiePool and its implementations should
be structured. The implementations go in the die pool file as internal
classes, because nobody should particularly care the specifics about
their die pool, only that it does what it says it should

1 files changed, 15 insertions, 1 deletions

diff --git a/dice/src/example/java/bjc/dicelang/neodice/statements/ArrayStatementValue.java b/dice/src/example/java/bjc/dicelang/neodice/statements/ArrayStatementValue.java
index 66e14ad..1a54ca5 100644
--- a/dice/src/example/java/bjc/dicelang/neodice/statements/ArrayStatementValue.java
+++ b/dice/src/example/java/bjc/dicelang/neodice/statements/ArrayStatementValue.java
@@ -4,10 +4,24 @@ import static bjc.dicelang.neodice.statements.StatementValue.Type.*;
 
 import java.util.*;
 
+/**
+ * A statement value which represents an array of statement values.
+ * @author Ben Culkin
+ *
+ * @param <ElementType> The contained type of value.
+ */
 public class ArrayStatementValue<ElementType extends StatementValue> extends StatementValue {
-	public final Type          elementType;
+    /** The type of the contained values. */
+    public final Type          elementType;
+    /** The contained values. */
 	public final ElementType[] values;
 	
+	/**
+	 * Create a new array statement value.
+	 * 
+	 * @param elementType The type of the contained values.
+	 * @param values The contained values.
+	 */
 	@SafeVarargs
 	public ArrayStatementValue(Type elementType, ElementType... values) {
 		super(ARRAY);