On xDebug they limit how many times a function can be nested, are there any disadvantages of nesting functions for so many times?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
On xDebug they limit how many times a function can be nested, are there any disadvantages of nesting functions for so many times?
Yes.
Each time you call a function from within another function, you add one level to the stack.
The past function calls have not yet returned, so the memory they claimed for local variables cannot be deallocated; it remains resident until the whole stack is unwound.
Imagine you were to throw an exception from inside a function 1,000 calls deep. In order to generate a stack trace, it would have to walk upward through 1,000 function calls, putting them all into the exception object.
There’s nothing you can do with recursion that deep which you couldn’t do instead with a well-written loop, and the loop would be both more memory-efficient (as it doesn’t have to have the stack frame overhead for each function invocation) and time-efficient (as it doesn’t have the overhead of actually performing the function calls you removed).
It is exceedingly unlikely that a program which reaches a recursion level of 1,000 is behaving as intended. More likely, it’s stuck in infinite recursion and will eventually exhaust all the system’s RAM. Better to kill it earlier.