[Issue 3254] Module member visibility depends on declaration order

d-bugmail at puremagic.com d-bugmail at puremagic.com
Thu Aug 20 00:03:28 PDT 2009


--- Comment #4 from Sobirari Muhomori <maxmo at pochta.ru>  2009-08-20 00:03:27 PDT ---
(In reply to comment #3)
> My guess is that the point is to protect against accidental behaviour changes
> if some code is moved between modules.
The code moved, it moved from one module to another. The accidental behavior
change still can happen in the module the code moved to. If there was public
foo(int), the module used to call it, then private foo(float) appears and the
module silently starts to call it.

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