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] my_ErrorReporter
Date: Fri, 24 Jan 2014 19:08:59 +0000	[thread overview]
Message-ID: <20140124190859.GA10925@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140024071320.eklhad@comcast.net>

On Fri, Jan 24, 2014 at 07:13:20AM -0500, Karl Dahlke wrote:
> Looks very much the same in Adam's latest as in mine.
> A small change, just to be safe, make the last line
> 
> if(report) report->flags = 0;

I've removed the JS_smprintf usage from jsloc.cpp and jsdom.cpp.

> That just makes me nervous.
What made me nervous about this was we were relying on something which isn't
really publicly exposed in SpiderMonkey and they freely admit they change the
internals (and public api) with no thought for backward compatability and very 
little notice.

> No I don't think that's any of our bug problems so far,
> but it's something we should address before a stable release.

Agreed.

> And the funny thing is, JS_smprintf is almost pointless in the C++ world,
> just concatenate the strings together and C++ will manage everything.
> And in my_ErrorReporter we could even use cerr directly.
> So might be we don't even need the silly function,
> I'm just saying I don't quite understand it.

We don't, and it's gone as per my last set of commits.

> As you see from this, I finally cloned your code.
> I plan to read through it first, then find / install moz 24,
> then build and play.

Cool. I've just pushed the commits removing JS_smprintf and reformatting the
code using ebindent.

Cheers,
Adam.

      reply	other threads:[~2014-01-24 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 12:13 Karl Dahlke
2014-01-24 19:08 ` Adam Thompson [this message]

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=20140124190859.GA10925@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).