[interfacekit] Re: Header issues

>
>"Marcus Overhagen" <ml@xxxxxxxxxxxx> wrote:
>> Fortunately, there are not many classes with a missing destructor.
>> Unfortunately, BFont has a problem.
>
>Dano's BFont used a UseModernFonts() call to tell BFont that you know 
>about the destructor - not really nice, though.
>I think we better keep R5 compatibility and redo this for R2 when we'll 
>switch to gcc 3 (and provide a new set of libraries).
I was not immediately aware that adding a destructor would break binary 
compatibility. Thanks for pointing that out, Marcus. After looking at the 
code again, I've figured out a way to utilize most of what is allocated to 
the heap without implementing a destructor. Changes will be made to the 
sources when I get around to it.

--DW

Other related posts: