#: 11884 S12/OS9/68000 (OSK)
    22-Aug-91  09:25:43
Sb: #11877-Questions
Fm: Mark Wuest 74030,332
To: Jim Peasley 72726,1153

To some extent, it doesn't matter whether I like C++ or not, we're "stuck" with
it on our present project. Whether we use classes or not is up to us. Contrary
to Scott's observations, *I* think I may like it. Using classes enforces data
hiding in a way we only approached on our last project. Just to whet your
appetited, I'll give you a feature you may like:
 If you have a function, foo(), it can actually be several functions with the
same name, but different prototypes. This means you can have several functions:
 int foo(int arg);
 int foo(char * arg);
 int foo(void);
 void foo(int arg1, int arg2);
 int foo(int arg1, char *arg2);

 - all having the same name. In your mainline code, you just call it with the
proper argument type and the compiler knows which one you actually want. Pretty
slick, huh? (FWIW, this is called "overloading")
 As far as being happy with the current version of C, I *do* believe we will
have to migrate to ansi C anyway, so why not go "whole hog"? I would go for it.
A little serendipity: Borland supports C++ in their forum here on CI$:
 go bprogb

 Mark