in reply to Re^6: how to supress stdout
in thread how to supress stdout

ikegami, I was commenting on observations we made on my last project (Strawberry perl on XP & Win2K3), where we resorted to using proper re-direction in a call to open() coz it (appeared to) work - having tried and failed to use it [proper redirection] in a DOS command window.

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^8: how to supress stdout
by ikegami (Patriarch) on Dec 13, 2008 at 17:23 UTC

    I don't understand. What do you mean by "proper redirection"? What other kind can it do?

    And what "is only true if the re-direction is done in the shell"?

      By 'proper redirection', I mean the redirection supported by *NIX, not the minimal redirection offered by Windoze.

      'Above will work only when a bourne-like shell (FreeBSD /bin/sh, bash, zsh, etc.) handles the redirection' ... is only true if the re-direction is done in the shell.

      A user level that continues to overstate my experience :-))

        'Above will work only when a bourne-like shell (FreeBSD /bin/sh, bash, zsh, etc.) handles the redirection' ... is only true if the re-direction is done in the shell.

        How can a shell handle redirection anywhere but in the shell?

        Still trying to understand what you wanted to communicate in Re^5: how to supress stdout. Your answers didn't help at all.