Thread overview
import foo vs. private import foo
Jan 10, 2007
jicman
Jan 10, 2007
Brad Roberts
Jan 10, 2007
Hasan Aljudy
Jan 10, 2007
Hasan Aljudy
January 10, 2007
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
January 10, 2007
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
January 10, 2007

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.
January 10, 2007

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?