defining new types for ULONG UINT...

[aewarnick]

Is this a bad idea?

typedef unsigned short ushort;
typedef unsigned long ulong;
typedef unsigned int uint;
typedef unsigned char byte;
typedef unsigned double udouble;

[twanvl]

No, it's a fine idea, but you should put these definitions in a visible place, for example a separate include file.

[aewarnick]

Why doesn't MS do put in in their headers and highlights those as keywords?

[twanvl]

The C(++) standard is unsigned something, usomething keywords are not really needed, you can't make everything a keyword.
By the way, you can make MSVC highlight your own keywords by editting vcdir/common/msdev98/bin/usetype.dat (in vc6, vc7 probably has a similair file)

[aewarnick]

Thanks. That file is no-where to be found. I have VS 2002.

[twanvl]

I found this

[aewarnick]

Looks good to me. Thanks! I'll give it a try.