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/2000-October/009854.html below:

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Python ceval.c,2.207,2.208

[Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Python ceval.c,2.207,2.208Thomas Wouters thomas@xs4all.net
Wed, 11 Oct 2000 10:31:49 +0200
On Wed, Oct 11, 2000 at 12:04:52AM -0700, Tim Peters wrote:

>   			default:
>   				fprintf(stderr, "Invalid argument to DUP_TOPX: %d!\n", oparg);

Hm, this fprintf is stray debugging code, added because I wasn't sure that a
SystemError wouldn't crash the interpreter, given that the stack is utterly
fu*d up at this point and we don't know what the compiler thinks is the
stack size or block size here. (The snippet doesn't show it, but it also
raises a SystemError.) Is it okay if I remove/comment this fprintf() before
2.0 final ?

(At least it didn't say "awoogah, stray debugging code detected, this
machine will self-destruct in 10 seconds" :-)

Another-day-another-demerit<wink>-ly y'rs,
-- 
Thomas Wouters <thomas@xs4all.net>

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



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