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-July/005517.html below:

[Python-Dev] USE_STACKCHECK/PyOS_CheckStack

[Python-Dev] USE_STACKCHECK/PyOS_CheckStack [Python-Dev] USE_STACKCHECK/PyOS_CheckStackTim Peters tim_one@email.msn.com
Wed, 5 Jul 2000 21:27:48 -0400
Twice in ceval.c, and once in object.c, there's code referencing
PyOS_CheckStack under the control of the preprocessor symbol USE_STACKCHECK.
There's nothing in the std distribution that could possibly define either of
those names.  Why are they there?  If nobody objects, I'll get rid of this
code!

PS for Jeremy:  the mechanism I was thinking of is _ts.recursion_depth,
which is used cross-platform in ceval.c, like so:

	if (++tstate->recursion_depth > MAX_RECURSION_DEPTH) {
		--tstate->recursion_depth;
		PyErr_SetString(PyExc_RuntimeError,
				"Maximum recursion depth exceeded");
		tstate->frame = f->f_back;
		Py_DECREF(f);
		return NULL;
	}

The effectiveness of this is dependent on guessing a good value (per
platform) for MAX_RECURSION_DEPTH (and it's broken under Windows in 1.5.2).





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