GitLab

 - Implemented new test for checking integer boundaries
 - checkTokenInteger documented
 - indentation fixed in parser.yy
 - integer check in lexer.ll extended from int to int64_t
 - a bug fixed in EvalContext::convertUint32
 - User's Guide now explicitly mentions network order

 - User's Guide clearified couple things.
 - messages orded alphabetically
 - indentation increased in parser.yy
 - debugging message formats updated slightly ('1234' => 0x1234)
 - one new case in vendorClass4SpecificVendorData added
 - verbose_ flag in log_utils.h commented

The debug output was modified to output text strings using
single quotes instead of double quotes but the document missed
getting this update.

    Minor corrections to doc/guide/classify.xml

Create a LogContentTest class and move the functions to manipulate
a test to check on the log output there.  This will make it available
for other tests in the future.  As part of this bundle a bit more
work into the class to minimze the calls in the test routines.

Where reasonable remove extra copys of the values being pushed
onto the stack - instead of generating a copy just for the logging
simply use the value from the top of the stack directly.

Swtich to using single quotes around text values.

Added some more description in the classify document

This patch adds a set of log messages to indicate what values are
being popped from or pushed to the classification value stack.  This
is meant to be used by an administrator when debugging the expression
statements.

also added a couple commas or missing spaces