Re: Should make handle non-blocking jobserver and use socket pair instead?

2019-09-03 Thread Paul Smith
On Thu, 2019-08-15 at 17:26 +0300, Juha-Matti Tilli wrote: > GNU make expects the jobserver to be blocking, whereas a program > based on an event-loop architecture should really be using non- > blocking file descriptors. Well, GNU make invented the jobserver concept, and GNU make is not an

Re: Should make handle non-blocking jobserver and use socket pair instead?

2019-08-16 Thread Juha-Matti Tilli
On Thu, Aug 15, 2019 at 7:04 PM Howard Chu wrote: > The jobserver was designed using a pipe because that is the least common > denominator > for IPC across POSIX systems - it worked across all flavors of Unix in > existence in 1991, > and continues to work unchanged to this day with no special

Re: Should make handle non-blocking jobserver and use socket pair instead?

2019-08-15 Thread Howard Chu via Bug-make
Juha-Matti Tilli wrote: > Hello, > > (Please CC me, I’m not on the list) The jobserver was designed using a pipe because that is the least common denominator for IPC across POSIX systems - it worked across all flavors of Unix in existence in 1991, and continues to work unchanged to this day

Should make handle non-blocking jobserver and use socket pair instead?

2019-08-15 Thread Juha-Matti Tilli
Hello, (Please CC me, I’m not on the list) I’m creating a new build system that is supposed to solve many of the issues of standard make. Most programmers who create alternative build systems (SCons, Rake, Shake) do so by selecting an alternative programming language (Python, Ruby, Haskell),