www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.ide
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript
electronics



digitalmars.D.learn - Is it intended behavior? (modules / packages)

Recently I've played a little bit with 'package' attribute and found 
something what is a bit strange for me.

I have following directory structure:

root
|-A
| |-module1
|
|-B
   |-module2


It is currently possible to define:

in module1:
---
module A.module1;

import B.module2;
(...)
---

and have in file module2 defined:
---
module A.module2; // please notice package which is different than real.
(...)
---

I like current behavior because module2 have package access to modules 
in package A, but I just wonder if it is not a bug and will be removed 
in future.

BR
Marcin Kuszczak
(aarti_pl)
Apr 30 2008