On Sat, 12 Feb 2005, Michael Walter wrote:

> > And I disbeleive the "makes it easier with large programs" statement.
> I was talking about that it's easier to write a > 1,000,000 line
> program (possibly partially) with GC than without GC.

OK.  I misunderstood you.  Sorry.

> > Very small functions, yes.  But it's less of an optimization than people
> > think, and (especially in C++) it gets way overused.
> I don't think so. From my experience basically noone is using
> __forceinline except for "very small functions" (on a probably mislead
> attempt to outsmart the compiler), and everyone lets the compiler
> decide which functions to inline.

You've had better experiences that I have, obviously.  I've met one too 
many programmers who said, in effect, "inlining a function makes it go 
faster, so I try to inline lots of my functions!"

> 
> What I'm saying is that choosing a language is a tradeoff, and the
> kind of tradeoff C++ gives you can be a very good one (if not the
> best) for particular problem domains. You can see evidence for such a
> domain in the time spent on improving already very good compilers :-)
> 

Actually, most of the time was spent improving the C compiler.  And, 
inthe case of Intel, IBM, etc., the Fortran compiler (less so with GCC).   
The C++ compiler got brought along for the ride.  There are good 
historical reasons why Ocaml doesn't use the GCC back end, but it'd be an 
interesting experiment to port Ocaml to the GCC back end and see how well 
it'd do.  Were I to write a new language, I'd definately target the GCC 
backend.

Brian