On 02.07.2012 20:57, Chet Ramey wrote:
On 7/2/12 2:36 PM, Jan Schampera wrote:
The origin of this all was a "bugreport" to me about the manual lying about
no limits on recursion
That's funny.
Aye. A bit of confusion.
--
Be conservative in what you do, be liberal in what you accept from oth
On 7/2/12 2:36 PM, Jan Schampera wrote:
> The origin of this all was a "bugreport" to me about the manual lying about
> no limits on recursion
That's funny.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS,
On 02.07.2012 15:57, Eric Blake wrote:
Look for FUNCNEST variable. In recent release it is available.
I more meant the shell interpreter, less the code I can write.
It would be possible to link bash with libsigsegv to install a graceful
stack overflow handler that allows a nicer exit message
On 07/01/2012 07:51 AM, Jan Schampera wrote:
> On 01.07.2012 14:37, Roman Rakus wrote:
>
>> Look for FUNCNEST variable. In recent release it is available.
>
> I more meant the shell interpreter, less the code I can write.
It would be possible to link bash with libsigsegv to install a graceful
st
On 01.07.2012 14:37, Roman Rakus wrote:
Look for FUNCNEST variable. In recent release it is available.
I more meant the shell interpreter, less the code I can write.
--
Be conservative in what you do, be liberal in what you accept from others.
- jbp, master of the net, in RFC793
On 07/01/2012 02:03 PM, Jan Schampera wrote:
Hi folks,
a suggestion about recursive function calls (and not only that, of
course).
Do you see a way for Bash to pull the emergency break before it runs
out of stack here (to provide an error to the user, rather than a crash):
---
Hi folks,
a suggestion about recursive function calls (and not only that, of course).
Do you see a way for Bash to pull the emergency break before it runs out
of stack here (to provide an error to the user, rather than a crash):
f1() {
f1
}
f1
Cu
