Modules named

[AgentOrange]

In article <e1i6gi$14oj$2 at digitaldaemon.com>, Hasan Aljudy says...
>
>Chris Nicholson-Sauls wrote:
>> It isn't perfect, but it appears there is now a way to have modules 
>> named 'object' or at least according to a cheap little test I just ran.  
>> The trick is to explicitly import 'object' in your own 'object'.  Let me 
>> show you what I mean:
>> 
>> # module test;
>> #
>> # private import std.stdio ;
>> #
>> # private import foo.object ;
>> #
>> # void main () {
>> #   FooObject foo = new FooObject ;
>> #   writefln("%s", foo.toString);
>> # }
>> 
>> # module foo.object;
>> #
>> # import object;
>> #
>> # class FooObject : Object {
>> #   public char[] toString () { return "<<FooObject>>"c; }
>> # }
>> 
>> This compiles and runs fine for me, DMD 0.153 on Windows.
>> 
>> -- Chris Nicholson-Sauls
>
>but this module is foo.object, which is totally different from object.
>
>There shouldn't be a problem with creating a module foo.object, it 
>wouldn't conflict with object anyway. At least that's what I think.


I think the original problem was you cannot declare a class with the name Object