On Thu, Jan 29, 2004 at 09:16:33AM -0800, Jeff Clites wrote: > > >Then the question becomes, "What about namespace clashes?", which Tim > >has already addressed. > > We could certainly do some sort of language-specific prefixing, as Tim > suggested, but it seems that we are then going to trouble to unify, > only to immediately de-unify. Certainly, a random Java programmer > shouldn't have to worry about naming a class so that it doesn't > conflict with any class in any other language in the world--that's > silly, especially since this Java programmer may not even know about > parrot.
I think you missed the part where I said that each language has it's own root which is actually below the root of the unified namespace. The namespaces of other languages are reached via a backlink/symlink kind of thing so they appear to be within the namespace of the language being used. > it seems natural to instead just use that class name as I would expect > it to be written--"java.lang.String" for Java, for example. In Java you would write "java.lang.String", naturally, and in Perl you'd write "parrot::java::java.lang.String". As per the example I gave previously. Take another look. Tim.
