🚀 go-pugleaf

Paul Long <plong@perf.com> writes:
> For example, what is the type of the composite type's
> parameter that is constructed from the following function declarations?
>
>    void foo(volatile);
>    void foo(const a) {
>        a = 3;
>    }

The type of the composite function's parameter is int; but the type
of "a" in the body of foo is "const int".

That is, the composite type of the function has no influence
on the actual types of the parameters in the function body; their
types remain as declared in the function definition (modulo the
decays for parameters declared as arrays and functions).

> Technical Corrigendum 1 says that "In the determination of type
> compatibility and of a composite type, ... each parameter declared with
> qualified type is taken as having the unqualified version of its declared
> type." So does that means that
>    1. the types of my two foo declarations are compatible,
>    2. the composite type of the parameter is int,
>    3. a is a modifiable lvalue, and
>    4. this is a conforming program?

Yes, yes, no, no.

Jutta Degener (jutta@cs.tu-berlin.de)