🚀 go-pugleaf

In message <1995Nov23.012520.24896@il.us.swissbank.com> - pld@syd.au.swissbank.
com (Phillip Drury) writes:
:>
:>I have come across this interesting problem with const pointer parameters
:>and typedefs and was wondering if anybody could explain it to me. I have
:>compiled the following code with gcc 2.6.3 and the Sun cc 3.0.1 compiler
:>and both have given the same result.
:>
:>typedef int *pINT;
:>
:>void
:>Test(int* param)
:>	{
:>	}
:>
:>void
:>Func1(const int* param)
:>	{				
:>	Test(param); /* Compiler complains const int* passed to int* parameter */
:>	}
:>
:>Func2(const pINT param)
:>	{
:>	Test(param); /* Compiler does not complain */
:>	}
:>
:>Now can anyone explain to me why the compiler does not complain about
:>the second case because "const int* param" should be exactly the same
:>as "const pINT param" as there exists the typedef int *pINT.
:>

No, they are not the same!  a typedef is like an implied parentheses.

const pINT == const (int*) == int * const.

Ken Walter

* All the above is hearsay and the opinion of nobody in particular