GNOME Bugzilla – Bug 653244
Review the padding of ATK classes
Last modified: 2021-06-10 11:25:42 UTC
(Spun off from bug 648616) Most of the objects and interfaces have some padding on the class structure. Some things to think about: * It is enough the current number of paddings? * Do atk really need the typedef AtkFunction? IMHO, it is somewhat silly to define a typedef to a basic type like gpointer to be used just for the paddings. In the same way, when someone find AtkFunction the first thought is that this is something important and really used. Projects like gtk and clutter use directly gpointer. * Atk uses the next format: AtkFunction pad1; AtkFunction pad2; Probably inherited from gtk But clutter uses this format: /* padding for future expansion */ gpointer _padding_dummy[29]; Probably cleaner, although this is just a cosmetic change
[Mass-reassigning open atk bug reports for better trackability as requested in https://bugzilla.gnome.org/show_bug.cgi?id=653179 . PLEASE NOTE: If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add atk-maint@gnome.bugs to your watchlist at the bottom of https://bugzilla.gnome.org/userprefs.cgi?tab=email to keep watching atk bug reports in GNOME Bugzilla. Sorry for the noise: Feel free to filter for this comment in order to mass-delete the triggered bugmail.]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of atk, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a ticket at https://gitlab.gnome.org/GNOME/atk/-/issues/ Thank you for your understanding and your help.