GitLab

Switched from loading test files to testing specific parsing constructs. The tests don't fully cover the span (eventually I'll add more, maybe), but there's a bunch there.
More to the point, the yaml-reader program doesn't do any file IO, so it doesn't require a specific working directory.

Removed throw() specifier in Exception (I don't remember putting it in). This may solve a gcc error (I haven't tested it yet) or it may break it further.

(Thanks to Vadim Zeitlin)

No commit message

We were getting memory leaks (as told by the CRT detectors, which I also added), and there's really no reason (as long as we're careful) to use pointers there.

Removed the (unused) 'required' flag from simple keys (the parser should take care of this, not the scanner).

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.

There's a bug (and question): should we test simple keys' validity BEFORE stuff or AFTER stuff?

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.

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.

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

Will be completely wiped, I think, in favor of a Scanner (to tokens), then Parser mechanism.

No commit message