From: "Ben Combee" <[EMAIL PROTECTED]> > > In general, the standard just requires the appearance that something > happened. It says that the implied copy constructor must act like it > worked like this, and that is what drove the initial implementation.
Right. I remember when memberwise init/copy was added to the language. Programmers were concerned it would slow down their programs, but implementors assured us that the memberwizing would be optimized away when possible. This is really required by the spirit of the language--a C program shall perform no worse when compiled as C++. Thanks for the explanation of the CW optimization process. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
