login
Header Space

 
 

Re: curses

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Subject: Re: curses
Date: Saturday, August 1, 1992 - 3:53 pm

In article <fortony.712630133@murphy>, fortony@sonne.cso.uiuc.edu writes:
|> 
|> Is anyone else having problems with curses?  I've written a very short
|> program which should move an x up, down, left and right on the screen
|> depending on what key the user presses, but there are two problems:
|> 
|> 1) sometimes, the x is written to the wrong place entirely (8 spaces
|>    to the right of where it should, for instance)
|> 
|> 2) endwin() invariably returns a non-zero value.
|> 

Please take a look at the curse code. endwin () returns some garbage.
I believe lots of bsd code do something like this,

foo (....)
{
....
....
bar = temp; /* no `return' here. */
}

I tried to clear libinet.a in gcc 2.2.2d. I didn't get time for curses.

-- 
H.J.
Gcc/libc maintainer for Linux.
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: curses, Hongjiu Lu, (Sat Aug 1, 3:53 pm)
speck-geostationary