autotools is growing on me even though I still LOATHE the sh dependency.
-
-
-
Replying to @RichFelker
Until Microsoft specifically made concessions in the kernel to impl it in Windows 10, I don't consider sh native to Windows.
1 reply 0 retweets 0 likes -
Replying to @cr1901 @RichFelker
In any case, it really doesn't practically matter now. It's the historical "*nix is the One True OS" attitude I disliked.
2 replies 0 retweets 0 likes -
Replying to @cr1901
The attitude is that those who overcome differences to find consensus get to decide what's standard/universal.
2 replies 0 retweets 0 likes -
Replying to @RichFelker
I guess Windows would've had to figure out how to fake a fork(), which sh relies on, back in the NT days :P.
1 reply 0 retweets 0 likes -
Replying to @cr1901
sh in no way relies on fork. That's a legacy implementation detail that can't be used on nommu anyway.
2 replies 0 retweets 0 likes -
Replying to @RichFelker @cr1901
Subshells are convenient to implement lazily with fork, but you can also use proper data structures and marshall state to child.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
Marshall? You mean "give the child all the required state as an "input argument" (for lack of better) to starting the child".
1 reply 0 retweets 0 likes -
Replying to @cr1901
Yeah. Serialize the shell state (vars, functions, etc.) to a pipe or some other data channel the child shell reads and inits from.
1 reply 0 retweets 0 likes
You can also optimize-out subshells whose pids are never visible & implement them as a context in the original shell process.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.