[Python-Dev] _cursesmodule.c clobbered since Christmas

[Mark Favas]

I last successfully downloaded from CVS, compiled, linked and tested on
Dec. 22 last year. For the last week or so, the current CVS
_cursesmodule.c gives a bunch of compiler warning messages of the form:

cc: Warning: ./_cursesmodule.c, line 619: In this statement,
"derwin(...)" of ty
pe "int", is being converted to "pointer to struct _win_st".
(cvtdiftypes)
  win = derwin(self->win,nlines,ncols,begin_y,begin_x);
--^
cc: Warning: ./_cursesmodule.c, line 1259: In this statement,
"subpad(...)" of t
ype "int", is being converted to "pointer to struct _win_st".
(cvtdiftypes)
    win = subpad(self->win, nlines, ncols, begin_y, begin_x);
----^
cc: Warning: ./_cursesmodule.c, line 1488: In this statement,
"termname(...)" of
 type "int", is being converted to "pointer to const char".
(cvtdiftypes)
NoArgReturnStringFunction(termname)
^
(more elided)

and

cc: Warning: ./_cursesmodule.c, line 305: The scalar variable "arg1" is
fetched 
but not initialized.  And there may be other such fetches of this
variable that 
have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getparyx, int, "(ii)")
^
cc: Warning: ./_cursesmodule.c, line 305: The scalar variable "arg2" is
fetched 
but not initialized.  And there may be other such fetches of this
variable that 
have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getparyx, int, "(ii)")
^
(more elided)

and at link time, fails with:

ld:
Unresolved:
getbegyx
getmaxyx
getparyx


I've held off bothering anyone about this, but it begins to look as
though no-one else has noticed... My platform? Tru64 Unix, V4.0F (aka
OSF1). The recent pow() bug hit this platform, too. Happy to do any
testing...



-- 
Mark Favas  -   m.favas@per.dem.csiro.au
CSIRO, Private Bag No 5, Wembley, Western Australia 6913, AUSTRALIA