adding some C++ in the code?

Hi, there.

There comes a time when I've seen too many #defines and every single one
of them is just a way to boilerplate either (a) a constructor or (b) a
destructor or (c) an access point that is shaped by the object type or
(d) type-dependent reusable versions of a-c.

For the configuration code, I think its time we considered having it,
but without the full stdc++ library (not too hard).

This just so long as any changes can pass muster with the self-test and
continue to work.  But the size of the config setup and the insanity in
getting to some parts or knowing some states of a config makes the
number of access functions really enormous and very confusing.

There are other areas ... but C++ can have fully-compatible C bindings.

Any objections?   Why all the pitchforks and torches?

     -- CH

Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.