I just tried to read in an invalid MRML file. It
contained NO
</MRML> in it. The slicer did not crash .
But, it did not return an error message either. It was
as if
the slicer ignored me.
An error message for MRML files that were unable
to be parsed is probably appropriate. Perhaps easier
to implement would be to check to see if the nothing
was found in the MRML file, and report a message
suggesting that there might be an error with the file.