Tokenizer Evolution

Added object key, and array data token matchers

JSNative.Tokenizer.Expression = function(regularExpression, name, readAhead)

regularExpression may be Object, RegExp, or String[] but not String

readAhead may be RegExp, Number, or String but not String[] or Object

The usage case here is that your read/scan/seek should be a single case constant or character class. Your "regularExpression" can match RegExp, match Object keys, or match Array words.

I certainly have not thought of everything, or enabled "every feature, for every feature" I have not much tested the algorithm, but it works for general purpose use, and any feature not implemented could be implemented through the custom callback function.

Modified: core.js
Tokenizer Doc updates

Modified: core.js
JSNative.Class define constructor methods 'hidden'

Its too cumbersome to "hide" these individually on every class constructor that does not want them exposed in a property enumeration, so the default is now "hidden"

Modified: bin/buildnum
Modified: src/JSNative/JSNativeClass.js
Redundant code purge..

Syncs core with previous commit changes

Modified: core.js
Installed: JSNative.Tokenizer

Modified: bin/buildnum
Modified: core.js
Modified: src/JSNative/JSNative.js
Relocated api type codes

Modified: core.js
Modified: src/JSNative/JSNativeType.js
Synchronized api type codes

Modified: bin/buildnum
Modified: src/JSNative.c
Fixed logic error

match must be created from expression :/

Modified: bin/buildnum
Modified: src/JSNative/JSNative.js
Updated the Tokenizer interface

renamed Tokenizer.matchReadAhead --> Tokenizer.readAhead

Tokenizer.readAhead defaults to 1 (pseudo getChar())

Modified: bin/buildnum
Modified: src/JSNative/JSNative.js
New Declaration Parser

Pushing for compliance!

Modified: core.js