From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] parser separation
Date: Sun, 30 Aug 2015 08:21:07 -0400 [thread overview]
Message-ID: <20150730082107.eklhad@comcast.net> (raw)
In-Reply-To: <20150830114343.GB23730@toaster.adamthompson.me.uk>
> Still not sold on hubbub.
Oh I'm not either, not at all,
just like I'm not sold on v8 -
but encapsulating things in separate sourcefiles gives us options,
and flexibility, and sometimes leads to a better design.
I'll get started on this today.
And I agree we don't have to build a fully functional node right now,
but there are I suspect a few things we'll need to add to take advantage of tidy.
More on this later.
Karl Dahlke
next prev parent reply other threads:[~2015-08-30 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 11:31 Karl Dahlke
2015-08-30 11:43 ` Adam Thompson
2015-08-30 12:21 ` Karl Dahlke [this message]
2015-08-30 19:06 ` Adam Thompson
2015-08-30 19:25 ` 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:
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=20150730082107.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).