Subj : Re: Strange Rhino NativeString behavior
To   : netscape.public.mozilla.jseng
From : Matt McShane
Date : Tue Oct 26 2004 12:43 am

Brendan Eich wrote:
> But I regard the distinction visible in the language between primitive 
> types and their "boxing" object subtypes to be a botch.  

Agreed. For lots of reasons that have been widely discussed in other 
forums. The question for me is what to do now, which leads me to . .  .

> It's too late to change this for JS1, but it may be possible for JS2 
> (ECMA-262 Edition 4).  I (possibly wrongly) recall one of waldemar's 
> draft specs eliminating the distinction.

Is it worth me sending an advocacy email out to someone? What is the 
ECMA process like? Google and ecma-international.org didn't turn up any 
info :(

In the meantime, if I were to try to hack a "no primitives" mode into 
Rhino (don't know how hard that would be - haven't even started looking) 
would anyone be interested in hearing about it? If so, I can do some of 
my thinking out loud here. If not, I'll do it and shut up.

Thanks for the explanation, Brendan.

Regards,
Matt.

.