From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] ebjs.p
Date: Sun, 26 Jan 2014 21:39:54 -0500 [thread overview]
Message-ID: <20140026213954.eklhad@comcast.net> (raw)
Don't need to pass context, ever, as it is accessible globally.
Example our_JS_NewStringCopyN
And I wonder if we're going to need these our_ wrappers in the future.
js.h
Line 4, probably list the new cpp files there.
Keeping jcx global, that's ok, though you could just use cw->jss->jcx instead,
which is longer and bulkier I realize,
but it would also eliminate the need for the jMyContext() function altogether.
Whatever you think is fine with me.
This is as far as I've gotten.
Karl Dahlke
reply other threads:[~2014-01-27 2:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140026213954.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).