Other notes

[BCS]

Reply to bearophile,

> Thank to everyone for the answers and comments.
> 
> BCS:
> 
>> leave that to some sort of "Lint for D"
>> 
> I agree that certain things are better left to a lint (because for
> example a static analysis of the code can be quite slow and complex,
> so it may make the compiler too much slow and complex. And some of
> those things may make its command line too much hairy, and some of
> those things may be a bit controversial), but there are other things
> better left to the compiler (optional integral overflow cheeks,
> warnings issued for unused variables/classes/functions, optional
> accurate pointer/reference cheeks. I think all three of them are quite
> important, and the first two are commonly found in other languages too
> (like Delphi and C#)).
> 
>> I only use real. On most, if not all, systems it's just as fast as
>> double (OK it needs more IO time but...) so why not use it?<
>> 
> Maybe to help the port of D to different not-Intel CPUs, but I am not
> expert about this.

real is defined as the largest hardware supported floating point type. That 
would be /smaller/ than double on a system with only 32bit FP hardware.