Caveats Of Using; Protoize - Red Hat ENTERPRISE LINUX 3 - USING GCC Using Instructions

248
struct Derived:public A, public B{
Derived():Base("Derived"){}
};
void func(Derived &d1, Derived &d2)
{
d1 = d2;
}
The C++ standard specifies that
copy-constructing a Derived object. It is unspecified whether
once when the implicit copy-assignment for Derived objects is invoked (as it is inside
example).
g++ implements the "intuitive" algorithm for copy-assignment: assign all direct bases, then assign
all members. In that algorithm, the virtual base subobject can be encountered more than once. In the
example, copying proceeds in the following order:
If application code relies on copy-assignment, a user-defined copy-assignment operator removes any
uncertainties. With such an operator, the application can define whether and how the virtual base
subobject is assigned.

11.10. Caveats of using

The conversion programs
that won't work unless you rearrange it.
can insert references to a type name or type tag before the definition, or in a file where
•

protoize

they are not defined.
If this happens, compiler error messages should show you where the new references are, so fixing
the file by hand is straightforward.
There are some C constructs which
•
argument types for declaring a pointer-to-function variable; this you must do by hand.
inserts a comment containing
variables by searching for this string. ISO C does not require declaring the argument types of
pointer-to-function types.
Using
• unprotoize
conversion of arguments, these conversions will not take place in the program without prototypes.
One case in which you can be sure
were made with
protoize
again without them.
You can find all the places where this problem might occur by compiling the program with the
option. It prints a warning whenever an argument is converted.
-Wconversion
Both conversion programs can be confused if there are macro calls in and around the text to be
•
converted. In other words, the standard syntax for a declaration or definition must not result from
expanding a macro. This problem is inherent in the design of C and cannot be fixed. If only a few
functions have confusing macro calls, you can easily convert them manually.
cannot get the argument types for a function whose definition was not actually compiled
• protoize
due to preprocessing conditionals. When this happens,
a function.
protoize
Base::Base
protoize
and
protoize unprotoize
protoize
each time it finds such a variable; so you can find all such
???
can easily introduce bugs. If the program relied on prototypes to bring about
unprotoize
; if the program worked before without any prototypes, it will work
tries to detect such instances and warn about them.
Chapter 11. Known Causes of Trouble with GCC
is only called once when constructing or
Base::operator=
, (via
val name strdup
can sometimes change a source file in a way
cannot figure out. For example, it can't determine
is safe is when you are removing prototypes that
changes nothing in regard to such
protoize
is called more than
in the
func
), , and again.
bval name
protoize