Problem with coupling shared object symbol visibility with protection

[Benjamin Thaut via Digitalmars-d]

Am 31.01.2015 um 06:11 schrieb Dicebot:
> On Friday, 30 January 2015 at 19:10:06 UTC, Martin Nowak wrote:
>
> It has a serious drawback of increasing attribute noise even more
> though. First approach allows for more automatic inference.
>
> But with D restrictions it seems the least bad option.

Well, export is going to remain transitive. So the first approach is 
still going to work. The only difference is going to be that you can 
"force export" private declarations. So for most modules it is hopefully 
going to be enough to put "export { }"  around the public part of the 
module and force export some of the needed private declarations. For a 
module without templates a single "export { }" should be enough.