Opening empty files causes uncaught exception about nbt

[twoolie]

How do you mean uncaught exception on empty file? do you mean that the exception generated when opening an empty file is not caught and re-raised as something more descriptive, or do you think that in the case of an empty file, a valid nbt structure should be inserted automatically.
I have no problem with the first option, in fact i would be happy to add that straight away, however as for the latter solution i would be worried that this behavior would potentially mask any underlying problem with non-valid files being loaded (I class empty files as invalid as per spec.)

[MostAwesomeDude]

After re-reading the spec, I do agree with you on this. Maybe an NBTException or something like that would be appropriate. The struct.errors are not obvious at all; it took me the better part of a day to figure out what happened when I first saw it!

[twoolie]

Fixed this issue in latest commit. NBTFile now raises MalformedFileError on parse failure. if invoking parsing directly, struct.error is still returned by all tags as wrapping every failure point would add a lot of overhead.

(also fixed an edge case where TAG_String would not raise error on partial read)