How does D improve design practices over C++?

[mgen]

I would argue using it as a debugger for dependency reasons is bad practice but using it to test smaller modules is good practice, but on a side note its a waste to not have the compiler running if you are not using up resources doing something else while coding (then its like a free check on yourself that takes no time if you glance when it is done). That way I get the info for minimal price and sometimes that info is very usefuly, after writing 1000 lines of code I would be worried about debugging if it was not segmented out in steps as I coded it.

Tony Wrote:

> 
> "Jarrett Billingsley" <jarrett.billingsley at gmail.com> wrote in message 
> news:mailman.356.1226010025.3087.digitalmars-d at puremagic.com...
> > On Thu, Nov 6, 2008 at 5:01 PM, Jarrett Billingsley
> > <jarrett.billingsley at gmail.com> wrote:
> >> On Thu, Nov 6, 2008 at 4:18 PM, Tony <tonytech08 at gmail.com> wrote:
> >>> Compile times as I am not doing large scale development. And with so 
> >>> much
> >>> processor power available these days, I really don't see a problem with
> >>> compile times. Some care in laying out code and headers goes a long way.
> >>
> >> Boost.
> >
> > I did also want to make another point about this.  Processors are not
> > getting that much faster; it's not 2001 anymore.  We've pretty much
> > hit the wall for single-core performance, and compilation is an
> > extremely difficult problem to parallelize.  Yes, you can compile
> > multiple files at once, but if a single compilation unit takes 20
> > minutes to compile, it doesn't matter how many cores you've got.  The
> > shortest compile time you can get is 20 minutes.  Even if your
> > compiles are "only" three minutes, if you spend three minutes
> > compiling, followed by ten minutes of testing, that means you're
> > spending almost a quarter of your time compiling.  That doesn't seem
> > like an efficient use of time.
> 
> I have designed/coded for months without ever pressing the compile button. 
> Some programmers use the compiler in a very iterative way: using it as a 
> debugger is bad practice.
> 
> Tony 
> 
>