[2244] in Kerberos_V5_Development
Re: Function pointers with krb5_{calculate,verify}_checksum
daemon@ATHENA.MIT.EDU (Ken Hornstein)
Wed Feb 19 17:24:25 1997
To: Ken Raeburn <raeburn@cygnus.com>
Cc: krbdev@MIT.EDU
In-Reply-To: Your message of "19 Feb 1997 17:12:52 EST."
<tx1sp2sigwr.fsf@cygnus.com>
Date: Wed, 19 Feb 1997 17:22:26 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
>ANSI C rules specify that function "values" are automatically
>converted to the function's address, except in the function-call
>context. And a call done with a function pointer does the right
>thing. I'm a bit fuzzy on those parts of the rules, but I think
>that's roughly right.
"Interesting". However, I don't think the _function_ call is failing,
on second glance .... I think it's the test to see if the function pointer
is NULL. So what is the value of **f under these rules?
Can you quote a more specific part of the ANSI C standard? If I can go
to the vendor and say, "Section X of the standard says you're wrong", it will
bolster my argument :-)
>> Am I way off base here? The thing that puzzles me is, if this is a problem,
>> how come it doesn't show up on other architectures?
>
>Because the other compilers implement this correctly.
Fair enough. But it still seems to me that this code is inconsistant with
the other uses of the krb5_x macro.
--Ken
