Re: Hiding DOS windows that accompany TK

If you launch your app with wperl.exe (which is also in your perl/bin folder), instead of perl.exe, then that DOS window might not get created ... not sure ...

Cheers,
Rob

Comment on Re: Hiding DOS windows that accompany TK

Replies are listed 'Best First'.
Re^2: Hiding DOS windows that accompany TK by TGI (Parson) on Dec 08, 2008 at 19:27 UTC
wperl is the correct answer. It runs perl as a "WINDOWS" subsystem application. Normally perl runs as a "CONSOLE" subsystem application. Without a console, your perl script will not have a proper STDIN, STDOUT, or STDERR. Perl does the best it can to paper over the problems, but doing IO redirection with child processes can be troublesome. exetype.bat in the perl/bin directory converts the console version of perl into a WINDOWS subsystem app. See the MSDN article on the SUBSYSTEM linker option for MSVC for a tiny bit of info. TGI says moo	[reply]

Replies are listed 'Best First'.

Re^2: Hiding DOS windows that accompany TK
by TGI (Parson) on Dec 08, 2008 at 19:27 UTC

wperl is the correct answer. It runs perl as a "WINDOWS" subsystem application. Normally perl runs as a "CONSOLE" subsystem application.

Without a console, your perl script will not have a proper STDIN, STDOUT, or STDERR. Perl does the best it can to paper over the problems, but doing IO redirection with child processes can be troublesome.

exetype.bat in the perl/bin directory converts the console version of perl into a WINDOWS subsystem app.

See the MSDN article on the SUBSYSTEM linker option for MSVC for a tiny bit of info.

TGI says moo

[reply]