From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Now on 24
Date: Wed, 29 Jan 2014 16:26:21 -0800 [thread overview]
Message-ID: <87mwiel3gy.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140029134918.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 29 Jan 2014 13:49:18 -0500")
> use string objects where it makes sense,
> and use the array class instead of my lists so all those warnings go away.
> I could do this, unless someone else is in there anyways
Swapping your lists for C++ lists should be a five-minute job, but the
string stuff is going to be tedious. I'm also willing to do it if you
aren't too enthused at the prospect.
-- Chris
prev parent reply other threads:[~2014-01-30 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 18:49 Karl Dahlke
2014-01-29 22:31 ` Adam Thompson
2014-01-30 0:26 ` Chris Brannon [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=87mwiel3gy.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).