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)...
723 my %root_of; # The root directory of the file hierarchy
803 my %root_of; # The root directory of the file hierarchy
963 my %root_of; # The root directory of the file hierarchy
1150 in the new object's hierarchy. That is, when the constructor is called,
1172 hierarchy.
1183 classes in the name hierarchy do happen to have attributes of the same
1250 unique as well. If two classes in the hierarchy both need an initializer
1332 in the class's hierarchy to be called befre the constructor finishes.
1357 from all the classes in its inheritance hierarchy, are automatically cleaned
1366 C<DEMOLISH()> in I<all> the classes in the new object's hierarchy. That
1396 If two or more classes in a class hierarchy have separate C<AUTOLOAD()>
1403 other unrelated base class on their left in the hierarchy.
1410 hierarchy, trying each one in turn until one of them produces a
1415 hierarchy. If the first one can't handle a particular method call, it
1435 # (Next AUTOMETHOD() in hierarchy will then be tried instead)...
1681 accessed within a class's own hierarchy (that is, by derived classes). And
1686 that provide some internal service for a class, or a class hierarchy.
1692 outside a class's hierarchy. Methods marked C<:PRIVATE()> are modified
1750 hierarchy by remembering to call C<< $self->SUPER::BUILD() >>.
1756 accumulate through a class hierarchy, in the same way as those of
1767 same name throughout the entire hierarchy has been called.
1770 classes in a simple class hierarchy like so:
1855 the hierarchy, and hence only prints:
1868 object's hierarchy, and whose corresponding values are the return values of
1912 start at the base class(es) of the hierarchy and work downwards, the way
1973 FIRST)> on methods of the same name in the same hierarchy. The resulting
2136 same name in two classes within the same hierarchy. Since methods can only be
2137 called going strictly up through the hierarchy or going strictly down
2138 through the hierarchy, specifying both directions is obviously a mistake.
2151 anywhere in the object's class hierarchy. Did you misspell the method name, or
2169 subsequently called from outside its class hierarchy. Did you call the