| Interface | Description |
|---|---|
| TypeSet.Resolver |
TODO should Resolver provide a canResolve() and a resolve()? Requiring 2
calls seems clunky...
|
| Class | Description |
|---|---|
| ClassNameDeclaration | |
| ClassScope | |
| LocalScope | |
| MethodNameDeclaration | |
| MethodScope | |
| NameFinder | |
| OccurrenceFinder | |
| PLSQLNameOccurrence | |
| ScopeAndDeclarationFinder |
Visitor for scope creation.
|
| Search | |
| SourceFileScope | |
| SymbolFacade | |
| TypeSet |
Keeps track of the types encountered in a ASTinput
|
| TypeSet.CurrentPackageResolver | |
| TypeSet.ExplicitImportResolver | |
| TypeSet.FullyQualifiedNameResolver | |
| TypeSet.ImplicitImportResolver | |
| TypeSet.ImportOnDemandResolver | |
| TypeSet.PrimitiveTypeResolver | |
| TypeSet.VoidResolver | |
| VariableNameDeclaration |
Copyright © 2002–2018 PMD. All rights reserved.