🚀 go-pugleaf

In article <3151@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
.This is the bottom line. Execute() has serious brain damage, and I hope it's
.fixed in 1.4. However, there is a workaround. Have PROGB called in a workbench
>environment (CreateProc, then pass a startup message). PROGB can get its
.current directory from WBStartup->sm_ArgList[0].wa_Lock. The code to do this
.in the general case is available from the binary groups. It's completely clean,
.there's no fudges and kludges needed to do it, and you get absolute verific-
.ation that the program completed (your startup message is returned). If you
.like I will repost my example program.

This looks like it could be a partial solution.  Programs run by IconX
probably lose it, as IconX won't pass them startup messages.

>PATHs are irelevant to the Workbench, and presumably CLI users will be
>sophisticated enough to know how to do these themselves.

Don't count on it.

Keith Doyle
keithd@gryphon.COM    gryphon!keithd     gryphon!keithd@elroy.jpl.nasa.gov