Encapsulation with local and protected: Pitfalls

Pitfalls and red flags

• Making fields public for convenience and later losing control over invariants.

• Using local where subclass customization is required, then adding unsafe public workarounds.

• Using protected for data that should never be touched by child classes.

• Exposing raw handles through getters and allowing uncontrolled mutation outside.

Related topics

• Back to Encapsulation with local and protected