typedef

[Merrill & Michele]

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLAT EHEADER;

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

[dandelion]

"Merrill & Michele" <be********@com cast.net> wrote in message
news:If******** ************@co mcast.com...

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLAT EHEADER;

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.

[Merrill & Michele]

"dandelion" <da*******@mead ow.net> wrote in message
news:41******** **************@ dreader15.news. xs4all.nl...

"Merrill & Michele" <be********@com cast.net> wrote in message
news:If******** ************@co mcast.com...

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLAT EHEADER;

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.

And where exactly do you put something like this so an OS can talk to ISO C
and vice versa. They teach different tools for hooking creatures like this
using Bjarne's paradigm. There has to be a way in C and my guess is that's
easy. MPJ

[Bryan Bullard]

"dandelion" <da*******@mead ow.net> wrote in message
news:41******** **************@ dreader15.news. xs4all.nl...

"Merrill & Michele" <be********@com cast.net> wrote in message
news:If******** ************@co mcast.com...

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLAT EHEADER;

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;

[Alan Balmer]

On Mon, 20 Dec 2004 08:31:03 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLA TEHEADER;

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

The best way is to include the headers, presumably supplied by the
unnamed platform's implementation, which define WORD.

--
Al Balmer
Balmer Consulting
re************* ***********@att .net

[Merrill & Michele]

"Alan Balmer" <al******@att.n et> wrote in message
news:l6******** *************** *********@4ax.c om...

On Mon, 20 Dec 2004 08:31:03 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLA TEHEADER;

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, moreefficacious way to make this pass gcc with -ansi tag and no complaints? MPJ

The best way is to include the headers, presumably supplied by the
unnamed platform's implementation, which define WORD.

But those are going to include a lot of much less than standard stuff. But
if I get your meaning, I need to track down WORD. I MEANT to use an example
with a DWORD. Would that make a difference? MPJ

[Bryan Bullard]

"Merrill & Michele" <be********@com cast.net> wrote in message
news:ZO******** ************@co mcast.com...

"Alan Balmer" <al******@att.n et> wrote in message
news:l6******** *************** *********@4ax.c om...

On Mon, 20 Dec 2004 08:31:03 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLA TEHEADER;

This is from vol 5 of unnamed platform's programmer's reference. I couldmake this conforming by enclosing everything in a /*...*/ comment and
appending the 'hail world' code. Is there an easier, and, let's say, moreefficacious way to make this pass gcc with -ansi tag and no complaints? MPJ The best way is to include the headers, presumably supplied by the
unnamed platform's implementation, which define WORD.

But those are going to include a lot of much less than standard stuff.

But if I get your meaning, I need to track down WORD. I MEANT to use an example with a DWORD. Would that make a difference? MPJ

He's given you good advise. See windef.h

[Alan Balmer]

On Mon, 20 Dec 2004 12:05:38 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

"Alan Balmer" <al******@att.n et> wrote in message
news:l6******* *************** **********@4ax. com...

On Mon, 20 Dec 2004 08:31:03 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

>typedef struct
>{
> WORD versionNumber;
> WORD offset;
>}
>MENUITEMTEMPLA TEHEADER;
>
>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 >

The best way is to include the headers, presumably supplied by the
unnamed platform's implementation, which define WORD.

But those are going to include a lot of much less than standard stuff. But
if I get your meaning, I need to track down WORD. I MEANT to use an example
with a DWORD. Would that make a difference? MPJ

No. But what are you trying to accomplish? If you are trying to
actually compile a program on this platform, use the platform's
headers. If you're just trying to read the program, does the exact
definition of the type WORD really matter?

The above tells me that the author has invented a type named
MENUITEMTEMPLAT EHEADER (terrible name, imo, but that's another
subject.) This type is a struct composed of two variables,
versionNumber and offset. I see no reason, at this point, to care what
type those variables are. In fact, there should be no reason even to
know what type MENUITEMTEMPLAT EHEADER is composed of - it just gets
used when it's needed, and a good implementation would bury the
details where you don't need to see them, unless you are the author
that created it.

--
Al Balmer
Balmer Consulting
re************* ***********@att .net

[Zax]

"Alan Balmer" <al******@att.n et> wrote in message
news:m8******** *************** *********@4ax.c om...

On Mon, 20 Dec 2004 12:05:38 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

"Alan Balmer" <al******@att.n et> wrote in message
news:l6******* *************** **********@4ax. com...

On Mon, 20 Dec 2004 08:31:03 -0600, "Merrill & Michele"
<be********@com cast.net> wrote:

>typedef struct
>{
> WORD versionNumber;
> WORD offset;
>}
>MENUITEMTEMPLA TEHEADER;
>
>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

>
The best way is to include the headers, presumably supplied by the
unnamed platform's implementation, which define WORD.

But those are going to include a lot of much less than standard stuff. Butif I get your meaning, I need to track down WORD. I MEANT to use an examplewith a DWORD. Would that make a difference? MPJ

No. But what are you trying to accomplish? If you are trying to
actually compile a program on this platform, use the platform's
headers. If you're just trying to read the program, does the exact
definition of the type WORD really matter?

The above tells me that the author has invented a type named
MENUITEMTEMPLAT EHEADER (terrible name, imo, but that's another
subject.) This type is a struct composed of two variables,
versionNumber and offset. I see no reason, at this point, to care what
type those variables are. In fact, there should be no reason even to
know what type MENUITEMTEMPLAT EHEADER is composed of - it just gets
used when it's needed, and a good implementation would bury the
details where you don't need to see them, unless you are the author
that created it.

Believe it or not, MENUITEMTEMPLAT EHEADER is a creature that I think ISO C
can reach with sufficient elbow grease. I'm gonna look through some
headers. MPJ

[dandelion]

"Bryan Bullard" <re****@to.grou p.com> wrote in message
news:lW******** *********@newss vr30.news.prodi gy.com...

"dandelion" <da*******@mead ow.net> wrote in message
news:41******** **************@ dreader15.news. xs4all.nl...

"Merrill & Michele" <be********@com cast.net> wrote in message
news:If******** ************@co mcast.com...

typedef struct
{
WORD versionNumber;
WORD offset;
}
MENUITEMTEMPLAT EHEADER;

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.