It seems that if the MODE parameter in a three args open contains IO layers and the third one is a scalar reference, then the latter is not open()ed in memory, but its stringification is interpreted as a filename:

picard:~ [10:30:46]$ perl -MFatal=open -e 'open F, "<", \"foo"' picard:~ [10:31:02]$ ^<^<:raw perl -MFatal=open -e 'open F, "<:raw", \"foo"' Can't open(F, <:raw, SCALAR(0x814fe04)): No such file or directory at +(eval 1) line 3 main::__ANON__('F', '<:raw', 'SCALAR(0x814fe04)') called at -e + line 1

and

picard:~ [10:35:09]$ perl -MFatal=open -e 'open F, ">", \$a' picard:~ [10:35:11]$ ^>^>:raw perl -MFatal=open -e 'open F, ">:raw", \$a' picard:~ [10:35:34]$ ls SCALAR\(0x814fe04\) SCALAR(0x814fe04)

Is this expected, documented, etc? I don't see anything in open()'s documentation to this effect...


In reply to Clash between IO layers and "in memory" files? by blazar

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.