- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Sat, 27 Nov 2021 13:57:32 +0000
- To: Dave Pawson <dave.pawson@gmail.com>
- Cc: ixml <public-ixml@w3.org>
On Saturday 27 November 2021 10:57:10 (+01:00), Dave Pawson wrote: > I find 'line termination characters' a nuisance, so +1 to that. > I guess we'd need \ to identify line continuations (long lines?) > > I think spacing is required for readability though. I wasn't suggesting changing anything, just as data for interest. ixml doesn't have the notion of lines. It's just a stream of characters where linefeeds are just another space character, so line continuations would not be necessary. Steven > > regards > > On Sat, 27 Nov 2021 at 09:50, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > > > > I had noticed that ambiguity slows down parsing a lot, and so I wondered to > > what extent near ambiguity had an effect. > > What do I mean with near ambiguity? Well, "." is a namefollower character, > > so with rules like > > > > a: b, c. > > d: e, f. > > > > it's not until the parser sees the "d" that it knows that "c." is not a > > name, but a name followed by a dot. > > > > So I created a number of versions of ixml: > > 1. Removing "." as a namefollower. > > 2. With a space between every token. > > 3. With no spaces (linefeeds were kept). > > > > > > Times (remember that this is an interpreted language, so numbers will be > > quite high): > > > > ixml straight out of the spec: > > real 0m15.740s > > user 0m15.722s > > sys 0m0.017s > > > > ixml without . as a namefollower > > real 0m12.817s > > user 0m12.800s > > sys 0m0.016s > > > > extra spaces: > > real 0m12.288s > > user 0m12.268s > > sys 0m0.020s > > > > No spaces: > > real 0m7.169s > > user 0m7.135s > > sys 0m0.033s > > > > > > > >
Received on Saturday, 27 November 2021 13:57:48 UTC