Bug #58456 for IO-Prompt: 2 arg open

Show quoted text
Mainly because this module is not under active maintenance. In fact, its successor (IO::Prompter) is being readied for release this week, and does indeed to conform to much better coding practices including radical ideas like full user documentation and proper internal commenting. And, yes, it does employ proper 3-arg opens as well. ;-) Show quoted text
Even though an RT stream is imposed on every CPAN author's every module, not every CPAN author chooses to use the facility. For me, RT is just another email stream, one that usually brings bad news. ;-) Damian

Show quoted text
its Show quoted text
radical Show quoted text
yes, I'll be looking for that. If it's the successor perhaps I'd better use that instead of this for my conversion.

Show quoted text
It would certainly be worth assessing. It has a slightly different feature set to its predecessor, so it would probably depend on what you were using it for. Here's the quick summary from the IO::Prompter docs: Short Long form form Effect ===== ============= ====================================== -a -argv Prompt for @ARGV data if !@ARGV -comp[lete]=>SPEC Complete input on <TAB>, as specified -dSTR -def[ault]=>STR What to return if only <ENTER> typed -DEF[AULT]=>STR (as above, but skip any -must checking) -e[STR] -echo=>STR Echo string for each character typed -fail=>VALUE Return failure if input smartmatches value -guar[antee]=>SPEC Only allow the specified words to be entered -h[STR] -hist[ory][=>SPEC] Specify the history set this call belongs to -in=>HANDLE Read from specified handle -i -integer[=>SPEC] Accept only valid integers (that smartmatch SPEC) -k -keyletters Accept only keyletters (as specified in prompt) -l -line Don't autochomp -menu=>SPEC Specify a menu of responses to be displayed -must=>HASHREF Specify requirements/constraints on input -n -num[ber][=>SPEC] Accept only valid numbers (that smartmatch SPEC) -out=>HANDLE Prompt to specified handle -prompt=>STR Specify prompt explicitly -rSTR -ret[urn]=>STR After input, echo this string instead of <CR> -s -1 -sing[le] Return immediately after first key pressed -stdio Use STDIN and STDOUT for prompting -tNUM -time[out]=>NUM Specify a timeout on the input operation -v -verb[atim] Return the input string (no context sensitivity) -w -wipe Clear screen -wipefirst Clear screen on first prompt() call only -y -yes Return true if [yY] entered, false otherwise -yn -yesno Return true if [yY] entered, false if [nN] -Y -Yes Return true if Y entered, false otherwise -YN -YesNo Return true if Y entered, false if N -_ No-op (handy for bundling ambiguous short forms) It will be on CPAN by Tuesday June 22, 2010 Damian

I'm guessing -in would allow me to specify a way to provide the answers from like a __DATA__ section? will there be a way with argv to say answer default on all?

will there be a way to pass variables as answers besides handles? so then maybe one could add ... less ... linear way to program things... I imagine handles might be somewhat linear (or at least ugly). I'm thinking kinda like $return = prompt('question: ', -yn, -answer => "$input"); then I could combine with getopt to provide like an all yes or all no gives me more UI options basically. -- Caleb Cushing http://xenoterracide.blogspot.com

On Thu, Jun 17, 2010 at 6:30 PM, damian@conway.org via RT <bug-IO-Prompt@rt.cpan.org> wrote: Show quoted text
no not really but now that I think more about it, what I was thinking about really wouldn't be needed. -- Caleb Cushing http://xenoterracide.blogspot.com