> Flipping a "private:" to "public:" has no effect on the binary compatibility. ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		slavik81 on June 12, 2019 \| parent \| context \| favorite \| on: C++ Patterns: The Badge > 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...

bdowling on June 12, 2019 | [–]

It'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.

kazinator on June 12, 2019 | [–]

That shouldn't prevent the subversion of data members or inline functions, or the ability to add your own member functions to the class.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact