From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] [PATCH] Use the list class from the C++ STL,...
Date: Thu, 30 Jan 2014 12:49:05 -0500 [thread overview]
Message-ID: <20140030124905.eklhad@comcast.net> (raw)
static list < struct htmlTag *>htmlStack;
It may just be a matter of style, or perhaps evolution
since my lists had to handle pointers, but why aren't you using
static list < struct htmlTag >htmlStack;
An array of the actual structures, rahter than pointers to the structures.
Thus the structures are allocated and freed as you go, by C++,
and I don't have to alloc and free them.
They are "inline", for lack of a better term.
I'm just looking to understand here,
and to learn what these lists can do for us.
Karl Dahlke
next reply other threads:[~2014-01-30 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 17:49 Karl Dahlke [this message]
2014-01-30 21:23 ` Chris Brannon
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 22:25 Karl Dahlke
2014-01-31 13:02 Karl Dahlke
2014-01-31 17:33 ` Adam Thompson
2014-01-31 18:37 Karl Dahlke
2014-01-31 18:48 ` Chris Brannon
2014-02-02 13:43 ` Adam Thompson
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=20140030124905.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).