About Go, D module naming

[Andrei Alexandrescu]

On 12/20/12 10:06 PM, bearophile wrote:
> Walter Bright:
>
>> There'd also be a revolt here if circular importing were removed.
>
> I didn't ask for the removal of circular importing. (But I suggest to
> read the rationale of the Go designers.)

I did read the piece and found it surprisingly weak. The problems with 
C's modularity are misidentified. The entire discussion on include 
guards is irrelevant because it's been obsoleted by today's compilers, 
which trivially recognize include guards. The problem of bloated 
includes in C and C++ does exist but its causes are different.

Then, the approach to simplifying smacks of making the lives of the 
implementer easier while passing the buck to the user.


Andrei