• jicman (9/9) Jan 09 2007 Greetings!
• Brad Roberts (6/22) Jan 09 2007 The change logs make for a good starting point to answer this sort of
• Hasan Aljudy (3/28) Jan 09 2007 I think it would've been easier to just answer the question, and *then*
• Hasan Aljudy (2/18) Jan 09 2007 The suggestion was accepted, imports are now private by default.

jicman <cabrera__ __wrc.xerox.com> writes:

Greetings!

A few months ago, there was a discussion in the newsgroup about
making all imports private.  Meaning that,

import foo;

would be treated by the compiler as,

private import foo;

Am I way off base?

thanks,

jic

Brad Roberts <braddr puremagic.com> writes:

jicman wrote:
 Greetings!
 
 A few months ago, there was a discussion in the newsgroup about
 making all imports private.  Meaning that,
 
 import foo;
 
 would be treated by the compiler as,
 
 private import foo;
 
 Am I way off base?
 
 thanks,
 
 jic

The change logs make for a good starting point to answer this sort of 
question:

     http://www.digitalmars.com/d/changelog.html#new0163

Later,
Brad

Hasan Aljudy <hasan.aljudy gmail.com> writes:

Brad Roberts wrote:
 jicman wrote:
 Greetings!

 A few months ago, there was a discussion in the newsgroup about
 making all imports private.  Meaning that,

 import foo;

 would be treated by the compiler as,

 private import foo;

 Am I way off base?

 thanks,

 jic

 
 The change logs make for a good starting point to answer this sort of 
 question:
 
     http://www.digitalmars.com/d/changelog.html#new0163
 
 Later,
 Brad

I think it would've been easier to just answer the question, and *then* 
posting the link?

Hasan Aljudy <hasan.aljudy gmail.com> writes:

jicman wrote:
 Greetings!
 
 A few months ago, there was a discussion in the newsgroup about
 making all imports private.  Meaning that,
 
 import foo;
 
 would be treated by the compiler as,
 
 private import foo;
 
 Am I way off base?
 
 thanks,
 
 jic

The suggestion was accepted, imports are now private by default.