[MLton-devel] upcoming release
Stephen Weeks
MLton@mlton.org
Tue, 8 Jul 2003 13:49:00 -0700
> I didn't mean to imply that having typedefs in a .h file was bad. Just that
> one should only have them in one .h file, and that one should do the usual
> sillyness: the include file xxx.h starts with
> #ifndef XXX_H
> #define XXX_H
> and ends with
> #endif
Sure, types.h has that. The real problem is that it defines some
common type names that might be defined elsewhere -- see below. I'm
still leaning towards eliminating it.
------------------------------------------------------------
#ifndef _TYPES_H_
#define _TYPES_H_
typedef char Int8;
typedef short Int16;
typedef long Int32;
typedef long long Int64;
typedef char *Pointer;
typedef float Real32;
typedef double Real64;
typedef unsigned char Word8;
typedef unsigned short Word16;
typedef unsigned long Word32;
typedef unsigned long long Word64;
typedef Int32 Int;
typedef Real64 Real;
typedef Word8 Char;
typedef Word32 Word;
typedef Int Bool;
#endif /* _TYPES_H_ */
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel