Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

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

I don't have IO::Scalar installed, so I can't help you with that module. However, you can do it without IO::Scalar in 5.8.0:

# This \$var syntax of open() requires Perl 5.8.0 or higher. use 5.8.0; my $input = "test\nfoo\nbar\n"; my $output = ''; my $code = 'print while (<STDIN>)'; { local *STDIN; open(STDIN, '<', \$input) or die("Can't open string for reading.\n"); local *STDOUT; open(STDOUT, '>', \$output) or die("Can't open string for writing.\n"); eval "$code"; } print("\$output contains:\n$output"); __END__ output ====== $output contains: test foo bar

A more general example:

# This \$var syntax of open() requires Perl 5.8.0 or higher. use 5.8.0; my $input = "test\nfoo\nbar\n"; open(my $old_stdin, "<&STDIN") or die("Can't dup STDIN: $!.\n"); close(STDIN); open(STDIN, '<', \$input) or die("Can't open string for reading\n"); my $output = ""; open(my $old_stdout, ">&STDOUT") or die("Can't dup STDOUT: $!.\n"); close(STDOUT); open(STDOUT, '>', \$output) or die("Can't open string for writing\n"); print($_) while (<STDIN>); print $old_stdout ("\$output contains:\n$output"); __END__ output ====== $output contains: test foo bar

In reply to Re: tieing STDIN & STDOUT using IO::Scalar for use inside an eval by ikegami
in thread tieing STDIN & STDOUT using IO::Scalar for use inside an eval by water

Title:
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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others about the Monastery: (4)
As of 2024-04-19 11:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found