From owner-freebsd-hackers  Tue Jul 22 23:20:00 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA27266
          for hackers-outgoing; Tue, 22 Jul 1997 23:20:00 -0700 (PDT)
Received: from precipice.shockwave.com (ppp-206-170-5-195.rdcy01.pacbell.net [206.170.5.195])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA27258
          for <hackers@FreeBSD.ORG>; Tue, 22 Jul 1997 23:19:57 -0700 (PDT)
Received: from shockwave.com (localhost [127.0.0.1]) by precipice.shockwave.com (8.8.6/8.7.3) with ESMTP id XAA13468; Tue, 22 Jul 1997 23:17:39 -0700 (PDT)
Message-Id: <199707230617.XAA13468@precipice.shockwave.com>
To: Marc Slemko <marcs@znep.com>
cc: hackers@FreeBSD.ORG
Subject: Re: how to tell if getchar() will block -- select doesn't cut it 
In-reply-to: Your message of "Wed, 23 Jul 1997 00:18:40 MDT."
             <Pine.BSF.3.95.970723001420.24312B-100000@alive.znep.com> 
Date: Tue, 22 Jul 1997 23:17:39 -0700
From: Paul Traina <pst@shockwave.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Yeah, I had thought of that, however, that means that the whole code-loop
is forced to become non-blocking aware.  I use that technique in some
other places in related code.

Thanks for the idea though,

Paul