>>55
12 arguments over several that take just one or two. it's MUCH clearer to read that way and MUCH more efficient.
I don't thing the word ``efficient'' means what you think it means.
It doesn't mean "sparing the programmer the need to read manuals (especially if he is too stupid to understand which parameters he don't need by the short description)". Use the expression "easy to use" for that, please.
But well, mr. Unix Programmer, it seems to me that you are a piece of pretentious shit, not a real programmer, and I have a very nice little question that would simultaneously prove it and show the real "efficiency" and "ease of use" of UNIX. The code presented in
>>43 contains a serious defect: when the parent process is killed all spawned processes are killed as well and until parent process quits, even terminated spawned processes just sit there waiting for someone to call `waitpid` on them.
Would you kindly explain the steps required from the programmer to understand source of the problem and find the proper way to fix it, then assess both the readability and the efficiency of the solution.