-- [ Picked text/plain from multipart/alternative ] Well, the difficulty here is, where are good points to place the checkpoints?
There were some errors with guns derived from _BaseWeapon. So I thought about placing one in the constructor and placing one in the destructor. But even then I get memleaks. (prolly from other classes which memory isn't cleaned up yet?) And what do you mean by: "sometimes is hard to understand you clean up in destructors." ? Thanx for your answer At 19:55 24/03/2003 -0600, you wrote: >Quoting Steven Van Ingelgem <[EMAIL PROTECTED]>: >you may allready know this, but the way you use _CrtDumpMemoryLeaks(); is you >call it right before you delcare the questionable memory.. make sure it shows >no leaks and if there are any, they are prolly ones valve made that they will >clean up later, then call it right after you allocat the mem >_CrtDumpMemoryLeaks >(); > >it will show you all the leaks you just made, then later on in your progie, >call it right after you clean up the questionable mem.. and all thoes leaks >should go away. >sometimes is hard to understand you clean up in destructors. > >example: >_CrtDumpMemoryLeaks(); // no leaks >int* p = new int >_CrtDumpMemoryLeaks(); // LEAK DETECTED 4 bytes >delete p; >_CrtDumpMemoryLeaks(); // no leaks; > >if you dont delete p, the leak will remain. > >again, not sure if that helps you :( >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, >please visit: >http://list.valvesoftware.com/mailman/listinfo/hlcoders G00fy, (aka KaReL, aka Steven) Main Webpage : http://komma.cjb.net CQ Database : http://lid.fragland.net/ ICQ # : 35217584 MSN : [EMAIL PROTECTED] -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
