GitLab

This improves performance on the test.yaml attached to #158 by about
25% on my machine as compared to the previous commit (0.25s -> 0.20s),
as measured by `time build/util/parse < test.yaml > /dev/null`.

This improves performance on the test.yaml attached to #158 by about
35% on my machine (0.39s -> 0.25s), as measured by
`time build/util/parse < test.yaml > /dev/null`.

Switched the 'pragma once' to only happen on MSVC, or gcc >= 3.4 (it was causing trouble on the sun compiler)

Flipped the include guard and the pragma, and don't use the pragma for early versions of gcc (< 3.4)

Added Anchor() regex (so that we're not just using Alphanumeric to match anchors), but it's still not 100% right (it shouldn't allow non-printable characters, e.g.). Also fixed a test that was broken along these lines (if a colon immediately follows an anchor, it's part of the anchor)

Switched to reading the entire file into a buffer at the start.\nThis speeds it up a TON (like 100x).

Added CMake scripts for other platforms\nFixed some bugs that gcc complained about\nFixed CR/LF vs LF bug

Updated some of the character-in-scalar rules.

Moved the input stream, together with line/column info, into its own class, which allowed some other stuff just to pass the stream, and not have to be a member of Scanner.

No commit message

Refactored some common whitespace-parsing code in scanning both scalars.
Implemented the flow collection tokens.

Split off the specific regular expressions, and the specialized token-scanning functions, into their own files.

Added stream input to the regular expressions, greatly simplifying the usage (in particular, we no longer have to specify the number of characters to be checked).

Wrote a simplified regular expression parser to make life easier (it only does single matches; i.e., no one-or-more matches, etc.).
Fixed some of the whitespace/line break matching.

Also messed around with multiple character peeking on the input, and got something working.

We're now using exceptions for errors, and scanning/pushing tokens is exception-safe (using a set of "limbo tokens").