Date:	29 Jul 2003 08:17:06 +0200
Message-Id:	<uptjt3li5.fsf@elta.co.il>
From:	Eli Zaretskii <eliz AT elta DOT co DOT il>
To:	djgpp AT delorie DOT com
In-reply-to:	<bg436h$1bk9$1@ulysses.news.tiscali.de> (bdeck@lycos.co.uk)
Subject:	Re: djgpp & ncurses
References:	<3F21CE28 DOT 9E5CFDF8 AT mail DOT rosecom DOT ca> <bftbs8$9hu$1 AT ulysses DOT news DOT tiscali DOT de> <3F257E91 DOT 2883F831 AT phekda DOT freeserve DOT co DOT uk> <bg436h$1bk9$1 AT ulysses DOT news DOT tiscali DOT de>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "bdeck" <bdeck AT lycos DOT co DOT uk>
> Newsgroups: comp.os.msdos.djgpp
> Date: Mon, 28 Jul 2003 23:12:37 +0200
> >
> > I have wondered if poll could be implement as a wrapper for select. Have you
> > thought about or tried that?
> >
> > I'd like to implement poll for the DJGPP 2.04 release, because it's part of
> > the POSIX standard.
> 
> I am not very familiar with the difference. I only know what DJGPP has and
> what it doesn't. However, Thomas Dickey seemed to indicate that the
> difference is quite significant, and that he has seen "many more successful
> poll implementations (in reading multibyte keys w/ ncurses) than select
> implementations".

I don't see why Thomas would say that the difference is
``significant''.  AFAICS, adding `poll' to DJGPP should be easy,
either as a wrapper for `select', or as a separate module reusing most
of the code in `select'.  I think this would be a welcome addition.

- Raw text -