Hi,

I can imagine this will be difficult to make complete, useful and bug free,
there are many issues that will appear.

I'd suggest saving a lot of time in development while still allowing the
feature in its earliest forms and leaving room for issues to be resolved at
will by providing hooks for a .so to replace the start, reap, and output
pipelines.

If you implement this by refactoring then the standard mechanism can be
available for extenders to use in the implementation.

The existing system with variables can be provided as a hello-world example
.so

Regards,
Tristan
On 29 May 2016 16:05, "Paul Smith" <psm...@gnu.org> wrote:

> On Sat, 2016-05-28 at 16:09 -0700, Josh Triplett wrote:
> > If make's own stdout/stderr refers to a PTY, make could create PTYs in
> > place of pipes, collect output that way, and synchronize it to its own
> > stdout/stderr as it does now.
>
> Just for clarity: GNU make doesn't use pipes to collect output, it uses
> IO redirection to temporary files.
>
> I don't see any serious issue with this proposal, as long as it's
> appropriately managed for portability.
>
> _______________________________________________
> Bug-make mailing list
> Bug-make@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-make
>
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Reply via email to