Any performance reason to put attributes protected/private?

Question

I \"learned\" C++ at school, but there are several things I don\'t know, like where or what a compiler can optimize, seems I already know that inline and

Answer 1

The teachers were right to tell you to use private and protected to hide implementation and to teach you about information hiding instead of propsing questionable performance optimizations. Try to think of an appropriate design first and of performance second, in 99% of the cases this will be the better choice (even in performance critical scenarios). Performance bottlenecks can appear in a lot of unpredicted cases and are much easier to come by if your design is sound.

To directly answer your question however: any reduction in scope may help the compiler to do certain optimizations, form the top of my head I can not think of any however right now in regards to making members private.

Answer 2

No. Making members private or protected is not going to provide any performance benefits; of course, the benefits to your design (information hiding) are huge.

Answer 3

There's no such thing as public, private and protected once your code is compiled, so it cannot affect performance.

There's also no such thing as const in machine code (except perhaps ROM), but the compiler can make some logical optimisations to your program by knowing whether a value can change (in some situations).

inline rarely has any effect. It is merely a suggestion to the compiler, which the compiler is free to ignore (and often does). The compiler will inline functions as it sees fit.