Re: Namespaces contiguous in the entirety

Replies are listed 'Best First'.
Re^2: Namespaces contiguous in the entirety by rir (Vicar) on Sep 28, 2005 at 13:47 UTC
That is one way to look at it. I think it is more accurate to view it this way: The first `package specific_name` statement creates a namespace and enters it. Subsequent invocations simply reenter the namespace. Having had the challenge of trying to explain the difference between C declarations and definitions to newbies; I can see how losing the distinction in dwimery would appeal as design choice for a higher level language. My reply above to tanktalus gives more of my reason to view it this way. Be well, rir	[reply] [d/l]
Re^3: Namespaces contiguous in the entirety by broquaint (Abbot) on Sep 28, 2005 at 15:32 UTC
The first package specific_name statement creates a namespace and enters it. Subsequent invocations simply reenter the namespace. While you may view that as conceptually accurate, that is not really what happens, hence my confusion above. I don't think I've ever come across this being an issue, not least because I would imagine that if you called code on a class you thought had declared, when in fact you had redeclared an existing class, something would break rather loudly. I can't think of any obvious way to do this within `perl`, but as you say, it would probably fairly simple just to hack the `perl` source and recompile. HTH `_________ broquaint`	[reply]
Re^4: Namespaces contiguous in the entirety by diotalevi (Canon) on Sep 28, 2005 at 15:42 UTC
The obvious way is to examine all the COP nodes in the compiled program and see that packages don't appear in multiple files. This is test should fit inside of a few lines.	[reply]


There's more than one way to do things
	PerlMonks