[Patches] [Patch #100853] merging my*.h into pyport.h

Thomas Wouters thomas@xs4all.net
Mon, 31 Jul 2000 18:36:24 +0200


On Mon, Jul 31, 2000 at 08:16:32AM -0700, noreply@sourceforge.net wrote:

> Date: 2000-Jul-31 08:16
> By: marangoz
> 
> Comment:
> Feedback: I'm not thrilled by the fact that Python interfaces are defined
> in pyport.h. Defining only the ANY & _Mem_EXTRA compatibility issues
> is fine, but official PyMem_ interfaces is not so fine.
> 
> I'd prefer a separate .h file, be it mymalloc.h or pymalloc.h.

Agreed: pyport.h should be for platform dependant things: prototypes that
should be in standard include files, features/macros that are necessary on
some systems, etc. mymalloc.h should be renamed to pymalloc.h, because it
isn't a local copy of a system interface, but rather a seperate interface
that happens to mirror a well-known one, but can be implemented however one
wishes. It's Python's Memory Allocator ;-)

-- 
Thomas Wouters <thomas@xs4all.net>

Hi! I'm a .signature virus! copy me into your .signature file to help me spread!