>when it is necessary to include a return statemnt in one's code
When you're returning from any function whose return type is not void.
>what is the difference between recursion and iteration?
At what level? At the highest level, there's no difference. Go a bit lower and recursion is just a more flexible form of iteration. Go down to the client level and recursion is a series of nested function calls while iteration is just a glorified goto loop. Go even deeper and recursion is an execution stack where stack frames are piled on top of each other and the instructions that operate on each frame happen to be the same while iteration is nothing more than conditionally jumping around the same instructions within one stack frame.
A loop can repeat a series of instructions only if each iteration immediately follows the previous one right? But in case of recursive functions, you can call the function at any point of the program and the series of instructions will be executed right? So can you say that the point I made is the difference between them?
>So can you say that the point I made is the difference between them?
No. I don't see how the two statements describe a difference unless you're adding the restriction that only one loop can be used ever and it can't be placed in a function.
I am working creating a fully encapsulated, homogeneous singly linked data structure. The Listing class and SinglyLinkedList class that are part of the whole application compile fine, but the problem ...