[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-commit] gnash ChangeLog server/vm/ExecutableCode.h test...
From: |
zou lunkai |
Subject: |
Re: [Gnash-commit] gnash ChangeLog server/vm/ExecutableCode.h test... |
Date: |
Sat, 1 Dec 2007 14:26:24 +0800 |
> > + // onClipEvents code are guarded by isDestroyed(), still might
> > be also guarded by isUnloaded()
> > + if( _target->isDestroyed() ) break;
>
> UNLOAD is one of these events, if we guard by isUnloaded() here it will never
> be executed.
>
yes, I understand.
isUnloaded() is more strict than isDestroyed(). Some events are
guarded by isDestroyed() and some others should be guarded by
isUnloaded(). Now we have actions guard on 3 levels: (1)guard before
pushing an action buffer; (2)guard before executing an action buffer
in on_event(); (3)guard in opcode level. This might be simplified at
next step, after more testing work.
--zou
On 11/30/07, strk <address@hidden> wrote:
> On Fri, Nov 30, 2007 at 09:59:05AM +0000, Zou Lunkai wrote:
>
> > + // onClipEvents code are guarded by isDestroyed(), still might
> > be also guarded by isUnloaded()
> > + if( _target->isDestroyed() ) break;
>
> UNLOAD is one of these events, if we guard by isUnloaded() here it will never
> be executed.
>
> --strk;
>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Gnash-commit] gnash ChangeLog server/vm/ExecutableCode.h test...,
zou lunkai <=