From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pertsserver.cs.uiuc.edu ([128.174.247.69]) by hawkwind.utcs.utoronto.ca with SMTP id <24648>; Wed, 2 Apr 1997 18:56:04 -0500
Received: (from mkgardne@localhost)
	by pertsserver.cs.uiuc.edu (8.8.5/8.8.5) id IAA28138;
	Wed, 2 Apr 1997 08:37:43 -0600 (CST)
Date:	Wed, 2 Apr 1997 09:37:43 -0500
Message-Id: <199704021437.IAA28138@pertsserver.cs.uiuc.edu>
From:	"Mark K. Gardner" <mkgardne@cs.uiuc.edu>
To:	rc@hawkwind.utcs.toronto.edu
Subject: Re: named pipe support (Was: autoconfig)
Reply-to: mkgardne@cs.uiuc.edu

[ On Tue, April 1, 1997 at 14:28:39 (-0500), Byron Rakitzis wrote: ]
> I am sorely tempted to remove named pipe support. It never worked
> properly. So something is needed to auto-sense the particular
> encoding for /dev/fd (systems encode this differently), which I
> doubt is supplied by GNU autoconf.

I must confess that as a new user of RC, I have not made use of the
named pipe feature. However, I have needed such a feature for a long
time. (Now that I know it is there I will definitely try it out.) I
would like to add my support for continuing the feature and fixing the
problems. Which brings up my next question. What are the problems with
named pipes as they are currently implemented?

-- 
Mark K. Gardner (mkgardne@cs.uiuc.edu)
University of Illinois at Urbana-Champaign
Real-Time Systems Laboratory
--