W
Wojtek
Roedy Green wrote :
The good thing abbout namespaces is that they allow for better
organization of application function. And (in Java) they also allow for
information hiding via the default modifier.
Ah but the human does know the context. Am I showing stuff on the
screen, or am I storing information. Different operations.
Don't know what you mean by "local". I have many tens of packages (um,
namespaces). Each has a Data class which is passed around by other
classes in the same package (Command, SQL, Validator, the servlet). Is
the Data class "local"? Yet it is marked as public because the JSP
needs to use it.
The problem with namespaces is they resolve the ambiguity for
computers, but not for humans.
The good thing abbout namespaces is that they allow for better
organization of application function. And (in Java) they also allow for
information hiding via the default modifier.
Humans are often confused if you mean java.util.List or java.awt.List.
It is best to avoid reusing names because of the way the human brain
works.
Ah but the human does know the context. Am I showing stuff on the
screen, or am I storing information. Different operations.
Namespaces are a safety feature. You should try to avoid reusing the
same name in different contexts, with a number of exceptions for some
common "local" names.
Don't know what you mean by "local". I have many tens of packages (um,
namespaces). Each has a Data class which is passed around by other
classes in the same package (Command, SQL, Validator, the servlet). Is
the Data class "local"? Yet it is marked as public because the JSP
needs to use it.