I'm somewhat uneasy about having coprocs inaccessible to each other.
I can foresee reasonable cases where I'd want a coproc to utilize one or
more other coprocs.

In particular, I can see cases where a coproc is written to by one process,
and read from by another.

Can we at least have the auto-close behaviour be made optional, so that it
can be turned off when we want to do something more sophisticated?

-Martin
          • ... Zachary Santer
          • ... Carl Edquist
          • ... Andreas Schwab
          • ... Zachary Santer
          • ... Carl Edquist
          • ... Chet Ramey
          • ... Martin D Kealey
          • ... Chet Ramey
          • ... Carl Edquist
  • Re: Examples o... Carl Edquist
    • Re: Examp... Martin D Kealey
      • Re: E... Chet Ramey
        • R... Zachary Santer
          • ... Chet Ramey
        • R... Carl Edquist
          • ... Chet Ramey
          • ... Zachary Santer
          • ... Chet Ramey
          • ... Carl Edquist via Bug reports for the GNU Bourne Again SHell
          • ... Chet Ramey
          • ... Carl Edquist

Reply via email to