yep, tried to analyze Attribute::Handlers but no time to dig into details.
in the meantime, here a hack that works: (plz ignore, see UPDATE)
package Foo;
use strict;
use Attribute::Handlers;
sub import {
my $pkg = (caller)[0];
eval <<"_code_";
sub ${pkg}::Sorted :ATTR {
print "all sorted"
}
_code_
}
1;
#!/usr/bin/perl
use strict;
use warnings;
use Foo;
$\="\n";
my $tst2 :Sorted;
print "done\n"
Beside of this:
I think attributes could be monkey patched to check a dedicated package like 'UNIVERSAL::attributes" for global attributes.
Cheers Rolf
( addicted to the Perl Programming Language)
UPDATE
less hacky, more stable!
package Foo;
use strict;
use Attribute::Handlers;
sub import {
my $src_pkg=__PACKAGE__;
my $dest_pkg = (caller)[0];
my $import = "sub ${dest_pkg}::Sorted :ATTR { goto \&${src_pkg}::Sor
+ted }";
eval $import;
}
sub Sorted {
print "all sorted"
}
1;
the essential problem is that :ATTR stores the combination of package and coderef for every new attribute to be able to identify them later via findsym().
-
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.
|