Now with short circuiting and/or but at the cost of some parser issues.  For now use and/or and avoid &&/||, bit twiddling with ||| and &&& will be broken until this is fixed.

Signed-off-by: Rick Minerich <richard.minerich@gmail.com>
as a cheap workaround I have now made a space after && and || part of the syntax.  This will allow me to avoid major parser changes while avoiding most reverse compatibility issues.

Signed-off-by: Rick Minerich <richard.minerich@gmail.com>