Ok, I'm getting annoyed. Quit babbling about fork().
Fork is HARD to support and has less portable semantics than Process.create_process(). Yes, there are some instances when it would be useful but it WILL NOT be supported in Pike with threads.
Personally I don't care if it is POSIX or not, because while POSIX may be a standard, it is a backwards and awkward standard that doesn't actually allow you to write useful applications. On top of that, many OS only implement parts of POSIX or have bugs in some of their POSIX calls. Using POSIX as a guide for Pike APIs is like using ASCII as a guide for drawing fonts.
/ Fredrik (Naranek) Hubinette (Real Build Master)
Previous text:
2002-09-03 17:50: Subject: argv[0]?
What about people other than "we"? As Lief (I think) stated fork() is at the base of any *nix system whether one likes it or not - as such, it is very useful since pike runs on many *nix systems...
/ Marek Habersack (Grendel)
You could at least read what I wrote. Fine, I am babbling, but I'm not alone in it. Dammit, I never said that Pike should be GUIDED by POSIX, I merely proposed (and I do regret that I spoke AT ALL) that a POSIX damned module is created! If it bothers you so much, then be it - I don't give a damn.
/ Marek Habersack (Grendel)
Previous text:
2002-09-03 22:38: Subject: argv[0]?
Ok, I'm getting annoyed. Quit babbling about fork().
Fork is HARD to support and has less portable semantics than Process.create_process(). Yes, there are some instances when it would be useful but it WILL NOT be supported in Pike with threads.
Personally I don't care if it is POSIX or not, because while POSIX may be a standard, it is a backwards and awkward standard that doesn't actually allow you to write useful applications. On top of that, many OS only implement parts of POSIX or have bugs in some of their POSIX calls. Using POSIX as a guide for Pike APIs is like using ASCII as a guide for drawing fonts.
/ Fredrik (Naranek) Hubinette (Real Build Master)
pike-devel@lists.lysator.liu.se