delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f |
Date: | Fri, 13 Jul 2001 13:16:29 -0500 |
From: | JT Williams <jeffw AT darwin DOT sfbr DOT org> |
To: | djgpp-workers AT delorie DOT com |
Subject: | Re: another termcap library option |
Message-ID: | <20010713131629.B4442@kendall.sfbr.org> |
Mail-Followup-To: | djgpp-workers AT delorie DOT com |
References: | <3B4D8E2E DOT 20 DOT 635925 AT localhost>; <20010712114929 DOT D2337 AT kendall DOT sfbr DOT org> <3B4EE2B2 DOT 10414 DOT 724246 AT localhost> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.2.5i |
In-Reply-To: | <3B4EE2B2.10414.724246@localhost>; from snowball3@bigfoot.com on Fri, Jul 13, 2001 at 11:59:46AM -0400 |
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 |
-: If we go with this library, then what happens now? For example, where -: should the library go, etc. I suppose DJ might add a new directory for the termcap functions, e.g., `/src/libc/posix/termcap'? Each termcap function gets its own source file, documentation file, etc., similar to existing djgpp libc organization. If I understood correctly a previous post by Eli, the termcap functions (they aren't that large) would simply be added to libc. Or are there other special reasons not to have a separate `libtermcap.a' ?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |