Date:	Wed, 13 Jun 2001 11:38:17 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	JT Williams <jeffw AT darwin DOT sfbr DOT org>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: DJGPP 2.04 release date
In-Reply-To:	<20010612125834.B24961@kendall.sfbr.org>
Message-ID:	<Pine.SUN.3.91.1010613113757.16126F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 12 Jun 2001, JT Williams wrote:

> Here is a brief description of the code:
> 
> 	     The file "tinytcap.c" contains a set of functions  that
> 	emulate  the  termcap  library  for  a small set of terminal
> 	types.  The terminal-specific info is hard-coded  into  this
> 	file.   It  is only used for systems that don't support real
> 	termcap.  Another alternative for screen control can be seen
> 	in  the  "curses.h"  and  "pc.c"  files.  Here, macros named
> 	VOIDBIOS and CHECKBIOS are used to indirectly call functions
> 	which perform low-level screen manipulation via BIOS calls.
> 
> The `hard-coded' terminal-specific info is already written in pretty
> standard termcap style; it would be simple enough to put it in a
> separate termcap file and point an environment variable at it.

Thanks.

What is the approximate size of this library?  If it's significant, we
probably should make it separate of termios.  Then there might be a
problem with having termios support editing keys without having to
link the entire termcap library into the executable.

This aspect is why I preferred to have some minimal implementation,
for editing keys support only, as part of termios.  But perhaps this
issue is not as important as I tend to think.

- Raw text -