Lines Matching refs:hierarchy
216 my @hierarchy = $class;
220 push @hierarchy, $parent;
229 } grep !$seen{$_}++, @hierarchy;
242 my @hierarchy = $class;
246 push @hierarchy, $parent;
255 } grep !$seen{$_}++, @hierarchy;
272 # Implement restricted methods (only callable within hierarchy)...
722 my %root_of; # The root directory of the file hierarchy
802 my %root_of; # The root directory of the file hierarchy
962 my %root_of; # The root directory of the file hierarchy
1149 in the new object's hierarchy. That is, when the constructor is called,
1171 hierarchy.
1182 classes in the name hierarchy do happen to have attributes of the same
1249 unique as well. If two classes in the hierarchy both need an initializer
1331 in the class's hierarchy to be called befre the constructor finishes.
1356 from all the classes in its inheritance hierarchy, are automatically cleaned
1365 C<DEMOLISH()> in I<all> the classes in the new object's hierarchy. That
1395 If two or more classes in a class hierarchy have separate C<AUTOLOAD()>
1402 other unrelated base class on their left in the hierarchy.
1409 hierarchy, trying each one in turn until one of them produces a
1414 hierarchy. If the first one can't handle a particular method call, it
1434 # (Next AUTOMETHOD() in hierarchy will then be tried instead)...
1680 accessed within a class's own hierarchy (that is, by derived classes). And
1685 that provide some internal service for a class, or a class hierarchy.
1691 outside a class's hierarchy. Methods marked C<:PRIVATE()> are modified
1749 hierarchy by remembering to call C<< $self->SUPER::BUILD() >>.
1755 accumulate through a class hierarchy, in the same way as those of
1766 same name throughout the entire hierarchy has been called.
1769 classes in a simple class hierarchy like so:
1854 the hierarchy, and hence only prints:
1867 object's hierarchy, and whose corresponding values are the return values of
1911 start at the base class(es) of the hierarchy and work downwards, the way
1972 FIRST)> on methods of the same name in the same hierarchy. The resulting
2135 same name in two classes within the same hierarchy. Since methods can only be
2136 called going strictly up through the hierarchy or going strictly down
2137 through the hierarchy, specifying both directions is obviously a mistake.
2150 anywhere in the object's class hierarchy. Did you misspell the method name, or
2168 subsequently called from outside its class hierarchy. Did you call the