Author haberman2
Recipients Alexander.Belopolsky, Arfrever, Christian.Tismer, Robin.Schreiber, amaury.forgeotdarc, belopolsky, haberman2, jcea, jhaberman, lekma, loewis, mattip, petr.viktorin, pitrou, seberg, steve.dower
Date 2021-09-27.17:39:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632764386.72.0.393707687089.issue15870@roundup.psfhosted.org>
In-reply-to
Content
> "static" anything in C is completely irrelevant to how symbols are looked up and resolved between modules

That is not true.  On ELF/Mach-O the "static" storage-class specifier in C will prevent a symbol from being added to the dynamic symbol table, which will make it unavailable for use across modules.

> I wasn't aware the C standard covered dynamic symbol resolution?

Well the Python docs invoke the C standard to justify the behavior of DLL symbol resolution on Windows, using incorrect arguments about what the standard says: https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_base

Fixing those docs would be a good first step.
History
Date User Action Args
2021-09-27 17:39:46haberman2setrecipients: + haberman2, loewis, jcea, amaury.forgeotdarc, belopolsky, pitrou, Arfrever, petr.viktorin, lekma, Alexander.Belopolsky, mattip, Robin.Schreiber, steve.dower, seberg, Christian.Tismer, jhaberman
2021-09-27 17:39:46haberman2setmessageid: <1632764386.72.0.393707687089.issue15870@roundup.psfhosted.org>
2021-09-27 17:39:46haberman2linkissue15870 messages
2021-09-27 17:39:46haberman2create