Recommended way to cleanup your own gobject types in a desktop app (finalize and/or dispose)
- From: "Jaap A. Haitsma" <jaap haitsma org>
- To: "GNOME Desktop Hackers" <desktop-devel-list gnome org>
- Subject: Recommended way to cleanup your own gobject types in a desktop app (finalize and/or dispose)
- Date: Sat, 22 Mar 2008 23:23:08 +0100
Hi,
When I look at projects like gnome-screensaver and gnome-power-manager
I see that for their own created gobject types only the finalize
function is implemented to cleanup the resources in the end of the
application.
gnome-volume-control uses only implements the dispose function
I understand from [1] that the two cleanup function dispose and
finalize exist to make bindings to languages with garbage collection
easier. So I guess for libraries for which other language bindings
might be written it's a good thing to follow the recommendation in [1]
of what to do in finalize and dispose.
So what is recommended for applications?
1) implement dispose and finalize as recommended
2) only finalize
3) only dispose
Jaap
[1] http://library.gnome.org/devel/gobject/unstable/gobject-memory.html
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]