From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] css parser
Date: Wed, 14 Feb 2018 02:59:48 -0500 [thread overview]
Message-ID: <20180114025948.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802132053490.9207@carhart.net>
Some stats: on the monster stackoverflow css, their parser finds 3097 descriptors, mine finds 3711.
Who's right? Got me!
Of the 3711, there are 153 that I don't understand or haven't implemented.
Some of them, like @directives, I'm not suppose to implement.
Others I know how to address but it's one thing at a time.
Still 153 out of 3711 isn't bad for version 1.
I think querySelectorAll will come together soon, unless I'm missing something important here.
It's fun to program again, especially in js, where I can wield a regexp like a giant hammer,
where one (somewhat ugly) line of code does the equivalent of a page of C.
Chris remembrers, when we wrote version 1 of edbrowse in perl.
Karl Dahlke
prev parent reply other threads:[~2018-02-14 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 18:41 Karl Dahlke
2018-02-13 18:59 ` Adam Thompson
2018-02-14 4:54 ` Kevin Carhart
2018-02-14 7:59 ` Karl Dahlke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180114025948.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).