Final answer:
It is true that recursion in event-controlled processes might cause a stack overflow if not managed carefully, because it can lead to more function calls than the available memory can support. However, it can still be used effectively with careful planning and optimization.
Step-by-step explanation:
The claim that recursion should not be used with event-controlled processes because it may result in more function calls than the available memory can support is generally true. Recursion involves a function calling itself until a base case is met. In an event-controlled process, which could have a high number of events, recursion might not reach a base case quickly. This delay can lead to a large number of recursive calls accumulating, potentially exhausting the memory stack and causing a stack overflow error if the recursion is not managed carefully or the system's memory limitations are reached.
Nonetheless, recursion can be used effectively if the programmer ensures that the base case is reachable and accounts for the memory limitations; for instance, by setting limits on recursive calls or using tail recursion optimization. Therefore, while it is advisable to be cautious when using recursion in event-controlled processes, skilled programmers can employ strategies to mitigate the potential memory issues.