Will using goto cause memory leaks?

Question

I have a program in which i need to break out of a large bunch of nested for loops. So far, the way most people have been telling me to do it is to use an ugly goto in my co

Answer 1

Goto is not always bad, but in your case you probably shouldn't be using goto.

See examples of good use of goto here and here.

If you goto a label that is outside of scope your object on the stack will be freed.

Example:

#include 
using namespace std;

class A
{
public:
  ~A() 
  {
     cout<<"A destructor"<

This will print:

Inside scope
A destructor
After l label