MenTaLguY wrote:
On Fri, 2008-06-27 at 12:41 +0200, J.B.C.Engelen@...1578... wrote:
For example, the parser calling code now catches the 2geom exception, outputs path string to screen and then rethrows the exception. For release only, instead of rethrowing it might want to return an empty path instead of throwing an exception.
This would be exactly the sort of sweeping under the carpet that I am concerned about. At minimum you should distinguish between simple parse errors (e.g. due to invalid input data), which *can* sometimes be reasonably treated relatively silently in this sort of way, from assertion failures, which should *always* be propagated up to the UI somehow.
BTW, if the parser encounters an error in the path data it should return the path upto and including the last parsed node (see the SVG spec).