Path: utzoo!attcan!uunet!husc6!cmcl2!rutgers!att!chinet!jkingdon
From: jkingdon@chinet.chi.il.us (James Kingdon)
Newsgroups: comp.os.vms
Subject: Re: VAX C typedef oddity
Summary: Nothing strange going on except the appearance
Message-ID: <6114@chinet.chi.il.us>
Date: 28 Jul 88 04:09:20 GMT
References: <880721084219.00000643081@naif.JPL.NASA.GOV>
Reply-To: jkingdon@chinet.chi.il.us (James Kingdon)
Organization: Chinet - Public Access Unix
Lines: 14

In article <880721084219.00000643081@naif.JPL.NASA.GOV> PJS@naif.JPL.NASA.GOV (Peter Scott) writes:
>
>	typedef struct _iobuf*	FILE;
>
>I can't find mention of this post-fixed usage of the asterisk.  

Try writing it
   typedef struct _iobuf *FILE;
which just means that FILE means pointer to struct _iobuf

Here as in most of C the spaces don't matter, and are only necessary to
separate typedef from struct and things like that.  (For some wonderful
abuse of this property, see the C Obstrufucated code contest results just
posted to comp.lang.c.)