D - more or less power than C++?

[Sebastián E. Peyrott]

In article <dudpqv$1otp$1 at digitaldaemon.com>, Hasan Aljudy says...
>The *correct* way of doing it is naming your modules according to the 
>directory structure.
>
>
>----- foo/bar/ff.d ----
>module foo.bar.ff;
>//rest of file
>
>----- foo/gg.d --------
>module foo.gg;
>//test of file
>
>----- rr.d ------------
>module rr;
>//rest of file
>
>now if you want to import rr.d from foo.bar.ff
>
>-----foo/bar/ff.d----
>module foo.bar.ff;
>import rr;
>//rest of file
>
>I think this should work!
>When you compile, you have to make sure that the working directory is 
>where rr.d resides.
>
>
>

I agree. I think there's no compelling reason to allow referencing files
according to the relative path of the current module. In fact, I think the
current behaviour enforces a more organized development structure.

--
Sebastián.