[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV TODO page (was Re: #38...)
From: |
Foteos Macrides |
Subject: |
Re: LYNX-DEV TODO page (was Re: #38...) |
Date: |
Sat, 05 Apr 1997 11:14:55 -0500 (EST) |
"T.E.Dickey" <address@hidden> wrote:
[...]
>if you do that, use 'napms()' if it's present -- 'sleep()' will have the
>undesirable effect of not flushing out the screen contents.
The current active developers obviously should have the major
say about the principles which will be followed in Lynx development,
but a principle of the past several years has been to favor universally
portable functions from external system libraries, and otherwise deal
with coding needs internally. Here's what the solaris man says about
napms():
curs_kernel(3X) Miscellaneous Library Functions curs_kernel(3X)
NAME
curs_kernel, [...], napms - low-level curses routines
SYNOPSIS
[...]
int napms(int ms);
MT-LEVEL
Unsafe
DESCRIPTION
The following routines give low-level access to various
curses functionality. These routines typically are used
inside library routines.
[...]
Note that fflush(), like sleep(), is considered a universally
portable external library function (but so is remove() :) :).
Fote
=========================================================================
Foteos Macrides Worcester Foundation for Biomedical Research
address@hidden 222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;
- Re: LYNX-DEV TODO page (was Re: #38...),
Foteos Macrides <=