Perhaps another monk can explain this behavior.
\&Foo::some_sub autovivifies a sub stub at run-time (just like sub Foo::some_sub; would at compile-time).
$ perl -le'
print(exists(&Foo::some_sub)?1:0, defined(&Foo::some_sub)?1:0);
$x=\&Foo::some_sub;
print(exists(&Foo::some_sub)?1:0, defined(&Foo::some_sub)?1:0);
eval "sub Foo::some_sub { print \"foo\" }";
print(exists(&Foo::some_sub)?1:0, defined(&Foo::some_sub)?1:0);
$x->();
'
00
10
11
foo
As demonstrated, this permits the reference to be taken to a sub that has yet to be defined.
\&Foo::some_sub creates glob entry at compile-time.
$ perl -le'
print(exists($Foo::{not_a_sub})?1:0);
print(exists($Foo::{some_sub})?1:0);
$x=\&Foo::some_sub;
'
0
1
-
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.
|