BTW: there is another implementation (called my_strdup) in
Modules/_ctypes/_ctypes_test.c, why not use the one in Python/strdup.c there?
I guess that's historical, from the times when ctypes was still a
separate package.
my_strdup is an exported function in _ctypes_test.pyd (on Windows),
On Wednesday 07 January 2009 16:30:23 Daniel Stutzbach wrote:
On Wed, Jan 7, 2009 at 5:30 AM, Ulrich Eckhardt dooms...@knuut.de wrote:
MS Windows CE doesn't provide strdup(), so where should I put it? I guess
I should just compile in Python/strdup.c, right?
I'm not an expert on Windows CE,
On Wed, Jan 7, 2009 at 5:30 AM, Ulrich Eckhardt dooms...@knuut.de wrote:
MS Windows CE doesn't provide strdup(), so where should I put it? I guess I
should just compile in Python/strdup.c, right?
I'm not an expert on Windows CE, but I believe it calls the function
_strdup():
MS Windows CE doesn't provide strdup(), so where should I put it? I guess I
should just compile in Python/strdup.c, right?
Right.
However, where should I declare it?
I recommend pyport.h.
Also, there is HAVE_STRDUP. I would actually expect that #undef HAVE_STRDUP
would do the trick to
