Upgrading Python Breaks Extensions; Fix proposal

[Ignacio Vazquez-Abrams]

On Wed, 29 Aug 2001, Niki Spahiev wrote:

> 8/29/2001, 19:31:24, Ignacio Vazquez-Abrams wrote:
>
> IVA> [...]
> IVA> SO...
>
> IVA> I propose that we make the following changes to how Windows C extensions are
> IVA> built:
>
> IVA> 1) make some sort of 'thunking.h' or whatnot that contains global function
> IVA>      pointers for 'PyMem_Malloc', 'PyMem_Free', etc., and
> IVA> 2) make a pythonDLLX.Y.lib that contains a DllMain() that thunks the functions
> IVA>      from the application (which has previously linked python.X.Y.lib) and
> IVA>      sets the global variables in thunking.h.
>
> IVA> That way the behaviour of the Windows C extensions matches that of the Unix C
> IVA> extensions and pythonXY.dll can be done away with.
>
> Bigest problem IMO are PyXXX_Check() macro and PyXXX_Type data objects.

No, because the macros don't really exist, and the types could be linked in
with pythonDLLX.Y.lib.

-- 
Ignacio Vazquez-Abrams  <ignacio at openservices.net>