Poonam Pahil am Mittwoch, 21. Dezember 2005 12.32: > Thanks for replying John. > > iam having a very limited choice in modifying the design.
hello Poonam Sorry, I meant the design of processes/subprocesses which would be bad if one could modify the parent's environment. > let me explain. > I want to write a perl script to automate the build process. > The normal manner is - > modify a file. > set up the build env.(use a *.cmd file) > start the build. > > I don't want to perform all this manually every time i make an exe. so i > wrote a perl script. > To set up the env. I have to use the *.cmd file . doing similar things in > the script will not be good. The only way i can do this is to use system or > exec() > I need control back so i use system. > In unix u can use the dot operator to make changes to the current > shell(env.). i have no idea in case of windows. > can you suggest anything better. I'm sorry no, since I threw windows away years ago. joe [history] > On 12/21/05, John Doe <[EMAIL PROTECTED]> wrote: > > Poonam Pahil am Mittwoch, 21. Dezember 2005 10.34: > > > Iam using the system command to call an application(windows) that sets > > > > up > > > > > the enviorment. as per my knowledge, a subshell would be created & > > > hence the modified enviorment would be lost once system returns to the > > > parent perl script. > > > > > > How can i modify the parent process enviornment in perl using system() > > > . > > > > You can't. > > > > Would be a very bad design if you could... > > > > hth, joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
