Put "extern" in front of a pile of function declarations.
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 31 Oct 2001 07:47:27 +0000 (07:47 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Wed, 31 Oct 2001 07:47:27 +0000 (07:47 +0000)
commitbadacf808dbcbc9cff487469c2b814833800dcdf
tree023bcd46af188932f8ffdee562cf0bf5d6d3baba
parent80ca5a4d768d9f2f2d45ab5930fa9f628a72ee4b
Put "extern" in front of a pile of function declarations.

It makes no difference if they really are function declarations;
however, in plugins, when building on OSes that don't let
dynamically-loaded modules access functions in the main program (e.g.,
Windows), when compiling a plugin, <plugin_api.h> defines the names of
those functions as (*pointer_name), so they turn into declarations of
pointer variables pointing to the functions in question, and, on
platforms with a def/ref model in the linker, if a plugin has more than
one source file that gets linked into the plugin, the linker may get
upset at two definitions of the same variable.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@4114 f5534014-38df-0310-8fa8-9805f1628bb7
epan/column-utils.h
epan/packet.h
epan/proto.h
epan/tvbuff.h
packet-giop.h
prefs.h