Closed feloy closed 8 years ago
I do like the idea of having the parser be more robust, and a bit more tolerant of non-standard/malformed files. I also am fairly sure your solution is sound, although I think I might want to add a warning so the calling code can know that something was wrong but handled. Let me work with your example and see what I come up with, and thanks for the great suggestion.
Fixed in latest 2.2.3-SNAPSHOT. Includes an error message in the parser errors collection, but allows parsing to continue.
Some generated GEDCOM files have incorrect numerotation. Below an extract of a file generated by GensDataPro: in the latest lines, a line beginning with 3 is directly following a line beginning with 1. The library does not correclty handle this error and raises an error.
Below some modification that permits the library to continue the parsing without error: