Re: Windows 7: fork in perl script spawns new cmd window

OK - so adding "call" like so

open(IN, "call svn info ... | ");
[download]

fixes the problem - but I'd still like to understand why this is needed in this new environment, and isn't needed on other W7 machines or older XP machines around here.

Michael

Comment on Re: Windows 7: fork in perl script spawns new cmd window Download Code

Replies are listed 'Best First'.
Re^2: Windows 7: fork in perl script spawns new cmd window by Anonymous Monk on Jan 25, 2013 at 10:08 UTC
Probably one calls the shell, and the other doesn't, see system/open and perl -V:sh Related perlrun Behind the GUI lives the Shell Windows Command Line Interpreter\|Shell\|DOS Prompt\|Batch Files\|Scripting Csh Programming Considered Harmful How Command Line Parameters Are Parsed http://www.gnu.org/software/bash/manual/bashref.html#Quoting String::ShellQuote/Win32::ShellQuote, Re: system() implementation on Windows (again), Re^3: system() implementation on Windows (again), Everyone quotes command line arguments the wrong way Proc::Background The Windows NT Command Shell exec always invokes the shell? win32, System, exec different behaviour with spaces	[reply]
Re^3: Windows 7: fork in perl script spawns new cmd window by mpeppler (Vicar) on Jan 25, 2013 at 13:01 UTC
It's from the exact same code, same build of perl 5.14, etc. The actual code uses IO::CaptureOutput, FWIW... Michael	[reply]
Re^4: Windows 7: fork in perl script spawns new cmd window by MidLifeXis (Monsignor) on Jan 25, 2013 at 13:36 UTC
Same versions of all ~~installed~~ used modules? --MidLifeXis	[reply]
Re^5: Windows 7: fork in perl script spawns new cmd window by mpeppler (Vicar) on Jan 25, 2013 at 15:10 UTC


"be consistent"
	PerlMonks