Once Again, Feature Request: Nested classes in separate scope

[Regan Heath]

downs wrote:
> Okay, let's drop the ownership debate and reformulate the problem to
> expressing that class Bar exists in the _context_ of class Foo.
> I agree that this relationship could be modelled by "class Foo { Bar
> context; alias context this; " as proposed before, but isn't this
> exactly what nested classes are supposed to be? Things that only exist
> in the context of something else? I simply think it would be better to
> extend this existing feature to allow Foo to be in a separate scope from
> Bar, instead of using what essentially amounts to a workaround.
> Nonetheless, thanks for your reply. :)
>  --downs

I'm not sure I understand the "seperate scope" requirement, what's wrong 
with:

--[windowmanager.d]--
module windowmanager;

class WindowManager
{
	class Window
	{
		private this()
		{
		}
	}

	Window[] children;
	
	Window createWindow()
	{
		children ~= new Window();
		return children[$-1];
	}
}

--[windowmanager_main.d]--
module windowmanager_main;
import windowmanager;

void main()
{
	auto m = new WindowManager();
	auto w1 = m.createWindow();
	auto w2 = m.createWindow();
	auto w3 = m.new Window();  //this is not accessible
}

Is the problem that you need to allow users to derive custom window 
types from Window?  I'm not sure if it's possible to derive from an 
inner class or what the syntax would be if it was...

Regan