edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] [PATCH] Use the list class from the C++ STL,...
Date: Sun, 2 Feb 2014 13:43:11 +0000	[thread overview]
Message-ID: <20140202134311.GC32200@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140031133731.eklhad@comcast.net>

On Fri, Jan 31, 2014 at 01:37:31PM -0500, Karl Dahlke wrote:
> > my gcc gives me a bunch of warnings in url.c about using int and size_t
> 
> Mine doesn't, which is odd, but sure make any changes you like.
> 

Which gcc version are you using?

> > Yeah, but then we've still got the cw->tags array to worry about.
> 
> Shouldn't be a problem, if we move tags into jsstate,
> thus cw->jss->tags, as I wrote Chris off-line.
> The only reference elsewhere is some freeTags call in buffers.c,
> but we could just pass cw->jss in that case.
> Then it's all encapsulated in html.cpp, and should be easy.

Yep, sounds good.

> 
> I'd thought about the link list for the lines in a file,
> but it would be a lot of rewrite.
> Wouldn't help me much, I only have 2 gig ram anyways,
> and might even reduce the sizes of files I can edit.
> At this level it is a bit like politics,
> anything we do here will help some people and hurt others.

Perhaps, though I'd say having a hard limit on how long you can run edbrowse
for (due to the lack of line index reuse) is something which should be fixed.
Without using a linked list, I really can't think of a nice way round the issue
without shifting all the lines down to fill the gaps in the array (possibly
once the indices are all gone). This sounds a bit nasty though and I'm not sure
how large the implications of such swapping would be.

Cheers,
Adam.

  parent reply	other threads:[~2014-02-02 13:43 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
2014-02-02 13:43 ` Adam Thompson [this message]
  -- 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=20140202134311.GC32200@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).