Is deconstructers bad :S ?

[Lil Margin]

Hey ya'll,
I notice that when i use a deconstructer it automatically gets called at startup of the code generation thingy...
so my question is : if it destructs at startup, why use it :S ?

[Acki]

hu ???
the destructor should only get called when you destroy the object but the constructor when you create the object !!!
and both are often usefull and needed...

I guess there is something wrong with your code...

[Lil Margin]

no lol its not my code, make a class of the irrlicht device.
create it in the constructor and drop it in the deconstructer, then when you usally call of device-drop() call the deconstructer...and you will get an unhandeled exception.

[Sylence]

Code: Select all

class A
{
   IrrlichtDevice* Device;

public:
   A()
   {
       cout << "A()" << endl;
       Device = createDevice();
   }

   ~A()
   {
       cout << "~A()" << endl;
       if( Device ) Device->drop();
   }
};

int main()
{
   A a;

   return 0;
}

Should work. Maybe you can show some code ?

[CuteAlien]

deconstructer... I'm never going to get that word out of my mind now!

The rule for Irrlicht is - only call drop() when you created with a function starting with create, when you used new or when you did a grab().

[Lil Margin]

@Sylence my code is familiar to yours...

@CuteAlien, so a deconstructer doesn't work...right?

[randomMesh]

There is no such a thing as 'deconstructer'.
Please read up on destructors.

[Lil Margin]

hahahaha destructer, lol funny me XD

[Acki]

hahahaha destructer, lol funny me XD

I thought my post nade this clear, but maybe it was a litle bit too subtile...