I have gotten in the habit of using the cool lexically scoped file handles. 

open my $out, ">", $filename or die $!;

[download]

http://testers.cpan.org is just about the coolest thing ever; because, you can see how your modules hold up on platforms you don't actually have.

There are a number of testers still using perl 5.6.1, which doesn't handle my $out filehandles well. It seems to actually fail during the parser pass on a print $out Object->method() line. So I guess I could try print {$out} Object->method(). I don't think the open line is going to work though — but it's been a while since I've used perl 5.6, so who knows.

Questions: What is the most appropriate way to deal with the problem? Should I go back to open IN, $filename? Otherwise, how do I instruct ExtUtils::MakeMaker that the module won't load without perl 5.8? I can get the Makefile.PL to crash with use 5.008001;; but what will CPAN.pm do with that? Is that the correct way?

I'm mostly interested in the correct way to require perl 5.8 in a way that CPAN understands. But all comments are welcome obviously.

UPDATE: open my $c is apparently in the perl56delta. But I still wish to know how you'd handle a syntax that requires a certain later perl version.

-Paul

In reply to testers.cpan vs perl 5.8 by jettero

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.