🚀 go-pugleaf

In article <5662@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>
> [My own ramblings about CreatProc()'ing a process deleted]
>
>No, the clean way to do this is to send a workbench message. I published a
>complete package for starting programs in this environment, under the name
>"launch". Look for it at your nearest archive site.

Yes, but can it start *UNMODIFIED* CLI programs? They won't be running
properly when not started from CLI, and I  can't  imagine I  would  be
able to set pr_CIS and pr_COS in anyway. As I said, The problem in  my
case is to create sort of an  asynchronous  Execute().  This  includes
passing command line arguments in the standard  fashion  and  allowing
for pr_CIS and pr_COS to be set.


>If you don't do something like this the process will never get cleaned up
>after, and you'll eat memory every time you run it.

Well, actually the code I posted works just fine, even  in  the  sense
that it doesn't even lose one byte of memory.  Obviously  the  process
gets cleaned up perfectly, since I seem  to  have  fooled  the  OS  in
believing that it is a standard CLI process. Strange but true.


>Then you can add extra stuff you want to feed the program (like file handles)
>after the message. This is pretty much how RogueStart works (which is something
>else you should look into).

As I said, this is something I cannot do, since  the  programs  to  be
started are usually standard CLI programs, often to  the  effect  that
they can't or shouldn't be modified. Arrgh! I want fork()!

--
Christian Motz                                     root@dialog.sub.org