Re: [AD] Borland C++ compilation errors

Re: [AD] Borland C++ compilation errors

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]

To: "Allegro conductors" <conductors@xxxxxxxxxx>
Subject: Re: [AD] Borland C++ compilation errors
From: "Eric Botcazou" <ebotcazou@xxxxxxxxxx>
Date: Mon, 5 Nov 2001 14:19:18 +0100

> Surely that function now always returns 0x7FFF?

Oh My God ! (tm) You're right.

> Assuming `fixed' is still `int',

'long' actually.

I (unconsciously) didn't feel very comfortable with this tiny patch, now I
know why... I hope the attached one is right :-)

--
Eric Botcazou
ebotcazou@xxxxxxxxxx

Attachment: alinline.diff
Description: Binary data

Follow-Ups:
- Re: [AD] Borland C++ compilation errors
  - From: George Foot

References:
- [AD] Borland C++ compilation errors
  - From: Eric Botcazou
- Re: [AD] Borland C++ compilation errors
  - From: Javier González
- Re: [AD] Borland C++ compilation errors
  - From: Eric Botcazou
- Re: [AD] Borland C++ compilation errors
  - From: George Foot

Messages sorted by: [ date | thread ]
Prev by Date: Re: [AD] Borland C++ compilation errors
Next by Date: Re: [AD] File selector patch
Previous by thread: Re: [AD] Borland C++ compilation errors
Next by thread: Re: [AD] Borland C++ compilation errors

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/