[Octave-bug-tracker] [bug #45625] fork on command line

[Mike Miller]

Follow-up Comment #10, bug #45625 (project octave):

I'm personally not a fan of safety features that get in the way of utility,
and this looks like it could be useful for experimentation, so in my opinion
we should let fork be called.

As a point of comparison, a Python interactive shell lets me call os.fork(),
and the terminal seems to be in control of the child process most times, so I
can then sys.exit(), but os.waitpid(0,0) says I have no child processes.

My point being it's not at all friendly or well-defined what an interactive
shell should do or could do to handle fork better, but why not let users call
it if they know what they're doing?

So that just leaves the problem of Qt causing our waitpid function to hang.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45625>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/