Thread overview |
---|
July 20, 2004 compiler still uses private imports out of scope | ||||
---|---|---|---|---|
| ||||
please... ########### ### exemple 1 - two modules ########### // file ImpA.d private import std.string; class A { } void main() { } // file ImpB.d private import ImpA; class B { void foo() { std.string.split("Hello there"); } } ########### ### exemple 2 - two modules ########### // file ImpA.d class A { private import std.string; } void main() { } // file ImpB.d private import ImpA; class B : A { void foo() { std.string.split("Hello there"); } } Ant |
July 20, 2004 Re: compiler still uses private imports out of scope | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | I know that if you use explicit qualification of a name, it will find it despite it being in a private module. It is a bug, but I think it is a low priority since it has to be done deliberately, and it doesn't break anything. |
October 06, 2004 Re: compiler still uses private imports out of scope | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | When trying to compile my applications on windows the compiler found a missing import that the linux version didn't. i.e. it compiles on linux but it fails in windows until the import is added. Ant |
Copyright © 1999-2021 by the D Language Foundation