On 9/5/14, 2:57 AM, bogun.dmit...@gmail.com wrote:
> This is more or less the way I am leaning. In the next version of bash,
> it
> will be possible to set a limit on the number of recursive source/. or
> eval
> calls at compile time. This will be accomplished by changing a define in
> config-top.h. There will be no limit enabled by default.
>
> Why "define"? Why not variable like "FUNCNEST" for functions? Most part of
> this mailing list tell me about inadmissibility any limits in gnu soft...
> And SIGSEVG in interpreter is only end user problem. An here is limit on
> compile time. :)
I don't particularly like the proliferation of variables for this purpose.
The presence of a define that a user can enable at compile time (which is
not defined by default) is consistent with the philosophy that GNU
software should have no builtin limits. That philosophy does not say that
a user cannot impose such a limit on himself.
Any programming language can be made to produce errors such as the SIGSEGV
you saw if a programmer is willing to put in the effort. Systems have
limits.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
