[bugfix] Digits were not being handled.

Author: ross-spencer

doc.go

@@ -1,10 +1,10 @@
 /*
 Package kvalscanner implements a basic lexical scanner for KVAL (Key Value
-Access Language). The language has been created for more fluid access to 
-Key-Value-like databases such as the popular BoltDb. 
+Access Language). The language has been created for more fluid access to
+Key-Value-like databases such as the popular BoltDb.
 
 Parsers can access a new Scanner() to check that a user provided string is
-valid according to the language's specification. For Golang, however, this 
+valid according to the language's specification. For Golang, however, this
 work is already done for you at http://github.com/kval-access-language/kval-parse
 
 The most up-to-date specification for KVAL can be found here:

kval-scanner.go

@@ -55,6 +55,9 @@ func (s *Scanner) Scan() (tok Token, lit string) {
 	} else if isLetter(ch) {
 		s.unread()
 		return s.scanLiteral()
+	} else if isDigit(ch) {
+		s.unread()
+		return s.scanLiteral()
 	}
 
 	// Otherwise read the individual character.

kval-scanner_test.go

@@ -38,7 +38,7 @@ func TestScan(t *testing.T) {
 
 // Test a range of literals that should be allowed by the library
 func TestValidLiterals(t *testing.T) {
-	var lits = []string{"āēīōūĀĒĪŌŪ", ">>>", "/)(*&^%$#@!>:!@#", "abc123", "子：？"}
+	var lits = []string{"āēīōūĀĒĪŌŪ", ">>>", "/)(*&^%$#@!>:!@#", "abc123", "子：？", "200"}
 	for _, s := range lits {
 		s := NewScanner(strings.NewReader(s))
 		var tok Token

kval-token.go

@@ -29,6 +29,31 @@ const (
 	REGEX // Regular expression, REGEX: {PATT} ANy regex pattern inside OPATT and CPATT
 )
 
+var ErrorLookup = map[Token]string{
+	ILLEGAL: "ILLEGAL",
+	EOF:     "EOF",        // Spacial token, EOF: Token signals the end of input
+	WS:      "WHITESPACE", // Spacial token, WS: Token signals whitespace has been found
+
+	LITERAL: "LITERAL", // LITERAL: String literal discovered
+
+	BUCKEY: "BUCKET >>>> KEY",  // Other operator, BUCKKEY: >>>> Bucket to Key syntax for KVAL
+	BUCBUC: "BUCKET >> BUCKET", // Other operator, BUCBUC: >> Bucket to Bucket syntax for KVAL
+	KEYVAL: "KEY :: VALUE",     // Other operator, KEYVALL :: Key to Value syntax for KVAL
+	ASSIGN: "ASSIGNMENT",       // Other operator, ASSIGN: => Assignment operator for KVAL renames
+
+	USCORE: "UNDERSCORE",          // Single character operator, USCORE: _ Return unknown Key or Value
+	OPATT:  "OPEN REGEX PATTERN",  // Single character operator, OPATT: { Open a regular expression pattern
+	CPATT:  "CLOSE REGEX PATTERN", // Single character operator, COATT: } Close a regular expression pattern
+
+	INS: "INSERT KEYWORD", // Keyword, INS: Insert capability of KVAL
+	GET: "GET KEYWORD",    // Keyword, GET: Get capability of KVAL
+	LIS: "LIS KEYWORD",    // Keyword, LIS: LIS capability of KVAL
+	DEL: "DEL KEYWORD",    // Keyword, DEL: Delete capability of KVAL
+	REN: "REN KEYWORD",    // Keyword, REN: Rename capability of KVAL
+
+	REGEX: "REGEX PATTERN", // Regular expression, REGEX: {PATT} ANy regex pattern inside OPATT and CPATT
+}
+
 // Mapped values exported for KVAL Parser to verify keywords
 // Lookup 'LIT' value in KeyWordMap and if found we have a KVAL key word,
 // e.g. INS, GET, LIS, REN, DEL. If used correctly this map will help a parser