News Group Posts

porting sco ncurses to linux

Message-ID: <48d55656$0$26372$e4f62565@news.jtan.com> 
From: dic...@invisible-island.net (Thomas E. Dickey)
Subject: Re: ncurese nodelay problem
Date: 20 Sep 2008 20:00:22 GMT

FurtiveBertie <Furtive_ber...@hotmail.com> wrote:
> On 17 Sep, 10:14, FurtiveBertie <Furtive_ber...@hotmail.com> wrote:
>> On 8 Sep, 21:24, dic...@invisible-island.net (Thomas E. Dickey) wrote:
>> > Nico Kadel-Garcia <nka...@gmail.com> wrote:
>> > >>> The SCO code is fascinating old stuff, on SCO OpenServer 5.0.6, built
>> > >>> with a manually compiled gcc-2.7.2 and the SCO Skunkware version of
>> > >>> ncurses-4.2.
>>
>> > >> ncurses 4.2 is 10 years old (I'm confused about the comment about 15 years).
...
>> I have narrowed this down, and got an idea of what is going wrong :-)

thanks.  I ran your test-program on Solaris 10 and IRIX64, found that it
behaves as you expect.

Back to ncurses - the problem is older than ncurses 4.2, apparently from
the original implementation of the feature in ncurses 1.9.2d in June
1995.

(It's been a while since I ran into one from the pre-1.9.9e era ;-)

The change:

diff -u -r1.98 base/lib_getch.c
--- base/lib_getch.c    2008/08/16 21:20:48     1.98
+++ base/lib_getch.c    2008/09/20 19:46:13
@@ -381,7 +381,7 @@
 
     recur_wrefresh(win);
 
-    if (!win->_notimeout && (win->_delay >= 0 || sp->_cbreak > 1)) {
+    if (win->_notimeout || (win->_delay >= 0) || (sp->_cbreak > 1)) {
        if (head == -1) {       /* fifo is empty */
            int delay;
            int rc;

That "!win->_notimeout" is the same in 1995, and is the only place that
the value is checked (or should be checked).  I'm puzzled by your reference
to ncurses 4.2, since the bug in (the original) version of that as well
(and I was unaware of any patched version).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.