From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] [ecmascript code]
Date: Fri, 1 Sep 2017 14:09:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1709011355150.28527@carhart.net> (raw)
Karl, Dominique, everyone who ported to duktape, do you know of a way to
echo JS function bodies that are represented as [ecmascript code]? For
instance, from jdb,
xxx = function() { alert('hi') }
function () { [ecmascript code] }
xxx
function () { [ecmascript code] }
Using moz, when I typed xxx it would echo the program. One use for this
is when diagnosing event handler code that might exist inline in a JS
file, maybe in something like
$(elements).on("click",handler(){ } )
(It doesn't have to be jquery - you could substitute getElementsByTagName,
etc etc.)
So the handlers are doled out to all of the elements in the result set
maybe. And it's invaluable to be able to come along later and echo the
contents of the onclick$$array and so on.
I'm assuming that when it tells you something is [ecmascript code], it's
like when you get [native code]. It's compiled, it's bytecode, it's on a
different level. It isn't available to the interpreted environment.
If you dunno, I'll try asking the duktape developers. Karl, have you
talked to them a bit?
thanks
Kevin
next reply other threads:[~2017-09-01 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 21:09 Kevin Carhart [this message]
2017-09-02 1:02 ` Karl Dahlke
2017-09-02 1:14 ` Karl Dahlke
2017-09-02 7:57 ` Kevin Carhart
2017-09-02 16:20 ` Karl Dahlke
2017-09-03 5:58 ` Kevin Carhart
2017-09-03 22:12 ` [Edbrowse-dev] very good news Kevin Carhart
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=alpine.LRH.2.03.1709011355150.28527@carhart.net \
--to=kevin@carhart.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).