Namespaces and inter-library private symbols
Nicolas.Williams at sun.com
Fri Nov 13 13:25:31 EST 2009
On Wed, Nov 11, 2009 at 10:11:55PM -0500, Jeffrey Altman wrote:
> I don't remember the introduction of the accessors as having anything to
> do with Windows in particular. The problem was the pollution of the
> export name space from shared libraries and the desire to be able to
> change the names and parameters of truly internal private functions that
> must be used by gssapi without being forced to change the signature of
> the of the library.
If a run-time linker encodes prototype information into its shared
object outputs, then I agree that exporting private symbols becomes a
problem, and the accessor is probably the best solution.
More information about the krbdev