On Mon, Apr 12, 2010 at 7:18 PM, Maciej Fijalkowski <[email protected]> wrote: > Why? I think we do support that.
On IRC xorAxAx asked me to comment it out again. I don't know the exact reason, he can probably tell you more about it :) > > On Sat, Apr 10, 2010 at 8:31 AM, <[email protected]> wrote: >> Author: jandem >> Date: Sat Apr 10 16:31:22 2010 >> New Revision: 73627 >> >> Modified: >> pypy/branch/cpython-extension/pypy/module/cpyext/include/pymem.h >> Log: >> Comment out PyObject_REALLOC >> >> >> Modified: pypy/branch/cpython-extension/pypy/module/cpyext/include/pymem.h >> ============================================================================== >> --- pypy/branch/cpython-extension/pypy/module/cpyext/include/pymem.h >> (original) >> +++ pypy/branch/cpython-extension/pypy/module/cpyext/include/pymem.h Sat >> Apr 10 16:31:22 2010 >> @@ -7,7 +7,8 @@ >> >> /* XXX use obmalloc like cpython and pypy do, otherwise we might get >> segfaults */ >> #define PyObject_MALLOC PyMem_MALLOC >> -#define PyObject_REALLOC PyMem_REALLOC >> +// we won't support this >> +// #define PyObject_REALLOC PyMem_REALLOC >> #define PyObject_FREE PyMem_FREE >> >> #define PyMem_Malloc PyMem_MALLOC >> _______________________________________________ >> pypy-svn mailing list >> [email protected] >> http://codespeak.net/mailman/listinfo/pypy-svn >> > _______________________________________________ > [email protected] > http://codespeak.net/mailman/listinfo/pypy-dev _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
