Hi broquaint, I've just downloaded the code from Sub::Lexical and done some tests of my own, and it seems to me that your subs now have local scope:

#!/usr/bin/perl -w use strict; use lib '.'; use Sub::Lexical; my sub testsub { print "testsub 1 called\n"; } my sub outersub { print "outersub called\n"; testsub(); } for (1) { my sub testsub { print "testsub 2 called\n"; } testsub(); outersub(); }

This outputs:

testsub 2 called outersub called testsub 2 called

While it probably SHOULD give:

testsub 2 called outersub called testsub 1 called
Because the first testsub() declaration is in lexical scope for outersub()

This could be considered a feature, if you just rename your module to Sub::Local... :-)

-- Joost downtime n. The period during which a system is error-free and immune from user input.

In reply to Re: Re: Concurrent lexical scopes? by Joost
in thread Concurrent lexical scopes? by broquaint

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.