View mode: basic / threaded / horizontal-split · Log in · Help
January 10, 2007
import foo vs. private import foo
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
Re: import foo vs. private import foo
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
Re: import foo vs. private import foo
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
Re: import foo vs. private import foo
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?
Top | Discussion index | About this forum | D home