3 ms·
> Flipping a "private:" to "public:" has no effect on the binary compatibility. That's not the case on Windows. The access qualifier is part of the mangled nam
by slavik81 7y ago
> Flipping a "private:" to "public:" has no effect on the binary compatibility.
That's not the case on Windows. The access qualifier is part of the mangled name. https://en.wikiversity.org/wiki/Visual_C%2B%2B_name_mangling#Basic_Structure https://en.wikiversity.org/wiki/Visual_C%2B%2B_name_mangling...
- kazinator 7y agoThat shouldn't prevent the subversion of data members or inline functions, or the ability to add your own member functions to the class.
- bdowling 7y agoIt's still an honor system. There's a way to generate code that will call the "private" or "protected" data/function even if it violates what's specified in the headers.