Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!sri-unix!husc6!mit-eddie!uw-beaver!cornell!rochester!ritcv!msl5864
From: msl5864@ritcv.UUCP (Michael S. Leibow)
Newsgroups: comp.sys.amiga
Subject: Re: Strange Guru Visitation
Keywords: Guru Programming C what-a-mess help-me-spock
Message-ID: <206@ritcv.UUCP>
Date: 13 Feb 88 13:26:01 GMT
References: <5209@well.UUCP>
Reply-To: msl5864@ritcv.UUCP (Michael S. Leibow)
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 27

In article <5209@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes:
>
>I'm experiencing a rather nasty and majorly head-scratching problem with
>a program I'm writing.
......
......
>	float v[3];
>	BOOL flag[3];
>	UBYTE s[8];


The problem is with the BOOL.  The BOOL is defined as a "short" when it should
be an "unsigned long".  If you edit your header file that has the "BOOL"
typedef in it and make a BOOL, a ULONG, you won't have any more problems.

I did not like the idea of editing my header files so I just make a new type
called BOOLEAN.

typedef BOOLEAN ULONG;

	Hope this helps...


-- 
Michael S. Leibow
UUCP:		{allegra,seismo}!rochester!ritcv!msl5864
CSNET:		msl5864%rit@csnet-relay.ARPA