G
gein.julien
Hi,
I'm currently working with a rather old library which declares a member
of a parent class as private while it should be protected. The library
then provides macros for the child classes that internally refer to
this private member (I'm not making a wrong use of the library). I was
working with VC6 before and this problem did not show up (the compiler
had a wrong behaviour regarding private static members). Now that I'm
working with VC7, I need to get rid of this problem...
I cannot change the header file where the private member is declared,
so I was wondering if there is a mecanism to hack the compiler
behaviour (though I admit it's bad...)
Any help appreciated !
-- B --
I'm currently working with a rather old library which declares a member
of a parent class as private while it should be protected. The library
then provides macros for the child classes that internally refer to
this private member (I'm not making a wrong use of the library). I was
working with VC6 before and this problem did not show up (the compiler
had a wrong behaviour regarding private static members). Now that I'm
working with VC7, I need to get rid of this problem...
I cannot change the header file where the private member is declared,
so I was wondering if there is a mecanism to hack the compiler
behaviour (though I admit it's bad...)
Any help appreciated !
-- B --