cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rice Yeh" <rice...@gmail.com>
Subject Re: Is catch (break | continue | return) supported?
Date Fri, 29 Sep 2006 17:58:48 GMT
I find it is because continuation does not support function call/apply yet
in rhino bug 258844. So FOM_Cocoon.suicide() does not work.

Rice

On 9/29/06, Rice Yeh <riceyeh@gmail.com> wrote:
>
> Have a new trace by printing out each step, I find FOM_Cocoon.suicide()
> does get called but the javascript intepreter just does not exit. Does
> anyone know what is going wrong?
>
> Rice
>
> On 9/29/06, Rice Yeh <riceyeh@gmail.com> wrote:
> >
> > Hi,
> >   By reading mail archives, I know there are catch (break | continue |
> > return) stuff. Is it still supported. I cannot find any examples about them
> > in trunk. In the
> > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=109528520325331&w=2, it
> > seems telling me that rhino's 'finally' now support catch (break) function.
> > How about the other twos catch(continue | return). I have written a section
> > of code to use try-finally to release resource usage. But
> > FOM_Cocoon.suicide() is never called, so showForm() does not suspend the
> > javascipt interpreter. I use Javascript debugger to trace the code and find
> > that the execution just stays on 'return this.sendFormAndWait(uri,
> > viewdata, ttl);' in Form.prototype.showForm many times. It just does not
> > go into sendFormAndWait(). I just cannot find any documents about these
> > things.
> >
> > Rice
> >
> >
> >
> >
>

Mime
View raw message