• Dan (21/21) Oct 16 2012 According to the spec, private module members are equivalent to
• bearophile (6/7) Oct 16 2012 It looks like a compiler bug/hole. DMD is not yet aligned to its
• Dan (8/15) Oct 16 2012 Thanks. I had assumed my interpretation was incorrect and was
• Oleg Kuporosov (4/11) Oct 18 2012 This is fixed issue in D2.061 alpha, but not in D1.

"Dan" <dbdavidson yahoo.com> writes:

According to the spec, private module members are equivalent to 
static
declarations in C programs. Why does this work (i.e. print 5)?
Both imported.d and sample.d are in same directory 
(.../attributes).

Thanks
Dan

----------------------------------------------------------------------
import std.stdio;
import play.education.attributes.imported;

void main() {
   WhyIsAccessible s;
   writeln(s.x);
}
----------------------------------------------------------------------
module play.education.attributes.imported;
private:
struct WhyIsAccessible {
   int x = 5;
}
----------------------------------------------------------------------

"bearophile" <bearophileHUGS lycos.com> writes:

Dan:

 Why does this work (i.e. print 5)?

It looks like a compiler bug/hole. DMD is not yet aligned to its 
specs...

Is it in Bugzilla?

Bye,
bearophile

"Dan" <dbdavidson yahoo.com> writes:

On Tuesday, 16 October 2012 at 19:31:45 UTC, bearophile wrote:
 Dan:

 Why does this work (i.e. print 5)?

 It looks like a compiler bug/hole. DMD is not yet aligned to 
 its specs...

 Is it in Bugzilla?

 Bye,
 bearophile

Thanks. I had assumed my interpretation was incorrect and was 
just looking for an explanation. Honestly, until just now, I have 
not explored bugzilla. There is bug 1141 which looks like what 
I'm asking about and references a newer one 2830 which looks 
exactly like the issue.

Thanks
Dan

Oleg Kuporosov <oleg.kuporosov gmail.com> writes:

Is it in Bugzilla?

 Bye,
 bearophile

 Thanks. I had assumed my interpretation was incorrect and was just looking
 for an explanation. Honestly, until just now, I have not explored bugzilla.
 There is bug 1141 which looks like what I'm asking about and references a
 newer one 2830 which looks exactly like the issue.

This is fixed issue in D2.061 alpha, but not in D1.

Thanks,
Oleg.