Time to destroy Walter: breaking modules into packages

Jonathan M Davis jmdavisProg at gmx.com
Tue Jun 18 23:46:46 PDT 2013


On Wednesday, June 19, 2013 08:25:00 TommiT wrote:
> > If it's worth letting nested packages have access to their
> > parent packages package-level stuff, then
> > let's just do that for everything.
> 
> But this is not enough. Let's say you have modules A.d and B.d
> under the same package. Now, if A.d uses something that is marked
> 'package' inside B.d, you can't break both A.d and B.d into these
> new module-package thingies without re-structuring your code.

Then just put whatever is supposed to be shared between them in the package 
that they were both in originally. package stuff is not part of the public API, 
so when you're refactoring package code, you're refactoring code that you own 
entirely, so it shouldn't be an issue if you have to rearrange it a bit, 
especially since it's all localized to a single package by definition. It's 
only when something is part of a public API that refactoring becomes a 
problem.

- Jonathan M Davis


More information about the Digitalmars-d mailing list