[Issue 313] Fully qualified names bypass private imports

[Derek Parnell]

On Tue, 23 Jan 2007 10:25:56 +0000 (UTC), d-bugmail at puremagic.com wrote:

> http://d.puremagic.com/issues/show_bug.cgi?id=313
> 
> 
> davidl at 126.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> 
> ------- Comment #2 from davidl at 126.com  2007-01-23 04:25 -------
> d 1.0 does correctly report the error message

But is it correct? If the 'std.stdio' is private to "a.d" and not
explicitly imported in to "b.d", then a statement in "b.d" should not be
able to use anything in std.stdio, fully qualified or not.

As far as I'm concerned, D is still broken in this regard as it allows one
to get access to private identifiers just by fully qualifying them. I
believe that private identifies are *private* and thus should not be be
able to be accessed by another module.

-- 
Derek Parnell