recursion depth

[TK]

Hi,

is there a way to change the recursion depth for a function/method?

In Python can I do it:

import sys
sys.setrecursio nlimit(1500)

Thanks for help.

o-o

Thomas

[Michael DOUBEZ]

TK a écrit :

Hi,

is there a way to change the recursion depth for a function/method?

Sure. First make it recursive terminale and then iterative.

>
In Python can I do it:

import sys
sys.setrecursio nlimit(1500)

If you want your compiler to allow deeper recursion, you should ask in
the relevant group or mailing list.

Michael

[Michael DOUBEZ]

Michael DOUBEZ a écrit :

TK a écrit :

>is there a way to change the recursion depth for a function/method?

Sure. First make it recursive terminale and then iterative.

I think the proper english term is "tail recursive".

Michael

[Ioannis Gyftos]

On Nov 14, 2:24 pm, TK <[e-mail] rote:

Hi,

is there a way to change the recursion depth for a function/method?

In Python can I do it:

import sys
sys.setrecursio nlimit(1500)

Thanks for help.

o-o

Thomas

No built-in mechanism that I am aware of.

But you could always use an optional parameter as a counter (say
starting at 1500), reduce it within each call, and also check if the
counter reaches zero and exit, or something to that effect. I guess
Python would do something similar. (That's for a specific function,
though, and as I read your example I assume that Python affects all
recursive calls)

My wild imagination assumes there might be some sort of nifty hack
with stack/heap size limit, where you hopefully might get an
std::bad_alloc or so when you reach your recursion limit, but I guess
that would be non-portable.

[TK]

No built-in mechanism that I am aware of.

>
But you could always use an optional parameter as a counter (say
starting at 1500), reduce it within each call, and also check if the
counter reaches zero and exit, or something to that effect. I guess
Python would do something similar. (That's for a specific function,
though, and as I read your example I assume that Python affects all
recursive calls)

My wild imagination assumes there might be some sort of nifty hack
with stack/heap size limit, where you hopefully might get an
std::bad_alloc or so when you reach your recursion limit, but I guess
that would be non-portable.

Thanks for your hints.

o-o

Thomas