After seeing a handful of failed tests, I have realized that the Dao language had an ambiguity: The
'Dao.Object.AST.AST_MetaEval' brackets #{ }# might immediately follow an ordinary closing brace of
any other expression, for example:
	if(a == 1) { print("Hello"); }
	#{ global b = a; }
If you were to write this on a single line, it could be written like so:
	if(a == 1) { print("Hello"); }#{ global b = a; }
Now, the token "}" is immediately followed by "#{", which means the tokenizer should tokenize it
like this:
	["}, "#{"]
but the tokenizer must always tokenize longer key strings before shorter key strings, so the
tokenizer would naturally tokenize it like
this:
	["}#", "{"]
and this sequence of tokens would of course fail during syntactic analysis. To fix this problem, I
have changed the 'Dao.Object.AST.AST_MetaEval' brackets to {# #}, for example:
	{# global b = a; #}
This syntax cannot result in ambiguity with any other syntactically valid Dao language expression.
As I write this, the automated test program is running and has randomly generated over 900000
syntactically correct Dao language expressions and every one of them has been parsed without an
error.
I have added another parameter to the test configuration to enable or disable the equality test in parser test. The equality test checks whether the object emitted by the parser is identical to the randomly generated test object. At first I was more interested in just checking whether or not the parser could parse arbitrary syntactically correct expressions. But now I am more interested in checking the correctness of the parser, so creating this option seemed to be a good idea.