From:	jstacey AT plato DOT wadham DOT ox DOT ac DOT uk (J-P)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: getch() mysteriously defined
Date:	8 Jul 2000 19:19:00 +0100
Organization:	Wadham College Oxford
Lines:	13
Message-ID:	<8k7rak$brc$1@plato.wadham.ox.ac.uk>
References:	<8k470e$262$1 AT plato DOT wadham DOT ox DOT ac DOT uk> <8ubbmsk17t4djl7cp8mput3su30k9uebk5 AT 4ax DOT com>
NNTP-Posting-Host:	plato.wadham.ox.ac.uk
X-Trace:	news.ox.ac.uk 963080341 5452 163.1.164.74 (8 Jul 2000 18:19:01 GMT)
X-Complaints-To:	newsmaster AT ox DOT ac DOT uk
NNTP-Posting-Date:	8 Jul 2000 18:19:01 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <8ubbmsk17t4djl7cp8mput3su30k9uebk5 AT 4ax DOT com>,
Chris Mears  <cmears AT bigpond DOT com> wrote:
>Well, gcc *does* complain:

Presumably with some sort of warnings turned on, as compiling via RHIDE
works silently.

>getch() is still called because it is part of libc, and libc is linked
>with the executable.

Yes. Ta for this, everyone.

J-P

- Raw text -