Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!adm!smoke!gwyn From: gwyn@smoke.ARPA (Doug Gwyn ) Newsgroups: comp.lang.c Subject: Re: typedefs and prototypes Message-ID: <8554@smoke.ARPA> Date: 21 Sep 88 03:52:52 GMT References: <7135@bloom-beacon.MIT.EDU> <8543@smoke.ARPA> <7785@haddock.ima.isc.com> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 20 In article <7785@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes: >In article <8543@smoke.ARPA> gwyn@smoke.ARPA (Doug Gwyn) writes: >> void (*kb_widget1)(int key, void *data) { ... } >That can't be right. If kb_widget1 is supposed to be a pointer to a function, >then its definition would take an initializer, not a function body. Hm, that's probably right. "Never mind." >>In <7135@bloom-beacon.MIT.EDU> tada@athena.mit.edu (Michael Zehr) writes: >>>typedef void (*Keyboard_widget)(int key, void *data); >It looks like what you meant to say was: > typedef void Keyboard_widget(int key, void *data); That's more what I had in mind anyway. I still can't get some of the PCC-based compilers around here to let me use function typedefs in the actual function definition. (Of course the parameter list is not an issue since old-style C doesn't have prototypes.)