Darren New wrote:
> Really, Python isn't noticeably less private than C++. C++ shows you 
> everything. The compiler says "don't reference that by name", instead of 
> the IDE doing it.

Or, to phrase it a different way, I've never had a problem caused by someone 
intentionally accessing a private member in a Python-like environment that 
would have been solved by making the code not compile when that happens.

I have never known someone to accidentally reference x._y and think they 
were supposed to be accessing _y as a normal part of the functioning of the 
program.

Have you ever known someone to accidentally name a C function __XYZ__ and 
not be aware they might be stepping on the compiler's namespace? Is it 
really a problem that the compiler doesn't prevent you from using names like 
that?

-- 
Darren New, San Diego CA, USA (PST)
   The question in today's corporate environment is not
   so much "what color is your parachute?" as it is
   "what color is your nose?"

Post a reply to this message