From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] [PATCH] Use the list class from the C++ STL,...
Date: Fri, 31 Jan 2014 10:48:54 -0800 [thread overview]
Message-ID: <87r47oj8bt.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140031133731.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 31 Jan 2014 13:37:31 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> Shouldn't be a problem, if we move tags into jsstate,
> thus cw->jss->tags, as I wrote Chris off-line.
Oh, struct htmlTag is forward-declared in eb.h, so cw->tags is struct
htmlTag **.
-- Chris
next prev parent reply other threads:[~2014-01-31 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 18:37 Karl Dahlke
2014-01-31 18:48 ` Chris Brannon [this message]
2014-02-02 13:43 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2014-01-31 13:02 Karl Dahlke
2014-01-31 17:33 ` Adam Thompson
2014-01-30 22:25 Karl Dahlke
2014-01-30 21:58 Karl Dahlke
2014-01-30 22:18 ` Chris Brannon
2014-01-31 12:09 ` Adam Thompson
2014-01-31 12:35 ` Chris Brannon
2014-01-30 17:49 Karl Dahlke
2014-01-30 21:23 ` Chris Brannon
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=87r47oj8bt.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--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).