it is as usual difficult to tell if everyone is being serious about wanting to see perldoc perlop extended here or if everyone is pitching arguments against because of the complexity of a comprehensive patch.
On Wed, 02 Mar 2005 06:18:54 +0800, Dan Jacobson <[EMAIL PROTECTED]> wrote: > D> qx// ... should mention that the process inherits perl's stdin > D> unless it's redirected. > > Sounds good. Also include examples of the right way to do > $output=qx/command/<<EOF > input > EOF > instead of > $output=qx/command<<EOF > input > EOF > / you of course got these backwards -- the pertinent fact is that qx can take multiple lines print <<`/` echo one echo two wc<<EOF 1 2 3 4 EOF / did what I meant. > and > [I have no idea] > instead of > $output=qx/echo $input|command/ > i.e., how to input small things to qx without disrupting other parts > of the program or relying on /bin/sh constructions to get the input > connected. yeah that's clearly the way to input small things to a command. The alternative, something like assigning half of a socketpair to a localized *STDIN, or forgoing qx for some variety of open-pipe syntax, would not be appropriate for inclusion in qx docs. A pointer to perldoc -f open could be appropriate too, and would include by reference the myriad documents referred to therefrom. Perhaps "STDIN is inherited as well. For far more than you ever wanted to know about file handles, see the documentation of perl's open function." -- David L Nicol "all the king's horses and all the king's men and all the king's idiot sons ain't never in all of their glorious battles solved anything with a gun" -- Tonio K (Trouble, 1978)
