On Friday, 11 September 2015 at 00:55:41 UTC, Adam D. Ruppe wrote:
On Friday, 11 September 2015 at 00:52:00 UTC, BBasile wrote:
While trying to get why some call to memmove without the right
import didn't lead to a compilation failure i've found that
imported symbols are not private ! Is that
On Friday, 11 September 2015 at 00:52:00 UTC, BBasile wrote:
While trying to get why some call to memmove without the right
import didn't lead to a compilation failure i've found that
imported symbols are not private ! Is that a bug ? The specs
don't say that a selective import is public !
On Friday, 11 September 2015 at 00:55:41 UTC, Adam D. Ruppe wrote:
On Friday, 11 September 2015 at 00:52:00 UTC, BBasile wrote:
While trying to get why some call to memmove without the right
import didn't lead to a compilation failure i've found that
imported symbols are not private ! Is that
While trying to get why some call to memmove without the right
import didn't lead to a compilation failure i've found that
imported symbols are not private ! Is that a bug ? The specs
don't say that a selective import is public !
-- other.d --
module other;
private import core.stdc.string: