Don't parse 1|2 as real literal.
Merge pull request #254 from Ventero/real-literal

Don't parse 1|2 as real literal.
Added more complex high-level tests.

Those test a broad spectrum of features and implementation details and
can be considered more of integration tests than anything else.

I added two sets of tests here: One consisting of my own code golf
solutions from codegolf.stackexchange.com. Those should provide a good
stress test for the parser and corner cases of the langage. Secondly I
added snippets I wrote for rosettacode.org that each showcase how to
approach a particular problem or how to use a specific language
feature. Those can probably be more of a metric what parts are still
missing to make Pash more useful in the real world (at least when used
as a programming and scripting language).
Merge pull request #255 from ygra/complex-tests

Added more complex high-level tests.
BUGFIX: Print table without columns
BUGFIX: Format-List threw exception with empty objects
Reworked arithmetic operations

Arithmetic operations are now done in their native datatype and only
casted if an overflow happens. This leads to better precision in results.
Also, hex strings are now allowed to have a sign (+ or -) if (and only if) they are
used in arithmetic opertations.
Made tests explicit where PS breaks its own specification
REFACTOR: code for division is easier to understand
Try more datatypes for numeric conversion
Merge pull request #256 from sburnicki/print_empty_psobj

BUGFIX: Print table without columns
Merge pull request #257 from sburnicki/arithmetic_fix

FIX: Correct arithmetic operations
[BUGFIX] Fixed an assertion that was deprecated in NUnit.
[BUGFIX] Fixed one of the new integration tests.

Write-Host is completely unavailable here.
Merge pull request #259 from ygra/integration-test-fix

Fixed an error in one of the new integration tests.
Merge pull request #258 from ygra/ast-test-fix

Fixed an assertion that was deprecated in NUnit.
Fixed class name for ConvertTo-Csv.
Worked around the failing CSV tests for PSv4 for now.

PowerShell's CSV parsing got a bit more lenient starting in v3 (which
isn't a bad thing – the two cases that failed here were things I
wouldn't really want as a user). Either we follow suit or ignore the
cases for now, but constantly-failing reference tests are a nuisance
for CI. And by now it's hard to come by machines with only PSv2.

Eventually the tests need a bit restructuring as well, I guess.
Currently it's a bit messy figuring out why a given test fails.
Merge pull request #260 from ygra/csv-tests

Workaround for the failing CSV tests on PowerShell v3+
Rearrange integer literal tests and add some new testcases.

This moves the integer literal tests to the AST tests, which has the
advantage of not requiring a TestHost just to parse a constant
expression.