Re: Reference to a C++ object in GTK+ callbacks
- From: Wallace Owen <wallace owen L-3com com>
- To: "Brian J. Tarricone" <bjt23 cornell edu>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: Reference to a C++ object in GTK+ callbacks
- Date: Wed, 14 Dec 2005 12:41:31 -0800
On Wed, 2005-12-14 at 11:28 -0800, Brian J. Tarricone wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
...
IIRC, I believe the functions only have to be static in this case if
they're actually C++ class methods. Plain old C global functions don't
need to be static, though if they're only used in that one module,
there's no reason *not* to make them static, and it's good practice to
do so.
True. the static keyword is 'overloaded' with a different meaning - it
doesn't change scope, but indicates that the function is one that
doesn't have an associated object.
// Wally
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]