summaryrefslogtreecommitdiffstats
path: root/Lib
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2002-03-20 04:02:31 (GMT)
committerTim Peters <tim.peters@gmail.com>2002-03-20 04:02:31 (GMT)
commitfbb556df15d66ced932619d61fb07ce9f9b34c0d (patch)
treead0c0b1889b482c04d2e669506e7555960b1ed52 /Lib
parentc63a396c5fc55beeaf3c973f137e160fc844d5a6 (diff)
downloadcpython-fbb556df15d66ced932619d61fb07ce9f9b34c0d.zip
cpython-fbb556df15d66ced932619d61fb07ce9f9b34c0d.tar.gz
cpython-fbb556df15d66ced932619d61fb07ce9f9b34c0d.tar.bz2
Arrange to export the _PyMalloc_{Malloc, Realloc, Free} entry points. On
Windows some modules are considered (by me, and I don't care what anyone else thinks about this <wink>) to be part of "the core" despite that they happen to be compiled into separate DLLs (the "to DLL or not to DLL?" question on Windows is nearly arbitrary). Making the pymalloc entry points available to them allows the Windows build to complete without incident when WITH_PYMALLOC is #define'd. Note that this isn't unprecedented. Other "private API" functions we export include _PySequence_IterSearch, _PyEval_SliceIndex, _PyCodec_Lookup, _Py_ZeroStruct, _Py_TrueStruct, _PyLong_New and _PyModule_Clear.
Diffstat (limited to 'Lib')
0 files changed, 0 insertions, 0 deletions