edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] many topics
Date: Mon, 03 Feb 2014 08:54:07 -0500	[thread overview]
Message-ID: <20140103085407.eklhad@comcast.net> (raw)

1. My latest push fixes the form reset bug, which I wrote about last time.

2. JSAutoCompartment, I almost understand what it does,
but still don't know why it is needed.
Look at the function JS_DefineProperty in the api, for example.
It's first argument is the context.
And all the functions seem to be like that.
They were before anywaays.
Every time you tap into the javascript machinery
you are telling it explicitly the context to use.
It is the first argument to everything.
Why then would it have to be set,
or assigned a compartment, or any such thing?
If a context were assigned in some global fashion,
then we wouldn't have to pass it as an argument to every js function
now would we?
There's something inconsistent about this design.

3. I think things are somewhat stable, and would like to reindent using
the kernel formatting.
That is a global change.
Are you working on something at present, or is the code quiescent?
Adam I know you said you wanted to make some changes to url.c
for compiler warnings.
Is this in process or on hold,
whence I could make a global change?

4. I think I know how to restructure the file map,
so I don't have marching index numbers that eventually run out,
unless I write another gc module, which I don't want to do.
There will probably still be a limit on files you can edit,
but larger, and perhaps architecture dependent, 4 byte pointers and indexes etc,
and in any case better than where we're at today.
So I may do that after the re-indent.

5. After all these changes have been made,
maybe we all play with it for a month or so to look for more bugs,
then cut a new version.


Karl Dahlke

             reply	other threads:[~2014-02-03 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 13:54 Karl Dahlke [this message]
2014-02-03 21:35 ` Chris Brannon
2014-02-03 23:20 ` 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=20140103085407.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).