#442 Include textual position info in CIF check violation messages.
requested to merge 442-consider-including-textual-file-position-for-cif-common-checks-violations into develop
This uses the suggestion from #442 (comment 1038341) to still have position information for null specifications as report object. It does lead to a change in CifPreconditionChecker, two toString overloads and a more complicated implementation of toString(Specification spec) than in #442 (comment 1038279). Let me know whether you prefer this implementation or the simpler one.
Also let me know what you think of the result for users, as visible in the changed test output.
Closes #442 (closed)