Date: Wed, 14 Oct 1998 17:40:36 +0100 (BST)
From: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: Detecting Arrow Key Presses
In-Reply-To: <7020ek$i79$1@news.metronet.de>
Message-ID: <Pine.OSF.4.05.9810141736580.32169-100000@sable.ox.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com

On Wed, 14 Oct 1998, Felix wrote:

> i have not figured out how to read extended scancodes, so if you do, let me
> know!

You can look at Allegro's keyboard handler -- it's in
`allegro/src/djgpp/keyboard.c'.

> i've just started using DJGPP and I've been using Turbo C++ 3.0 for almost
> half a year before.... somewhere on the web there is a doc on how to deal
> with its bugs (like increasing memory available to the program, executing
> 32bit inline-assembly-instructions...) - you might want to look at that!

Please, these are not djgpp bugs!  They're problems cause by
unportable behaviour in your programs.  I don't see how
increasing the amount of memory available could be called a bug,
and inline assembly is inherently unportable.

-- 
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