Subject: Re: [xsl] Re: Getting info of runtime failure in saxon environment From: Michael Kay <mike@xxxxxxxxxxxx> Date: Wed, 27 Feb 2013 16:28:41 +0000 |
On 27/02/2013 12:41, Michael Kay wrote:My point is that to break a file into lines you need first to decode the bytes, and if it's sufficiently corrupt that you can't decode it, then knowing what line you're on requires some fancy footwork. Your decoding error was happening well before tokenization.Note that the reason some parsers fail to provide location information for an
encoding error is that in a properly layered architecture you need to do
decoding before you start recognizing line endings, which means that the
information about line numbers is typically not available at the point where the
decoding error is detected.
I'm not sure I understand this. It seems from what you're saying that, for example, a compiler should also be unable to give line number information for errors (unless it's not "properly layered"). Shouldn't the tokeniser keep track of where each token comes from in the source file and be able to tell you this if asked?
Michael Kay Saxonica
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Re: Getting info of runti, John English | Thread | Re: [xsl] Re: Getting info of runti, Liam R E Quin |
Re: [xsl] Re: Getting info of runti, John English | Date | Re: [xsl] Re: Getting info of runti, Liam R E Quin |
Month |