Closed Bug 735915 Opened 12 years ago Closed 12 years ago

make atk interface vfuncs static

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: tbsaunde, Assigned: tbsaunde)

Details

Attachments

(1 file, 1 obsolete file)

      No description provided.
Attached patch make atk interface vfuncs static (obsolete) — Splinter Review
Attachment #606017 - Flags: review?(askalski)
Why would we need to do that?
We build our code with visibility hidden, it doesn't make any different with "static".

BTW:
extra spacing here:
+
+  void
+imageInterfaceInitCB(AtkImageIface* aIface)
(In reply to Ginn Chen from comment #2)
> Why would we need to do that?
> We build our code with visibility hidden, it doesn't make any different with
> "static".

I'd say "need" is too strong, but it should help reduce what gets included hopefully making  the build a little faster and reducing what depends on what which at least in theory should help incremental builds.

> BTW:
> extra spacing here:
> +
> +  void
> +imageInterfaceInitCB(AtkImageIface* aIface)

yeah, fixed locally
In AtkSocketAccessible.cpp

it should be
extern "C" {
void (*AtkSocketAccessible::g_atk_socket_embed) (AtkSocket*, gchar*) = NULL;
}

or just
AtkSocketEmbedType AtkSocketAccessible::g_atk_socket_embed;
(In reply to Ginn Chen from comment #4)
> or just
> AtkSocketEmbedType AtkSocketAccessible::g_atk_socket_embed;

I mean

AtkSocketEmbedType AtkSocketAccessible::g_atk_socket_embed = NULL;
(In reply to Trevor Saunders (:tbsaunde) from comment #3)
> (In reply to Ginn Chen from comment #2)
> > Why would we need to do that?
> > We build our code with visibility hidden, it doesn't make any different with
> > "static".
> 
> I'd say "need" is too strong, but it should help reduce what gets included
> hopefully making  the build a little faster and reducing what depends on
> what which at least in theory should help incremental builds.

Another nice advantage of this way imo is that it makes it clearer to the reader what boundaries there are between "modular" components.
(In reply to Ginn Chen from comment #5)
> (In reply to Ginn Chen from comment #4)
> > or just
> > AtkSocketEmbedType AtkSocketAccessible::g_atk_socket_embed;
> 
> I mean
> 
> AtkSocketEmbedType AtkSocketAccessible::g_atk_socket_embed = NULL;

yeah, sounds good I'm not really sure why Mike didn't just use the typedef originally.
It looks good to me, though I just checked whether code transfer matches and mochitests passes.
Attachment #606017 - Flags: review?(askalski) → review+
Attached patch patch 2Splinter Review
fixed comments
Attachment #606348 - Flags: review?(ginn.chen)
Attachment #606017 - Attachment is obsolete: true
Attachment #606348 - Flags: review?(ginn.chen) → review+
https://hg.mozilla.org/mozilla-central/rev/4e78e0214934
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Version: unspecified → Trunk
Assignee: nobody → trev.saunders
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: