DIP22 : Private symbol visibility

Jonathan M Davis jmdavisProg at gmx.com
Thu Jan 31 06:48:58 PST 2013


On Monday, January 28, 2013 18:05:37 Dicebot wrote:
> http://wiki.dlang.org/DIP22
> 
> There are two important issues with current protection attribute
> design:
> 
> * Senseless name clashes between private and public symbols
> * No way to specify internal linkage storage class
> 
> This DIP addresses both of them with two decoupled proposals:
> 
> * Change of private related name resolution rules
> * Definition of static storage class for module-scope symbols.

I see no point to the internal linkage stuff. What we need is for inaccessible 
symbols to not be put in overload sets. I'm not sure that it really needs to 
be any more complicated than that.

- Jonathan M Davis


More information about the Digitalmars-d-announce mailing list