🚀 go-pugleaf

Subject: Re: parameter type matching (was Re: the SUN way)
In article <1990Dec24.112015.4426@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes:
>diamond@tkou02.enet.dec.com ("diamond@tkovoa") writes:
>>Here in pseudo-C syntax:
>>  typeof(x) *bsearch(const any (*x)[], const typeof(x) *,
>>                     unsigned, unsigned,
>>                     int(*)(const typeof(x) *, const typeof(x) *));
>How about:
> typeof(x) *bsearch(const any (*x)[], const oftype(x) *,
>                    unsigned, unsigned,
>                    int(*)(const oftype(x) *, const oftype(x) *));
 
My understanding was that gcc calls it typeof.  (Though gcc's construct
is not powerful enough to back up from the parameter declaration to the
function return type.  The 1989 Extended Pascal standard can do it because
function return types come after the parameter declarations.)
 
I don't care if you want to call it oftype instead of typeof.
But you missed one.
> typeof(x) *bsearch(const any (*x)[], const oftype(x) *,
  oftype
 
>Also, looking at it, I would assume that "x" is of type "pointer to
>function", and so question the "*"s within the prototype of bsearch;
>i.e., it is hard to understand to what, and with what stopping point,
>your typing has tied x.
 
Huh?  I said, and you correctly quoted my saying, what x was:
>> Notice that the first parameter names the prototype-scoped identifier
>> x, whose type is invoked in other parts of this prototype. If the
>> programmer wanted to name other parameters and copy their types as
>> well, it could also be done.
  oftype(x) *bsearch(const any (*x)[], const oftype(x) *,
                             ----^----
In this example, x has type (const any *).  [Hmm, the oftype (or whatever)
construct will have to be given additional capability to remove "const"
when necessary.]
--
Norman Diamond       diamond@tkov50.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.