Mark Hammond wrote:
> Doug Turner wrote: > >> >> How about adding a GetEnv/SetEnv method to the following interface: >> >> http://lxr.mozilla.org/seamonkey/source/xpcom/threads/nsIProcess.idl > > > > That doesn't really make alot of sense. GetEnv/SetEnv make sense more > for the *current* process than for child processes. Adding these > methods to an interface designed to spawn children may imply that they > can be used at any time - whereas they are relly only meaningful before > the child has started. > > An nsICurrentProcess may make more sense - then we can add cwd and other > useful functionality. > > Mark. Why limit yourself to the current application? What not allow child processes have different system environments than the parent where possible? This is what I do all of the time. My debugger has a different env than my shell sessions. I spawn my debugger from my shell. I do not see what the point of a nsICurrentProccess is when the current process can just implement nsIProcess and have some service return it. Oh well, it is too early in the morning for this. I need to get some coffee. Doug Turner
