The same would go for java (IMHO). if you are just going to do simple stuff, then no, you don't need access modifiers. if you are going to do anything even REMOTELY beyond a basic program, then yes.
If you are saying that access modifiers are necessary to write complex programs, Smalltalk programmers will disagree. In Smalltalk all methods are automatically public, and all fields private. And Smalltalk is known to be quite appropriate for complex programs.
I'd still say that to be taken seriously as a Java programmer, you will need to at least understand how they work.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
First I'll like to thanks for your interest. I anticipate this answers and I agree with everything. I come on this (strange) questions after some endless discussions with some of the "visual" developers, this people are used to use smart IDES where everything is pink, or at least it looks like. This is a classical case where a tool changes quick from a bless in to curse and this without the victim can check something. Even if you try use the theory like argument they have the "look it works" argument. What arguments can I bring in this kind of dispute ? What you guys think about ?
Regards, M [ April 24, 2008: Message edited by: Mihai Radulescu ]