<html><body><div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Jan 5, 2025 at 4:43:39 PM, Jonas Maebe via fpc-pascal <<a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
That said, Darwin also uses two-level namespaces:<br><a href="https://blog.darlinghq.org/2018/07/mach-o-linking-and-loading-tricks.html#two-level-symbol-namespace">https://blog.darlinghq.org/2018/07/mach-o-linking-and-loading-tricks.html#two-level-symbol-namespace</a><br>. However, it does not do this through name mangling. The linker simply<br>encodes in the generated binary in which library/framework it found the<br>symbol at link time. Then, at run time, the dynamic linker will only<br>look for that symbol in that specific library (unless you force a<br>flat/single namespace through an environment variable).<br>
</blockquote>
</div>
<br>
<div dir="ltr">Thank you for your very detailed response.</div><div dir="ltr"><br></div><div dir="ltr">It sounds like maybe the external library name is only useful for DLLs and maybe the Darwin two level namespaces?</div><div dir="ltr"><br></div><div dir="ltr"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Regards,</div> Ryan Joseph</div></div><br>
</div></body></html>