On 3/9/07, Andreas J. Koenig <[EMAIL PROTECTED]> wrote:
Sure can we. If you would let the user use his terminal the way it was
designed. STDIN closed means: there's nothing to expect. User can do
this by "< /dev/null". Because we want to support more than one way:
PERL_MM_USE_DEFAULT=1 is the second way to get defaults only. The
third one is to pipe "yes ''|" to the Build.PL. I'm sure there are
plenty more ways.
Everything else shall wait for an answer, period. I have a right to
see the questions and I have a right to answer them. It's my decision
where I redirect the questions to and how I enter the answers. Please
don't get in the way.
I've got to back up Andreas on this one.
Read on STDIN and write to STDOUT. If STDIN is closed or exhausted,
used defaults. PERL_MM_USE_DEFAULTS just means use defaults even if
STDIN is available. I'm not sure what to do in the case of STDOUT
being closed, but I'd still think you'd only want to stop sending to
it, but would still want to read from STDIN in case it's some batch
operation.
Leave it to the user after that and document it. It wouldn't take
much of a cookbook to highlight the issues and show how to deal with
it.
David
