From:	"Ben Davis" <bndavis AT lineone DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: getch() mysteriously defined
Date:	Sat, 8 Jul 2000 23:33:53 +0100
Organization:	RemarQ http://www.remarQ.com
Lines:	14
Message-ID:	<8k8a8h$kmr$1@supernews.com>
References:	<8k470e$262$1 AT plato DOT wadham DOT ox DOT ac DOT uk> <8ubbmsk17t4djl7cp8mput3su30k9uebk5 AT 4ax DOT com> <8k7rak$brc$1 AT plato DOT wadham DOT ox DOT ac DOT uk>
NNTP-Posting-Host:	213.1.17.35
X-Trace:	963095633 LGTBT6QCL1123D501C uk21.supernews.com
X-Complaints-To:	newsabuse AT remarq DOT com
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> >Well, gcc *does* complain:
>
> Presumably with some sort of warnings turned on, as compiling via RHIDE
> works silently.

No it doesn't. If you enable -Wall (Options -> Compilers -> Warnings), you
should find the warning message(s) in the message window, where it says
"Compiling foobar.c" followed by "no errors" or "there were some errors".
What's more, it should interpret these messages and show you the line that
caused them.

Ben Davis

- Raw text -