$x is some attribute of some node. Associated with that attribute is a (possibly empty) list, @kabluther of callbacks to other nodes associated with this node by this attribute.
Sorry, you misunderstood me. @kabluther has nothing whatsoever to do with $x or callbacks. It's just an example of some sort of processing that might occur. The example could also be
onTime {
our $pos : Attr('position');
our $active;
if ($active) {
$pos->[0]++;
}
}
or
onTime {
our $x : Attr('something');
our @fixups;
foreach (@fixups) {
$x += $_;
}
@fixups = ();
}
The "callbacks" I was referring to are behind the scenes. Here's an example of the previous code sample, without using the new "simplified" API:
onTime {
my $attr = $NODE->getAttr("something");
my $val = $attr->getValue();
foreach (@fixups) {
$val += $_;
}
@fixups = ();
$attr->setValue($val);
$attr->doCallbacks();
}
That's how it would be written with the current API, unless they wanted to suppress the possibly unneeded callbacks, in which case they would spell it:
onTime {
my $attr = $NODE->getAttr("something");
my $val = $attr->getValue();
my $was_updated = 0;
foreach (@fixups) {
$val += $_;
$was_updated = 1;
}
@fixups = ();
if ($was_updated) {
$attr->setValue($val);
$attr->doCallbacks();
}
}
-
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.