Date:	Tue, 6 Oct 1998 18:04:18 +0100 (BST)
From:	George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To:	djgpp AT delorie DOT com
cc:	Diego Domonguez Cazorla <ddomingu AT mlg DOT cit DOT alcatel DOT es>
Subject:	Re: ALLEGRO and ANSI C ????
In-Reply-To:	<m0zQYFT-000S5AC@inti.gov.ar>
Message-ID:	<Pine.OSF.4.05.9810061754340.30717-100000@sable.ox.ac.uk>
MIME-Version:	1.0
X-MIME-Autoconverted:	from QUOTED-PRINTABLE to 8bit by delorie.com id RAA22034
Reply-To:	djgpp AT delorie DOT com

On Tue, 6 Oct 1998, Salvador Eduardo Tropea (SET) wrote:

> Diego Domínguez Cazorla <ddomingu AT mlg DOT cit DOT alcatel DOT es>
> 
> > 		I tried to make a proyect containing ALLEGRO 3.0 functions and qhen I turned on the gcc ANSI 
> > switch it complaint about some elements in ALLEGRO (directive #error for 
> > example).
> > 
> > 	Have I done something wrong?
> > 	Is ALLEGRO 3.0 non ANSI C?
> 
> Allegro uses low level hardware stuff, isn't supposed to be ANSI.

True but even so perhaps the header should be parsable in strict
ANSI mode.  This allows people to write the rest of their code
portably, apart from the Allegro calls.  It'll make it easier to
port to WinAllegro+MSVC, for instance.

I just made a couple of changes to my version of the WinAllegro
header (used with RSXNTDJ), and it works fine with `-ansi'.  I
needed to change all `asm' to `__asm__' -- that's all.

For the DOS Allegro header some other changes may be necessary.
`DJGPP' isn't defined, we must use `__DJGPP__' instead.  I think
this would need changing in the Windows version too actually.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

xu do tavla fo la lojban  --  http://xiron.pc.helsinki.fi/lojban/lojban.html

- Raw text -