| Re: [AD] Allegro on amd64-linux |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro on amd64-linux
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Mon, 18 Oct 2004 02:16:46 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=VfMWohkPEb2wulXJ/eUCkyEpzmuULAssrbzMCC9+c/aPXByoqrS7qhKAVqFGECxaBDSt+lsuuAKuLPLCMN74JmvL+hjp1InH9quEVbIlyJTiF67Ypracay0qaEkoRc+HSnX+sJjIU3fgwiC5SJL+ihpwU7ujXjTVT09XcvM4IqU
On Mon, 18 Oct 2004 08:40:17 +0200, Eric Botcazou
<ebotcazou@xxxxxxxxxx> wrote:
> Note that the same problem will occur in user code too, which means that
> strict backwards source compatibility has been broken. IMO for nothing,
> because replacing GFX_MODEX with GFX_HAS_MODEX is really pointless.
I just sent a patch earlier today that should take care of the
problem. Old code should still compile and run as expected since if
GFX_MODEX is defined, so is the function split_modex_screen. If
there's any other Mode-X function that should exist even if Mode-X
isn't available, just say what and I'll make it do a null-op. The
Mode-X vtable and its functions don't exist when VGA is disabled, but
those've never been part of the exposed API so user-code should never
touch them.
- Kitty Cat