A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-January/019503.html below:

[Python-Dev] Name clash with typedefs in object.h

[Python-Dev] Name clash with typedefs in object.h [Python-Dev] Name clash with typedefs in object.hJack Jansen jack@oratrix.nl
Tue, 15 Jan 2002 16:29:26 +0100
Object.h declares various typedefs for routine pointers, and their names are 
not adorned with some sort of Py_ prefix.

Suddenly this has started to be a problem for me on OSX (not sure why: either 
object.h changed or because I got a new version of the OSX devtools): object.h 
declares a typedef "destructor", and if that is in scope when <pthread.h> is 
included this fails, which uses the name "destructor" as an argument name (for 
a routine pointer), and the parser gets confused.

I think it's GCC that's to blame here, but still: shouldn't these names have 
some sort of a prefix?

Alternatively I can apply a quick fix by defining "destructor" as something 
else just before including <pthread.h>...
--
- Jack Jansen        <Jack.Jansen@oratrix.com>        http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma Goldman -






RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4