That being said, if you want to prevent the method itself from being called on behalf of an object of a derived class, just call it a submethod instead, and then the derived class will have to define its own version of the submethod that will presumably refer to its own class attributes. I suspect that in general most class attributes are of interest only to infrastructural methods like constructors and initializers and destructors, and most of those should be submethods in the first place.
If a method ever has to ask what the actual type of its invocant it, it's usually a clue that something is seriously wrong in the design of either the program or the language. It's the dispatcher that should be making those kinds of decisions before your method is ever called. Perl 6 provides several degrees of freedom in the dispatcher to help you keep that sort of infrastructural spaghetti out of your methods.
Of course, we won't prevent you from examining the actual type of the invocant if you really want to...
In reply to Re^7: How will you use state declared variables in Perl6?
by TimToady
in thread How will you use state declared variables in Perl6?
by Limbic~Region
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |