Couldn't agree more. This just does not make sense in a tight mcu environment (it would probably haunt me a bit until I found out the reason for this probably historic mess :) )

Eyal

> On 21 Oct 2013, at 18:57, Gordon Williams <notifications@github.com> wrote:
> 
> In src/jsparse.c:
> 
> > @@ -1143,11 +1161,22 @@ JsVar *jspeFactorNewString() {
> >  
> >  JsVar *jspeFactorNewId() {
> >    // TODO: these should be regular constructors
> > +  bool isArray = false, isString = false;
> > +  const char *name = jslGetTokenValueAsString(execInfo.lex);
> > +
> > +  if (strcmp(name, "Array")==0)
> Thanks! Let's find out ;) I've created a bug for it and I'm just giving it a go.
> 
> As you say, that behaviour is strange:
> 
> var a = 'X';
> var b = new String('X')
> a
> "X"
> b
> "X"
> a==b
> true
> "X"==="X"
> true
> a===b
> false
> At some point we've got to say we're not implementing pointless JavaScript weirdness - and I think that's something we could ignore.
> 
> —
> Reply to this email directly or view it on GitHub.