ruby - How important is adding quiet/verbose flags to new unix tools? -


I'm writing some Unix-style ruby ​​scripts that take the option flag. Generally, I write lots of STDOUT.puts and STDERR.puts in these scripts. Now I am wondering if the STDERR is a "good form" to put in the - verbose or -q flag to switch or turn on supportive output .

  • There are two arguments against doing so:

    1. This will make the program more complicated,
    2. User is already redirected to STDERR By logging outputs can silence / dev / null

    But again, one of the principles of Unix philosophy is that silence is golden, which means that always -Web mode mode But should it be stem with the principle of making small programs And who is not, who does one thing well?

    And the second question will be: If the mute / verbose flag is a good idea, should verbosity be the default ever?

    Can some UNIX programming gurus please advise?

  • Tools that I need to redirect to STDERR to turn them off. To support cool operation This is not too complicated.


    Comments

    Popular posts from this blog

    objective c - iPhone and it's wireless area -

    unix - Listing all shared memory segments used by a process on AIX5.3+ -

    .net - Self Tracking Entities (STE)'s and partial updates with EF4 and mVC2 -