> Eh? I taught C programming at university. Never had any 
> 5-line function 
> rubbish. I do remember penalising students for functions > 80 
> lines though.
What I mean is that it is hard to define rules for good code, just as it
is hard to define rules for good art.  You can have rules of thumb, like
less than 80 lines, or composition in a photo should balance - but it is
hard to have really strong rules.  Ie, the "no goto" rule - I
occasionally break it because it makes the code better.

> Java is the successor to C++.

Huh?  Sorry I don't believe that Java can contend as a serious language
for operating system development, driver development, or really anything
that involves talking to the silicon.  Unless Java has changed a heck of
a lot since I learned it at uni (well, that was almost 6 years ago...),
it is only useful for pure software apps.

> D will always remain niche.
> It's just too late to the party.

It might be too late to the party, but I think that it is a much better
fit as a replacement for C++ than Java being a replacement for C++.

Cheers
Brad

Reply via email to