From: Moo-Juice <Ben AT flag DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Why two identical typedef are considered an error in DJGPP?
Date: Wed, 22 Jan 1997 10:59:27 +0000
Organization: Honest Ron's Car Emporium
Lines: 24
Distribution: world
Message-ID: <dzL7mEAPMf5yEwI6@flag.demon.co.uk>
References: <01IE7MKQWZ2Q003361 AT cc DOT uab DOT es>
 <Pine DOT A41 DOT 3 DOT 94 DOT 970115082052 DOT 92882A-100000 AT acs2 DOT acs DOT ucalgary DOT ca>
 <jRKDPBAXkX3yEw9J AT foobar DOT co DOT uk> <slrn5e086r DOT gp5 DOT davep AT hagbard DOT demon DOT co DOT uk>
 <32e22d1c DOT 4599867 AT ursa DOT smsu DOT edu>
NNTP-Posting-Host: flag.demon.co.uk
MIME-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <32e22d1c DOT 4599867 AT ursa DOT smsu DOT edu>, Tony O'Bryan
<aho450s AT nic DOT smsu DOT edu> writes
>On Sat, 18 Jan 1997 01:01:22 GMT, Dave Pearson <davep AT hagbard DOT demon DOT co DOT uk>
>wrote:
>
>>#ifndef BYTE
>>typedef unsigned char BYTE;
>>#endif
>>
>>#ifndef BYTE
>>typedef unsigned char BYTE;
>>#endif
>
>GCC complains about a redefinition, but will allow a #define in place of the
>typedef.  Turbo C allows both versions.
>
>Sorry for the extra text, but Free Agent won't let me send a message that has
>more quoted material than new. :(

One question...  why are the 'chars' unsigned?  This is a simple query
and not an attack on the reason for using it :)

-- 
Moo-Juice