Re: typedef [OT]
From: dandelion (dandelion_at_meadow.net)
Date: 12/21/04
- Next message: anirudhvr_at_spymac.com: "Re: Binary to ascii encoder"
- Previous message: Charlie Gordon: "Re: Binary to ascii encoder"
- In reply to: Bryan Bullard: "Re: typedef [OT]"
- Next in thread: Richard Bos: "Re: typedef [OT]"
- Reply: Richard Bos: "Re: typedef [OT]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 21 Dec 2004 13:08:29 +0100
"Bryan Bullard" <replay@to.group.com> wrote in message
news:lWCxd.3318$iC4.2986@newssvr30.news.prodigy.com...
>
> "dandelion" <dandelion@meadow.net> wrote in message
> news:41c6e878$0$9611$e4fe514c@dreader15.news.xs4all.nl...
> >
> > "Merrill & Michele" <beckjensen@comcast.net> wrote in message
> > news:IfSdnTZiJ-8Bf1vcRVn-ow@comcast.com...
> > > typedef struct
> > > {
> > > WORD versionNumber;
> > > WORD offset;
> > > }
> > > MENUITEMTEMPLATEHEADER;
> > >
> > > This is from vol 5 of unnamed platform's programmer's reference. I
> could
> > > make this conforming by enclosing everything in a /*...*/ comment and
> > > appending the 'hail world' code. Is there an easier, and, let's say,
> more
> > > efficacious way to make this pass gcc with -ansi tag and no
complaints?
> > MPJ
> >
> >
> > typedef int WORD;
> >
> > or
> >
> > typedef unsigned int WORD;
> >
> > Personally, i think of 'words' as unsigned, but i'm open to corrections.
> >
>
> Actually, this is probably what you are looking for:
>
> typedef unsigned short WORD;
Maybe. Depends on the definition of a 'word'. On a 80x86 you are right,
on a Z80 you are wrong.
- Next message: anirudhvr_at_spymac.com: "Re: Binary to ascii encoder"
- Previous message: Charlie Gordon: "Re: Binary to ascii encoder"
- In reply to: Bryan Bullard: "Re: typedef [OT]"
- Next in thread: Richard Bos: "Re: typedef [OT]"
- Reply: Richard Bos: "Re: typedef [OT]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]