gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash ChangeLog libbase/extension.cpp libbase/e...


From: strk
Subject: Re: [Gnash-commit] gnash ChangeLog libbase/extension.cpp libbase/e...
Date: Sun, 23 Sep 2007 11:01:34 +0200

On Sun, Sep 23, 2007 at 08:48:20AM +0000, Chad Musick wrote:

> +/// A destructive Getter/Setter property.
> +///
> +/// Just like a regular Getter/Setter property, but you only get one chance
> +/// to call its getValue -- it then becomes a simple property whose value is
> +/// the value returned by getValue.
> +///
> +class DestructiveGetterSetterProperty : public GetterSetterProperty
...
> +     /// Set GetterSetter, mValue as reachable (for GC)
> +     void setReachable() const
> +     {
> +             _getset.setReachable();
> +             mValue.setReachable();
> +     }

Is _getset still useful after mDestroyed  is set to true ?
If now we may set to NULL and don't release it's memory on destroy()

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]