Hannes,
> I'm sorry that you feel this way. While I can understand your
> frustration, I think your conclusion is a bit harsh and over the top.
> I could now become defensive, or apologetic, or polemic, but I really
> think that kind of discussion is a waste of time.
I agree but believe me, that was not a pleasure to write such a mail ;-(
> Let's just look at
> your actutal problems instead. From what I understand, the bug that
> haunts you the most is #374918? I promise to look at your patch for
> that bug soon. If there are any other showstopper bugs you need fixed
> please let me know.
#374918 is not the only bug for which I'd like to see more interest from
the committers. Nevertheless you're right that it is currently the one
that has the highest priority for me. As written in my last comment to
the bug, the patch that I uploaded for 2 months doesn't fully solve the
problem. I will come today or tomorrow with a new patch (it was a long
work but I have currently only 2 failing standard tests remaining) and
this is where help from (probably all) committers will be needed: indeed
it is not possible to fix this when Rhino continue to use String, Double
and Boolean to handle JavaScript primitives. This means that extra
classes have to be introduced ("PrimitiveString", ...) what has large
consequences but what may be a chance to start addressing the problem
reported by Attila as "Death by Double".
Cheers,
Marc.
--
Web: http://www.efficient-webtesting.com
Blog: http://mguillem.wordpress.com
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
