You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's just a type that provides hasQualifiedName. It would be equally valid to use ClassOrInterface, a subtype of RefType that includes other reference-types (e.g. arrays), or Class or Interface depending on which one Context and InitialContext happen to be, but RefType suffices so the author hasn't bothered to restrict it further.
It's worth noting that if the types Context and InitialContext happen to match the requirements of a subtype, then Context will be compatible with that subtype even if it doesn't extend it. For example, Java defines
Where enclInRefType is a database relation (something populated by the extractor) which means that this occurs syntactically inside some other RefType, e.g. an inner class. Supposing for a moment that Context really was a Java nested class, even though Context directly extends RefType, we will be able to do things like from Context c where c.(NestedType).getEnclosingType().hasName("MyOuterClass") .... That is, we were able to cast Context, which extends RefType, to a NestedType even though it does not extend NestedType. The cast "worked" (that is, we got any results) because it matched NestedType's characteristic predicate enclInReftype(this, _).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The following class is declared to filter certain class,
So why does it extend the RefType class instead of any other base class?
All reactions