From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-39363-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 6594 invoked by alias); 12 May 2005 07:06:21 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 6477 invoked from network); 12 May 2005 07:06:02 -0000
Received: from unknown (HELO romy.inter.net.il) (192.114.186.66)
  by sourceware.org with SMTP; 12 May 2005 07:06:02 -0000
Received: from zaretski (IGLD-83-130-254-105.inter.net.il [83.130.254.105])
	by romy.inter.net.il (MOS 3.5.6-GR)
	with ESMTP id BEV51568 (AUTH halo1);
	Thu, 12 May 2005 10:05:42 +0300 (IDT)
Date: Thu, 12 May 2005 07:36:00 -0000
From: "Eli Zaretskii" <eliz@gnu.org>
To: Ian Lance Taylor <ian@airs.com>
Message-ID: <01c556c0$Blat.v2.4$b16011e0@zahav.net.il>
Content-Transfer-Encoding: 7BIT
Content-Type: text/plain; charset=ISO-8859-1
CC: djgpp-workers@delorie.com, gcc-patches@gcc.gnu.org,
        gdb-patches@sourceware.org
In-reply-to: <m38y2lqjaw.fsf@gossamer.airs.com> (message from Ian Lance Taylor
	on 11 May 2005 22:17:43 -0400)
Subject: Re: RFA: fix libiberty/pex-djgpp.c
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <01c5565c$Blat.v2.4$082130a0@zahav.net.il>
	<m3y8alqzgx.fsf@gossamer.airs.com>
	<01c55680$Blat.v2.4$9ebe4740@zahav.net.il> <m38y2lqjaw.fsf@gossamer.airs.com>
X-SW-Source: 2005-05/txt/msg00266.txt.bz2

> Cc: djgpp-workers@delorie.com, gcc-patches@gcc.gnu.org,
>   gdb-patches@sourceware.org
> From: Ian Lance Taylor <ian@airs.com>
> Date: 11 May 2005 22:17:43 -0400
> 
> > It's not easy to figure out what is needed and in what conditions.  It
> > would be nice if this machinery were to be documented a bit more
> > methodically.  Right now, the information is scattered between
> > pex-common.h, include/libiberty.h and a few comments in pex-*.c files.
> 
> Don't forget pexecute.txh.

Yes, but what's missing from all of these places is the overview (or
an example) of how would one go about running a pipeline of processes
using these functions, and a guided walk through the orchestrated
operation of these functions during such a pipeline, which would
explain the importance of each one in the process.  The pieces are
there, but the glue is missing, and since there are so many pieces and
tiny details, one can easily get lost in them.