diff options
| author | Tim Peters <tim.peters@gmail.com> | 2000-07-23 18:10:18 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2000-07-23 18:10:18 (GMT) |
| commit | 1be46844d9c858a21021e2c3ad0ef9bbee64d9e0 (patch) | |
| tree | ccddb1369834ad559d8c61954a8354548fdc2c57 /Parser | |
| parent | 2f2370bfc99e95a4f5edaf4d29cd47afd54fb1b7 (diff) | |
| download | cpython-1be46844d9c858a21021e2c3ad0ef9bbee64d9e0.zip cpython-1be46844d9c858a21021e2c3ad0ef9bbee64d9e0.tar.gz cpython-1be46844d9c858a21021e2c3ad0ef9bbee64d9e0.tar.bz2 | |
Recent ANSIfication introduced a couple instances of
#if RETSIGTYPE != void
That isn't C, and MSVC properly refuses to compile it.
Introduced new Py_RETURN_FROM_SIGNAL_HANDLER macro in pyport.h
to expand to the correct thing based on RETSIGTYPE. However,
only void is ANSI! Do we still have platforms that return int?
The Unix config mess appears to #define RETSIGTYPE by magic
without being asked to, so I assume it's "a problem" across
Unices still.
Diffstat (limited to 'Parser')
| -rw-r--r-- | Parser/intrcheck.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/Parser/intrcheck.c b/Parser/intrcheck.c index e9927e9..2f151ee 100644 --- a/Parser/intrcheck.c +++ b/Parser/intrcheck.c @@ -168,9 +168,7 @@ intcatcher(int sig) } signal(SIGINT, intcatcher); Py_AddPendingCall(checksignals_witharg, NULL); -#if RETSIGTYPE != void - return 0; -#endif + Py_RETURN_FROM_SIGNAL_HANDLER(0); } static RETSIGTYPE (*old_siginthandler)(int) = SIG_DFL; |