- From: Dave Pawson <dave.pawson@gmail.com>
- Date: Fri, 4 Feb 2022 08:12:34 +0000
- To: Norm Tovey-Walsh <norm@saxonica.com>
- Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, ixml <public-ixml@w3.org>
Tks for the clarification Norm. @MSM - do you mean 'in all circumstances'? As Norm says, I've met a confirmed error, should I continue (could I even continue parsing) to the end? Doesn't sound like a sensible option from the outside? Would a user be interested? In many cases the first error compounds later ones etc? Parse to the end of the input string... unless errors are found? Is that a reasonable caveat? HTH DaveP On Thu, 3 Feb 2022 at 19:08, Norm Tovey-Walsh <norm@saxonica.com> wrote: > > > What has changed? > > I wasn’t aware of the discussion from last April. I have not read all of > the archives with the care I might have liked. > > I don’t think this is behavior that needs to be conformant in 1.0, so > I’m happy to leave it closed. It seems like something that could be > added later. > > I implemented a version of it, partly out of curiosity and partly > because I have found various aspects of writing an ixml parser extremely > frustrating and in the moment, this wasn’t one of them. > > For those interested, if I reach a point in the parse where I’ve clearly > gone off the rails never to recover, I look back at the last token that > was successfully parsed. If among the parses for that token was a > complete sentence in the grammar, then I provide a mechanism for > returning it. > > I also buffer up the tokens consumed from the input iterator so that a > user who wishes can restart at the first bad character. If, for example, > you were matching a*b* and you fed the input aaaabbbbaaaabbbb, you could > extract the prefix parse “aaaabbbb” and restart the parse (or start > another parse, it’s just an iterator) with “aaaabbbb”. > > Be seeing you, > norm > > -- > Norm Tovey-Walsh > Saxonica -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
Received on Friday, 4 February 2022 08:12:57 UTC