Re: Call order of parrent methods in __dispose() and __finalize()

This is a multi-part message in MIME format.

[email protected]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Not that I remember, I'll take a look at it.

Jiri

On Sat, Mar 5, 2011 at 10:08 PM, Dmitri Toubelis
<[email protected]> wrote:
> Hi,
>
> I noticed that implementation of __dispose() and __finalize() methods gen=
erated by GOB includes calls corresponding dispose() and finalize() methods=
 of the parent BEFORE deallocating local objects. GObject specification sta=
tes to call them AFTER local resources have been freed. In most cases that =
should not be an issue, but the fact that it is inconsistent with the speci=
fication makes me cautious. Is there any reason for this behavior?
>
> Regards,
> Dmitri
>
>
>
> --
> to unsubscribe:
> send mail to [email protected] with "unsubscribe gob-list" in the subject
>



--=20
Jiri (George) Lebl, http://www.math.ucsd.edu/~jlebl/ or http://www.jirka.or=
g/


[email protected]
Content-Type: text/plain; charset=us-ascii; name="footer.txt"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

--
to unsubscribe:
send mail to [email protected] with "unsubscribe gob-list" in the subject

[email protected]