On Oct 14, 12:37 pm, Nolan Darilek <[email protected]> wrote:
> Cool, thanks for the pointers. I tried posting earlier and it doesn't
> appear to have gone through, so please accept my apologies if multiple
> similar messages post. :)
>
> I'm experimenting with Rhino and am having more issues. Specifically,
> I have this Scala code:
>
> package info.thewordnerd.spiel.utils
>
> import org.mozilla.javascript.Context
> import org.mozilla.javascript.Scriptable
>
> object Scripter {
>
>   val js = """
>   """
>
>   def apply() = {
>     val cx = Context.enter
>     cx.setOptimizationLevel(-1)
>     val scope = cx.initStandardObjects
>     val result = cx.evaluateString(scope, js, "<spiel>", 1, null)
>     Context.exit
>     true
>   }
>
> }
>
> I get this in my logs:
>
> E/AndroidRuntime(  784): Uncaught handler: thread main exiting due to
> uncaught exception
>
> E/AndroidRuntime(  784): java.lang.ExceptionInInitializerError
>
> E/AndroidRuntime(  784):        at org.mozilla.javascript.Context.enter
> (Context.java:411)
>
> E/AndroidRuntime(  784):        at org.mozilla.javascript.Context.enter
> (Context.java:406)
>
> E/AndroidRuntime(  784):        at org.mozilla.javascript.Context.enter
> (Context.java:386)
>
> E/AndroidRuntime(  784):        at info.thewordnerd.spiel.utils.Scripter
> $.apply(Scripter.scala:12)
>
> Looks like the Context.enter call.
>
> Have you encountered this? Is something being caused by the default
> optimization level allowing for compilation, perhaps running something
> before I can set it to -1?
>
> Or is this another Dalvik issue? :(

Could be. Didn't the actual nested exception come out in the trace?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to