A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2000-August/008159.html below:

[Python-Dev] Preventing recursion core dumps

[Python-Dev] Preventing recursion core dumps [Python-Dev] Preventing recursion core dumpsVladimir Marangozov Vladimir.Marangozov@inrialpes.fr
Fri, 11 Aug 2000 15:19:38 +0200 (CEST)
Barry Scott wrote:
> 
> Why not set a limit in the intepreter? Fixing this for every call in object.c
> seems a lots of hard work and will always leave holes.

Indeed.

> 
> For embedding Python being able to control the recursion depth of the
> intepreter is very useful. I would want to be able to set, from C, the
> max call depth limit and the current call depth limit.

Except exporting MAX_RECURSION_DEPTH as a variable (Py_MaxRecursionDepth)
I don't see what you mean by current call depth limit.

> I'd expect Python to set a min call depth limit.

I don't understand this. Could you elaborate?
Are you implying the introduction of a public function
(ex. Py_SetRecursionDepth) that does some value checks?

-- 
       Vladimir MARANGOZOV          | Vladimir.Marangozov@inrialpes.fr
http://sirac.inrialpes.fr/~marangoz | tel:(+33-4)76615277 fax:76615252



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