[Issue 314] Static, renamed, and selective imports are always public

d-bugmail at puremagic.com d-bugmail at puremagic.com
Thu Aug 20 11:57:16 PDT 2009


Stewart Gordon <smjg at iname.com> changed:

           What    |Removed                     |Added
                 CC|                            |smjg at iname.com

--- Comment #10 from Stewart Gordon <smjg at iname.com>  2009-08-20 11:57:14 PDT ---
(In reply to comment #7)
> Access protection is defined to happen after lookup and overload resolution.

Defined where in the spec?

> Making private symbols invisible defeats this,

Would it be reasonable to change it as I described in the final paragraph of
issue 3254 comment 3?

> and also doesn't work as the
> overload list is a linked list, and making the head of it private would hide
> the rest of the possibly public overloads.

That's obviously an implementation issue.  Possible ways to deal with this:

(a) have multiple linked lists, one for each protection attribute
(b) build the linked list in such a way that the head element will always be
one of the ones of the most public access level that exists among the overloads

Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

More information about the Digitalmars-d-bugs mailing list