edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: I don't know shit about xml
Date: Wed, 12 Oct 2022 20:32:37 -0400	[thread overview]
Message-ID: <20220912203237.eklhad@comcast.net> (raw)
In-Reply-To: <Y0dXGYdDnxu7bVLU@codewreck.org>

The scanners have huge overlap, and I expect only minor differences, so 
should keep it as one function. 
All the tag cracking and attribute cracking and &element; cracking and 
building the tree it's all the same. 
I suspect html came first and xml was a direct generalization, by 
throwing away the semantics. For sure one was very quickly on the heels 
of the other.

Karl Dahlke

  reply	other threads:[~2022-10-13  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 22:51 Karl Dahlke
2022-10-13  0:08 ` Dominique Martinet
2022-10-13  0:32   ` Karl Dahlke [this message]
2022-10-19  8:14     ` Adam Thompson
2022-10-19  9:13       ` Karl Dahlke

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220912203237.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=edbrowse-dev@edbrowse.org \


* 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).