Time to destroy Walter: breaking modules into packages

TommiT tommitissari at hotmail.com
Wed Jun 19 23:45:21 PDT 2013


On Thursday, 20 June 2013 at 05:24:12 UTC, TommiT wrote:
> This is how I see the logic of this new feature you're adding:
>
> When you have a folder named "mod" which contains a file named 
> package.d, the mod folder becomes conceptually a file with same 
> name and the extension "d". I.e. the folder conceptually 
> becomes a module, which you can then import to other modules. 
> All the code contained within all the files contained within 
> the mod folder becomes conceptually the content of this 
> imaginary mod.d file. Therefore it is only logical that all the 
> code within this imaginary mod.d file would have access to 
> 'package'-labeled symbols that are in files which are located 
> under the same folder under which this imaginary mod.d file is.

...and following that thread, I would also argue, that 
'private'-labeled symbols in files that are inside this mod 
folder should be accessible to all the other files that are 
inside this mod folder, because conceptually all those files are 
part of the same (imaginary) module (mod.d).


More information about the Digitalmars-d mailing list