What do you mean by recursive function in C?
 callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables is the process which comes into existence when a function calls a  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables of itself to work on a  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables problem. Any function which calls itself is called recursive function, and such function calls are called recursive  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables. Recursion involves several numbers of recursive calls. However, it is important to impose a termination condition of recursion. Recursion code is shorter than  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables code however it is  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables to understand.
Recursion  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables be applied to all the problem, but it is more useful for the tasks that can be defined in terms of similar  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables. For Example, recursion may be applied to sorting,  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables, and traversal  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables.


What is memory allocation of recursive method?
Each recursive call creates a new  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables of that method in the memory. Once some data is  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables by the method, the copy is  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables from the memory. Since all the  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables and other stuff declared inside function get stored in the  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables, therefore a separate stack is maintained at each  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables call. Once the value is returned from the corresponding function, the stack gets  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables. Recursion involves so much complexity in resolving and  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables the values at each recursive call. Therefore we need to maintain the  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables and track the values of the variables defined in the  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables.


What is garbage value C?
Allocating a variable implies  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables some memory for that  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables. In some programming languages (like C) if a  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables is allocated but  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables assigned, it is said to have a " callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables value" , that is, some  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables that was being held any  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables piece of the computer's  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables.


What is storage classes in C?
A  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables class defines the  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables (visibility) and life-time of  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables and/or functions within a C Program


How many storage classes are there?
Storage  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables in C are used to determine the lifetime, visibility,  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables location, and  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables value of a variable. There are  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables types of storage classes in C
Automatic
External
 callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables
Register


Which storage class is faster?
For faster access of a  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables, it is better to go for register  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables rather than auto specifiers. Because,  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables variables are stored in register memory whereas auto  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables are stored in main  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables memory. Only few variables can be  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables in register  callscannotclassescopyCPUdestroyeddifficultfourgarbageinformationinitialiterativememorynotproblemsrandomRecursionrecursiveregisterremovedreservingreturnedscopesearchingsmallerspecifiersstackStaticstoragestoredsubtaskstrackingvariablevariables.