🚀 go-pugleaf

In article <5674@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>
>ALL programs should be written to support being launched from either the
>Workbench or the CLI, so this translates to "this only works for non-buggy
>programs". Which is fine by me. The CLI startup environment is a crock
>anyway.

In my case the MAIN program supports being launched either from WB or CLI
which isn't very difficult 'cause I dont use stdio or cli-arguments, but
the sub-programs being "launched" from the MAIN (and only from the main)
shouldn't have to bother about WB or CLI. All I want to is to start them,
send them a message containing the address of the costomscreen I use,
and when they exit let the MAIN program do the unloading.


>
>And, of course, if you're writing the launchee as well as the launcher you can
>go wild...

In my case i could go wild, but since your launch package does,almost,
all the work I'll use it. THe irritating part is that I'll have to allocate
and send an extra message to the child, with the address to the screen.
But this is a minor nuisance with which I'll have to live.
Thanks anyway for you launch program.

					Karl
ps. That pic. in your .sig is that to be Australia?

---

Karl Hultland,(d87-khd@sm.luth.se)
University of Lulea,Sweden

Egoist: a person of low taste, more interested in himself than in me.
						- A. Bierce