Re: [Deinterlace-discuss] Bugs in scheduling code
Brought to you by:
adcockj,
dschmelzer
|
From: Rob M. <rob...@gm...> - 2007-03-02 02:52:17
|
At 15:37 01-03-07, Radoslav Masaryk wrote: >I thought about it but I don't want to delete m_name and m_name_program >everytime when some Cschedule object is destroyed, just look more >carefully at code...it will lead to error when I copy Cschedule object >to another Cschedule object becouse at the end of function the >destructor is called, so m_name would be removed and original Cschedule >object would have bad pointers...and we don't want to make that happen Maybe it is better to just let the calling code allocate the buffer and pass the pointer? > >What happens if the object is destroyed but clearData is not called? > >Please look to code....I cared about all memory clearing of Cschedule >objects, they frees correctly. >There aren't memory leaks at the moment as I know. But what happens in the future when some code is added? It seems to me that a mistake is easily made. Rob |