Module-level accessibility

[Sergey]

Hi bearophile,

you've just cheered me up :-) I'll proceed doing my best to get closer to  
this language.
By the way, if it's not difficult for you, could you please clarify the  
following:

1) what did you mean by "far worse bugs" :-) just several examples
2) Andrei Alexandrescu wrote in his book that it's possible to make  
non-final methods of interfaces private, and then override them in derived  
classes. There are even examples in his book that demonstrate this. At the  
same time, current DMD documentation pretty clear says that nothing  
private can be overridden.

Best regards,
Sergey.

On Mon, 04 Oct 2010 14:03:14 +0300, bearophile <bearophileHUGS at lycos.com>  
wrote:

> Sergey:
>
>> But such serious bugs that are not fixed yet can disgust any  
>> programmer, I think.
>
> That's a mild bug :-) You can live with it, until it's fixed. There are  
> far worse bugs in DMD now. You can't ask the implementation of a new  
> language to be bug-free. Especially a language that has grown so quickly.
>
>
>> All the more beginning programmers, like me. Probably D2 implementation  
>> is
>> not grown-up enough yet to be used in projects of a real importance...
>
> It's a bootstrap situation: bug get found and fixed while people write  
> larger and larger programs, and people are able to write larger programs  
> because bugs get fixed. At the moment is wrong to use D2 for  
> live-or-death situations, for systems where reliability is critical. But  
> as it gets debugged more and more the scope of its usability will grow.  
> D is designed to eventually be a reliable language, more than C :-)
>
> Bye,
> bearophile


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/