Subj : Re: OO compilers and efficiency
To   : comp.programming
From : Gerry Quinn
Date : Mon Aug 01 2005 03:14 pm

In article <1122842210.201949.196060@g49g2000cwa.googlegroups.com>, 
robert.thorpe@antenova.com says...
> Gerry Quinn wrote:

> Much C-style-C++ still hanging around in programs today dates from old
> requirements for performance.  The C has hung around because no-one has
> had the time or inclination to replace it, or because new programmer
> mistakenly believe it's there for a reason.  In situations like this
> programmer should decide if they're C or C++ programmers and move in
> one way or the other.

If it's not broken, why fix it at all?

> If not, and if you're writing code in C for performance reason then
> it's quite likely that's because it _always_ needs to be fast.  If it's
> a weak requirement that goes away as time progresses it's likely easier
> to write it in C++ anyway and put up with a little slowdown until
> computers get faster.
> 
> If you have a program like this I think it's often wise to isolate the
> performance sensitive part in a separate library or executable.  At the
> very least a clear interface must be created to it, even if it's the
> only clear interface in the whole program.

Certainly, that is the most important thing.

- Gerry Quinn

.