import concerns (C++ visib question)

[Walter Bright]

Bruno Medeiros wrote:
> Well, that clearly states that private members should not be invisible 
> in C++, but I'm having trouble understanding why. He says "Without it, 
> private out-of-class member declarations become impractical to parse in 
> the general case." but I don't see how or why, anyone has an example or 
> clarification?

I don't understand that, either.

My best guess is that getting consistent overloading results when 
changing protections was deemed by Bjarne to be less surprising, but I'm 
just guessing.