From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: conio.h bug?
Date: 1 Jul 2003 08:22:16 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 38
Message-ID: <bdrgbo$937$1@nets3.rz.RWTH-Aachen.DE>
References: <bdq8md$hjv$1 AT newsreader1 DOT netway DOT at>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1057047736 9319 137.226.32.75 (1 Jul 2003 08:22:16 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 1 Jul 2003 08:22:16 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

News Reader <nospam AT aol DOT com> wrote:
> 1) Compiler error received:

>   In file included from test.c:1:
>   c:/ab/djgpp/include/conio.h:74: error:
>     nonnull argument references non-pointer operand (arg 1, operand 1)

[Later clarified that this only happens with GCC-3.3, not earlier
versions].

> 3) Line 74 in header file:

>   int gettext(int _left, int _top, int _right, int _bottom, void *_destin);

This is the 2.03 version of conio.h.  In 2.04alpha, this function is
renamed to _conio_gettext, to avoid a conflict with <libintl.h> from
GNU gettext, the program localization toolset.

To me, this sounds more like a potential bug in GCC-3.3 or its port
than a bug in conio.h --- that source line appears to be completely
correct, and the error message makes no sense whatsoever.

It might help to check preprocessor output for this, i.e.:

	gcc -E -dD test.c > test.i

and inspect test.i closely.  Particularly check what became of line 74
of conio.h.

Andris: did you put any machinery into the 3.3 port to deal with the
gettext() ambiguity? Maybe in some pre-loaded header?




-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.