Add type details to AST tree Token.content.Value nodes.

[Matthewar]

In order for useful type matching details when coding the parser and the execution engine (#6 and #7), further details should be added to Token.content.Value nodes to explain expected and allowed types for each use case.

[Matthewar]

Need to also add type syntax details to wiki:

Values

• Integer: Any number of 0..9
• Floating: Any number made of 0..9 with a period in it e.g. 123.456
• Character: A single letter encapsulated in apostrophes e.g. 'a'
• Boolean: The word true or false with a capital first letter e.g. True

  Literal

• A string is maximum 255 characters, contained in quotation marks e.g. "word"

[sighellan]

The database structure has int, float, string, bool and byte. So no char, but includes byte. This will need to be resolved.

[Matthewar]

Alright, I'll go over that later.

[Matthewar]

Char now removed, forgot byte from my list:

Values

• Integer: Any number of 0..9
• Floating: Any number made of 0..9 with a period in it e.g. 123.456
• Byte: 8 bit unsigned integer, written as a number with a 'B' suffix e.g. 25B
• Boolean: The word true or false with a capital first letter e.g. True

  Literal

• A string is maximum 255 characters, contained in quotation marks e.g. "word"