On Mar 19, 7:37 am, Hannes Wallnoefer <[email protected]> wrote:
> The problem is obviously the patch 
> forhttps://bugzilla.mozilla.org/show_bug.cgi?id=456546
>
> The intention here was to be able to pass any Scriptable
> implementations to methods with a Scriptable or ScriptableObject
> argument, but of course it also applies to methods taking a
> java.lang.Object argument.
>
> I'll attach a new patch soon.
>
> Hannes
>
> On 18 Mrz., 19:24, Norris Boyd <[email protected]> wrote:
>
> > On Mar 18, 10:56 am, Hannes Wallnoefer <[email protected]> wrote:
>
> > > Just got this from a Helma user: The following worked with Rhino
> > > 1.7R1:
>
> > > Rhino 1.7 release 1 2008 03 06
> > > js> var sdf = new java.text.SimpleDateFormat();
> > > js> sdf.format(new Date());
> > > 18.03.09 18:50
>
> > > however the 1.7R2 release candidates throw an exception:
>
> > > Rhino 1.7 release 2 2009 01 16
> > > js> var sdf = new java.text.SimpleDateFormat();
> > > js> sdf.format(new Date());
> > > js: "<stdin>", line 3: The choice of Java constructor format matching
> > > JavaScript argument types (object) is ambiguous; candidate
> > > constructors are:
> > >     class java.lang.String format(java.lang.Object)
> > >     class java.lang.String format(java.util.Date)
> > >         at <stdin>:3
>
> > > I'll look into it later this evening. Can we wait a little longer with
> > > 1.7R2 until we've figured this out?
>
> > > Hannes
>
> > Yes, we can wait. Let me know what you find out.
>
> > --N

So is the 1.7R2 release good to go from your perspective?

--N
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino

Reply via email to