edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Javascript support
Date: Sun, 22 Dec 2013 10:36:56 -0800	[thread overview]
Message-ID: <87lhzcd96f.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20131222164813.GA12841@toaster.adamthompson.me.uk> (Adam Thompson's message of "Sun, 22 Dec 2013 16:48:13 +0000")

Adam Thompson <arthompson1990@gmail.com> writes:

> "SpiderMonkey now provides a fully C++ interface,
> so embedders relying on embeddability in C projects will have to convert to
> C++, or implement their own adapter code."

Hi,
Thank you ever so much for doing the research.

Years ago, we batted around the idea of rewriting edbrowse in C++.
Those string objects would sure be nice, and after all, edbrowse is very
string-intensive.  We also use lists in some places, and we could use
STL's list container instead.  But it never happened.  C++ is a
complicated beast.  The people who work on edbrowse are more comfortable
with C.  I used to be decent with C++, but I've managed to forget most
of what I knew.  So I'm not chomping at the bit to do this.  I wonder
how difficult the adapter code will be?  I assume it'll just be tedious.

Happy Holidays,
-- Chris

  reply	other threads:[~2013-12-22 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 18:45 [Edbrowse-dev] html unicode translations in edbrowse Karl Dahlke
2013-12-19 12:20 ` Adam Thompson
2013-12-21 18:00 ` [Edbrowse-dev] Javascript support MENGUAL Jean-Philippe
2013-12-22 15:42   ` Chris Brannon
2013-12-22 16:48     ` Adam Thompson
2013-12-22 18:36       ` Chris Brannon [this message]
2013-12-22 19:10         ` Adam Thompson
2014-01-08 12:50   ` Adam Thompson
2013-12-22 22:26 Karl Dahlke
2013-12-23  9:26 ` Adam Thompson
2013-12-23 14:26   ` Chris Brannon
2013-12-24  9:25     ` Adam Thompson
2013-12-23 14:29 Karl Dahlke

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=87lhzcd96f.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).