Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: is (int (*)())NULL legal when NULL is (void *)0?
Message-ID: <14484@smoke.brl.mil>
Date: 15 Nov 90 21:42:02 GMT
References: <13799@crdgw1.crd.ge.com> <14463@smoke.brl.mil> <13870@crdgw1.crd.ge.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 19

In article <13870@crdgw1.crd.ge.com> volpe@camelback.crd.ge.com (Christopher R Volpe) writes:
>If the above is not true, then where in the standard does it say that
>an implementation must support casting an int into a float?

Conversions involving pointers have an explicit set of requirements
in 3.3.4 beyond the basic semantics.  The basic semantics suffice for
interconversion of arithmetic values; 3.2.1.3 gives details.

>Both *conversions* are supported, if done via assignment operators.

I can't parse that.

Certain license beyond 3.3.4 is granted in 3.3.16.1 for assignment
involving certain pointers that meet the constraints of 3.3.16.1.

If you have further questions about this, I suggest you send X3 a request
for an interpretation ruling.  Possibilities for misunderstanding are
limitless, and I really cannot spend much more time on this than I
already have.  I think the standard is clear on this.