From: "Eli Zaretskii" <eliz@gnu.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: djgpp-workers@delorie.com, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org
Subject: Re: RFA: fix libiberty/pex-djgpp.c
Date: Thu, 12 May 2005 07:36:00 -0000 [thread overview]
Message-ID: <01c556c0$Blat.v2.4$b16011e0@zahav.net.il> (raw)
In-Reply-To: <m38y2lqjaw.fsf@gossamer.airs.com> (message from Ian Lance Taylor on 11 May 2005 22:17:43 -0400)
> 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.
prev parent reply other threads:[~2005-05-12 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 19:15 Eli Zaretskii
2005-05-11 23:13 ` Ian Lance Taylor
2005-05-11 23:31 ` Eli Zaretskii
2005-05-12 3:46 ` Ian Lance Taylor
2005-05-12 6:56 ` Ian Lance Taylor
2005-05-12 7:06 ` Eli Zaretskii
2005-05-12 7:36 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01c556c0$Blat.v2.4$b16011e0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=djgpp-workers@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ian@airs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox