From owner-freebsd-hackers Tue Jun 24 06:01:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13093 for hackers-outgoing; Tue, 24 Jun 1997 06:01:45 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13086 for ; Tue, 24 Jun 1997 06:01:38 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id JAA17207; Tue, 24 Jun 1997 09:01:59 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id JAA15168; Tue, 24 Jun 1997 09:02:08 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 24 Jun 1997 09:02:07 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Steve Howe cc: Michael Smith , freebsd-hackers Subject: Re: BSD io In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Jun 1997, Steve Howe wrote: > i did - i initially wanted fast char i/o from/to vga, > preferably portable, so it seems as if S-Lang would've > been the "obvious" choice from the start, but none of Hehe. :) But this isn't what S-Lang does! As proof, S-Lang will (well, should... :) work under an xterm or a dumb-terminal, or ..., all of which make it impossible (or impractical) for slang to directly scan the video memory. > > S-Lang is a C programmer's library that includes routines for the rapid > > development of sophisticated, user friendly, multi-platform applications. > > The S-Lang library includes the following: "multi-platform" ... as in platforms that don't have VGA! :) > > Low level tty input routines for reading single characters at a time. > > Keymap routines for defining keys and manipulating multiple keymaps. > > High level screen management routines for manipulating both > > monochrome and color terminals. These routines are very "terminal", above, is a word used to suggest any screen which programs can output to. Screen, depending on the context, may be used to mean a much more restricted and lower-level view of the moniter & video card on a PC (or, it may not -- the word's a ambigious). > > Low level terminal-independent routines for manipulating the display > > of a terminal. "terminal" :) > > Uh. As this message is rated PG, I'll reserve my judgement on that one. > > huh? i have no idea what you are talking about, i spent years fine > tuning code and algorithms for certain things .... I would suggest that this results from a lack of common semantical and abstractional (good grief! WTF does that word mean? I'm starting to sound like Terry Lambert! ;) basis, rather than from the situation of two people trying to go two opposite directions (which is what the casual observer would probably believe :). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk