This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients
Date 2002-04-05.15:24:39
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=21627

I don't want to change this, as I don't have access to an
AIX system, either; I might consider accepting a well-tested
patch, though. However,

http://usgibm.nersc.gov/vac/ref/compopts/ruoptlvl.htm

suggests that the default langlevel is ANSI, so I don't
trust the recommendation that adding it helps. Furthermore,
I'm concerned that something else may break, since the ANSI
settings of the compilers tend to disable a lot of useful
functions (which are merely POSIX instead of being even ANSI).

For your specific problem: Python.h offers the staticforward
define, which ought to correctly use static for each each
compiler.

If you think you need a platform-specific work-around, you
can add a pragma langlvl (see URL).

History
Date User Action Args
2007-08-23 14:00:23adminlinkissue539719 messages
2007-08-23 14:00:23admincreate