in reply to Re: Re: win32/unix compatible script
in thread win32/unix compatible script
my $in = new FileHandle "<&STDIN"; my $out = new FileHandle ">&STDOUT"; autoflush $out;
What this allows you to do is to treat STDIN and STDOUT (keyboard and monitor, essentially) as if they were any old descriptor. Thus, you can have a commandline app that doesn't care if it's talking to a person at the keyboard or a telnet session.
This works under Unix cause everything in Unix is treated (for all practical purposes) as if it's happening on a VT-100 terminal. Each window is treated by the kernel as its own process with its own input and output. The input and output (generally) is the same for all your windows, but the kernel doesn't make that optimization.
Windows does, which means that STDIN isn't an attribute of a given window, but of the OS as a whole. Thus, the problem.
It's easy to get around - you just have to telnet to yourself. :)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Re: Re: win32/unix compatible script
by John M. Dlugosz (Monsignor) on Jul 14, 2001 at 00:09 UTC | |
by dragonchild (Archbishop) on Jul 14, 2001 at 00:13 UTC | |
by John M. Dlugosz (Monsignor) on Jul 14, 2001 at 00:34 UTC | |
by dragonchild (Archbishop) on Jul 16, 2001 at 16:48 UTC | |
by John M. Dlugosz (Monsignor) on Jul 16, 2001 at 19:05 UTC | |
|