Re: tn3270, mset and map3270

[itohy%NetBSD.org@localhost (ITOH Yasufumi)]

In article <4B866EA0.5030407%NetBSD.org@localhost>
roy%NetBSD.org@localhost writes:

> What makes you think that terminfo(5) doesn't allow this also?

I knew some implementations have extension to allow custom
capabilities, but is not portable.
Interesting enough, the extension is something like adding termcap
entry in the terminfo, and inconsistent with the original idea of
terminfo.

The idea of terminfo(5) (terminfo(4) might be more precise, since
UNIX System V reordered section number) is to use a fixed array of
capabilities to speed-up loading database, so basically there is
no room for custom capabilities.

To use custom capabilities, we can use termcap almost everywhere.

Do you have any benefit to use terminfo for programs that are
already written to use termcap?
Since our new termcap library is fast, I don't see any benefit to
rewrite termcap programs for terminfo.  It just causes loss of
features such as $TERMCAP.

(I'm not objecting for providing termcap API somewhere, since it might
be useful to use programs written for terminfo without modification.)

Regards,
-- 
ITOH Yasufumi