Re: Is C/C++ the future?

[mfeldman@seas.gwu.edu (Michael Feldman)]

In article <DAG.94Nov2083525@bellman.control.lth.se>,
Dag Bruck <dag@control.lth.se> wrote:
>>>>>> "MF" == Michael Feldman <mfeldman@seas.gwu.edu> writes:
>
>MF> I wasn't really thinking of cases like this, rather of situations
>MF> where programmers in industry _know_ they are writing plain C and
>MF> passing it off as C++.
>
>Maybe this characterization isn't entirely fair.

Of course it's not. It was meant mostly as an ironic joke.

>When converting an organization from C to C++, the conservative
>approach is to gradually introduce C++ features, starting by just
>updating the C code so it compiles with a C++ compiler.  When that is
>done, classes, overloading, inheritance, etc. is introduced.
>
>The point is that during this transition phase they will not use the
>full power of C++, and that is probably wise.

If, in fact, everyone is being that honest with one another, sure.
I have seen cases, though, where it was all too easy to con a manager
that C++ was being used, when in fact _none_ of the power of C++
was being used, only a C++ compiler.

'Course that manager also thought the language was called C+. (no :-))

Mike Feldman