The current model forces people to 'convince' others to open up
classes for inheritance at the precise point it is necessary. This is
a model which has served, at least, Hadoop very well.
So, I think we should not go make every member protected - rather we
should open them up one at a time,
Making things protected breaks encapsulation, while keeping them
private hampers extensibility. Ideally, we would go through careful
design phases and consider all such issues, coming up with clean
interfaces that allow just enough visibility into reference
implementations of public-facing interfac
Would it be better to make them protected when a use case for
inheritance arises rather than begin as protected?
-Original Message-
From: Dmitriy Ryaboy [mailto:dvrya...@gmail.com]
Sent: Tuesday, February 02, 2010 7:35 PM
To: pig-dev@hadoop.apache.org
Subject: Private variables are not e
