Date:	10 Aug 2003 07:58:35 +0200
Message-Id:	<uvft612b8.fsf@elta.co.il>
From:	Eli Zaretskii <eliz AT elta DOT co DOT il>
To:	djgpp AT delorie DOT com
In-reply-to:	<20030809213558.07244.00001052@mb-m12.aol.com> (sterten@aol.com)
Subject:	Re: ATT assembler question
References:	<3f35735b$0$167$cc7c7865 AT news DOT luth DOT se> <20030809213558 DOT 07244 DOT 00001052 AT mb-m12 DOT aol DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: sterten AT aol DOT com (Sterten)
> Newsgroups: comp.os.msdos.djgpp
> Date: 10 Aug 2003 01:35:58 GMT
> 
> (it's a pity, that C doesn't let me test what key is pressed !)

Yes, it does.  DJGPP has a few functions to do that: _bios_keybrd,
bioskey, getkey, getxkey.  One of them should do what you want, I
hope.

> First,  I don't know  what COFF is, nor how to link.

COFF is the object file format used by DJGPP.  If NASM generates COFF
*.o object files, you can link them into your programs as if they
were compiled by GCC:

     gcc -o myprogram.exe foo.o bar.o baz.o ...

where the various *.o are object files.

> Second , when I give my source to others, I don't want to
> require that they do get NASM,  do the COFF  and link,
> just when they only want to implement a small change,
> like changing a parameter.

NASM is free software, available from the net, so requiring it is no
different from requiring the rest of DJGPP development tools.

That said, I do think that using the standard development tools is
slightly better.  NASM was mentioned only to make the life easier for
you, as you obviously know the Intel assembly format better.

- Raw text -