Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

based on Haj's example
use v5.12; use warnings; STDOUT->autoflush; STDERR->autoflush; STDIN->autoflush; say "Give me a cookie: "; my $thing = readline(STDIN); $thing =~ /^(a )?cookie$/ or warn "That was no cookie."; say "Thanks and goodbye!"; die "exiting here";

expected output in pre/tt

Give me a cookie:                                               # waits for input
croock                                                          # manual input             
That was no cookie. at line 10, <STDIN> line 1.  # jumps to line 10
Thanks and goodbye!
exiting here at line 14, <STDIN> line 1.         # jumps to line 14

For better understanding I manually added meta info

  • STDOUT in black
  • STDIN in red
  • STDERR resp. clickable cross-refs as hrefs
  • additional comments in grey

I've stumbled over a SO discussion which made this (half) work.

> C-u M-x compile and ... compilation buffer will be in comint mode, i.e. interactive.

(the C-u means prefix arg, a very e-lisp-ish annoyance)

I still have to find a way to make this work inside mode-compile

Cheers Rolf
(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery

In reply to Re: Prompting for input inside IDE (SSCCE) (half SOLVED) by LanX
in thread Prompting for input inside IDE run (was Reading from STDIN) by LanX

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.