This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Request for suggestions: xm-romp.h
Michael Meissner <meissner@cygnus.com> writes:
|> On Fri, Mar 16, 2001 at 05:08:49PM -0800, Richard Henderson wrote:
|> > On Fri, Mar 16, 2001 at 02:04:07PM -0800, Zack Weinberg wrote:
|> > > #define GEN_FCN(CODE) (insn_data[(int) (CODE)].genfun)
|> > > #else
|> > > #define GEN_FCN(CODE) (*insn_data[(int) (CODE)].genfun)
|> >
|> > The former is also acceptable to ISO C. Does it cause K&R problems?
|> > If not, maybe we can just use that always.
|>
|> The automatic dereference of a function pointer to function in a call context
|> should cause K&R problems, since as I recall it was feature added by the
|> original ANSI C document.
Actually in ISO C the function pointer is not dereferenced, but rather the
function decays to a function pointer in call context. Thus the syntax
without the dereference operator was a natural consequence.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5