wperl.exe vs perl.exe

Nalina has asked for the wisdom of the Perl Monks concerning the following question:

Hi monks,
What happens if I use wperl.exe instead of perl.exe? What r the other substitutes for perl.exe? _{janitored by ybiC: Retitle from "wperl.exe" because one-word node titles hinder site search}

Comment on wperl.exe vs perl.exe

Replies are listed 'Best First'.
Re: wperl.exe vs perl.exe by Corion (Patriarch) on Aug 16, 2004 at 06:49 UTC
The `wperl.exe` command under Windows starts Perl without attaching it to a console. This means that if you associate for example the file extension `.wpl` with `wperl.exe`, double-clicking `test.wpl` will not pop up a console window with text scrolling by. This is very convenient if your Perl script is written using Win32::GUI or some other windowing toolkit. Using `wperl.exe` and thus not having a console attached also has a drawback - STDIN,STDOUT and STDERR are not available, so you will need to reopen them to some log files if you output any text via `print` or `warn`.	[reply]
Re^2: wperl.exe vs perl.exe by Nalina (Monk) on Aug 16, 2004 at 07:13 UTC
will wperl.exe run continuesly unless it is terminated by opening Task Manager and terminating wperl.exe process? If not how do I do it?	[reply]
Re^3: wperl.exe vs perl.exe by Corion (Patriarch) on Aug 16, 2004 at 07:25 UTC
`wperl.exe` will exit when your script exits. Simple as that. If your script never exits of itself, and has no method in it for you to terminate it, then you will have to terminate it through the task manager.	[reply]


Do you know where your variables are?
	PerlMonks