Re: Problem with coupling shared object symbol visibility with protection

[Dicebot via Digitalmars-d]

I like the first version more as it fits better the natural way 
people design their interfaces and reduces attributed noise. 
Can't say if it will trigger some hidden issues.

First version also fits better some of ideas I had about 
automated API generation/verification 
(http://forum.dlang.org/post/otejdbgnhmyvbyaxa...@forum.dlang.org)

Thanks for keeping to poke this issue - symbol visibility is 
currently a big undefined minefield in D ABI.