Question

because obj, the playingCard object is created inside a nested for loop does that mean after the second for loop completes, obj gets deallocated from the stack each time?

and a small side question,
does a compiler use the stack (similar to recursion) to keep track of loops and nested loops?

    for(int c = 0;c<nElems;c++) {
    for(int z = c + 1;z<nElems;z++) {
            playingCard obj;


        }
    }

Answer 1

It gets constructed and deconstructed every iteration.

However, on the stack, the concept of allocation is (for at least VS and GCC) more hazy. Since the stack is a contiguous block of memory, premanaged by the compiler, there’s no real concept of allocating and deallocating in the way that there is for heap allocations (new/delete or malloc/free). The compiler uses the memory it needs on the stack, and simply rolls back the pointer later on.