19 Nov
2017
19 Nov
'17
10:19 p.m.
You can probably wrap one (or both) of them in a namespace (or class) in a separate .h file containing just the include to one lib and definitions of (used|all) functions in the lib, calling the lib, and include that .h file instead of the library one. (Not very practical, I know)
--
Mc
On 11/17/2017 11:35 AM, Eduard Braun wrote:
> Hi all,
>
> just stumbled across something again I always wanted to ask the devs
> more familiar with C/C++ than me:
>
> If the same function name is used in two third party C libraries, is
> there a good way to avoid this name conflict without changing the third
> party library?
>
> Background is a conflicting function name in libwmf and libuemf that
> caused some crashes [1] and was fixed by Tav by renaming the function in
> libuemf [2] which works as we have a copy of that library but obviously
> will cause issues if we attempt to update the library with upstream code
> at some point in the future.
>
> Best Regards,
> Eduard
>
> [1] https://bugs.launchpad.net/inkscape/+bug/1616844
> [2]
> https://gitlab.com/inkscape/inkscape/commit/038293f7984fa8bfd89a0451d3d77fce...
>
>
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel