On 18 Feb 2004 at 3:11, Autrijus Tang wrote: > On Tue, Feb 17, 2004 at 10:25:25AM -0800, Alan Stewart wrote: > > The work-around I mentioned below is overkill and prevents having systems defaults > > for > > PAR_TEMP, PAR_CLEAN and PAR_DEBUG getting to the second exe. > > Nice catch. > > So all we have to do is to first copy the original envs into _PAR_TEMP > and _PAR_CLEAN, *then* modify them, so they apply to this exe only. > That way PAR_CLEAN/PAR_TEMP will not change and will be picked up > verbatim by the next .exe. >
I was thinking a little different. If the user wants system wide defaults, he/she sets SYS_PAR_xxx before running PAR apps. The static.c or unspawned main.c/par.pl starts by deleting PAR_xxx and setting them to any SYS_PAR_xxx, ignoring the incoming PAR_xxx. The rest of the code is unchanged, including any user PAR scripts that have been written to look at PAR_xxx variables already. Less patching, but whaddya think? Alan Stewart
