org.apache.flex.compiler.internal.definitions

Class AmbiguousDefinition

java.lang.Object

org.apache.flex.compiler.internal.definitions.DefinitionBase

org.apache.flex.compiler.internal.definitions.AmbiguousDefinition

All Implemented Interfaces:

IDefinition, IDocumentableDefinition, IDefinitionSet

public final class AmbiguousDefinition
extends DefinitionBase
implements IDefinition

IDefinition marker to represent ambiguous results. TODO: Can modify to keep track of what the ambiguous results were. This would be an improvement over TODO: ASC, which only reported that a reference was ambiguous, but didn't tell you which symbols it matched.

Field Summary

Fields inherited from class org.apache.flex.compiler.internal.definitions.DefinitionBase

FLAG_CAST_FUNCTION, FLAG_CONSTRUCTOR, FLAG_CONTINGENT, FLAG_DECLARED_IN_CONTROL_FLOW, FLAG_DEFAULT, FLAG_DEPRECATED, FLAG_DYNAMIC, FLAG_FINAL, FLAG_GENERATED_EMBED_CLASS, FLAG_HAS_INIT, FLAG_IMPLICIT, FLAG_NATIVE, FLAG_OVERRIDE, FLAG_REST, FLAG_STATIC, flags, nodeRef, singletonEmptyMetaTags

Method Summary

Methods

Modifier and Type	Method and Description
static AmbiguousDefinition	get() Get the AmbiguousDefinition instance - currently there is only 1 AmbiguousDefinition instance, but we may modify that if each AmbiguousDefinition needs to keep track of it's ambiguous results
static boolean	isAmbiguous(IDefinition d) Is the definition passed in an AmbiguousDefinition.
boolean	isInProject(ICompilerProject project) Debugging method that can be used to assert that a definition is a specified project.
static IDefinition	resolveAmbiguities(ICompilerProject project, List<IDefinition> defs) Helper method to resolve apparently ambiguous results - there are 2 cases where we what looks like an ambiguity is not - getter/setter pairs, and legally re-declared local variables If we have a getter and a setter, we will end up with 2 resulting definitions, but we don't want to report them as ambiguous if they are a getter & setter for the same property. in this case, this method arbitrarily returns the first definition passed in - this should be ok because getter and setter definitions have methods to access the other one (resolveCorrespondingAccessor), so callers can use that to get at the one they want.

Methods inherited from class org.apache.flex.compiler.internal.definitions.DefinitionBase

addMetaTag, buildInnerString, buildString, getAbsoluteEnd, getAbsoluteStart, getAllMetaTags, getAncestorOfType, getArrayElementType, getBaseName, getBindableEventNames, getColumn, getContainingASScope, getContainingFilePath, getContainingScope, getContainingSourceFilePath, getDefinition, getDeprecationInfo, getEnd, getExplicitSourceComment, getFileScope, getFileSpecification, getInstanceType, getLine, getLocationString, getMaxSize, getMetaTagByName, getMetaTagsByName, getMName, getModifiers, getNameColumn, getNameEnd, getNameLine, getNamespaceReference, getNamespaceReferenceAsString, getNameStart, getNode, getPackageName, getParent, getPercentProxy, getQualifiedName, getSize, getSkinPart, getSourcePath, getStart, getStorageName, getTypeAsDisplayString, getTypeDependencyType, getTypeReference, hasCollapseWhiteSpace, hasExplicitComment, hasMetaTagByName, hasModifier, hasNamespace, hasRichTextContent, inPackageNamespace, isBindable, isBindableStyle, isColor, isContingent, isContingentNeeded, isDeprecated, isDynamic, isEmpty, isFinal, isGeneratedEmbedClass, isImplicit, isInternal, isNative, isOverride, isPrivate, isProtected, isPublic, isRequiredSkinPart, isStatic, isTopLevelDefinition, matches, resolveNamespace, resolveType, resolveType, resolveType, resolveType, resolveType, setBindable, setContainingScope, setContingent, setDynamic, setFinal, setGeneratedEmbedClass, setImplicit, setLocation, setMetaTags, setModifier, setNameLocation, setNamespaceReference, setNative, setNode, setOverride, setPublic, setStatic, setTypeReference, toStorageName, toString, unsetOverride, verify

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Methods inherited from interface org.apache.flex.compiler.definitions.IDefinition

getAbsoluteEnd, getAbsoluteStart, getAllMetaTags, getAncestorOfType, getBaseName, getBindableEventNames, getColumn, getContainingFilePath, getContainingScope, getContainingSourceFilePath, getDeprecationInfo, getEnd, getLine, getMetaTagByName, getMetaTagsByName, getModifiers, getNameColumn, getNameEnd, getNameLine, getNamespaceReference, getNameStart, getNode, getPackageName, getParent, getQualifiedName, getSourcePath, getStart, getTypeAsDisplayString, getTypeReference, hasMetaTagByName, hasModifier, hasNamespace, isBindable, isBindableStyle, isContingent, isContingentNeeded, isDeprecated, isDynamic, isFinal, isGeneratedEmbedClass, isImplicit, isInternal, isNative, isOverride, isPrivate, isProtected, isPublic, isStatic, resolveNamespace, resolveType

Method Detail

isAmbiguous

public static boolean isAmbiguous(IDefinition d)

Is the definition passed in an AmbiguousDefinition.

Parameters:

d - the definition to check

Returns:

true if d is an AmbiguousDefinition

get

public static AmbiguousDefinition get()

Get the AmbiguousDefinition instance - currently there is only 1 AmbiguousDefinition instance, but we may modify that if each AmbiguousDefinition needs to keep track of it's ambiguous results

resolveAmbiguities

public static IDefinition resolveAmbiguities(ICompilerProject project,
                             List<IDefinition> defs)

Helper method to resolve apparently ambiguous results - there are 2 cases where we what looks like an ambiguity is not - getter/setter pairs, and legally re-declared local variables If we have a getter and a setter, we will end up with 2 resulting definitions, but we don't want to report them as ambiguous if they are a getter & setter for the same property. in this case, this method arbitrarily returns the first definition passed in - this should be ok because getter and setter definitions have methods to access the other one (resolveCorrespondingAccessor), so callers can use that to get at the one they want. If we have the same variable declared multiple times, then we don't want to report access to that variable as ambiguous. A variable can be legally re-declared when: 1. It is declared at global scope (outside a package), or it is a local var in a function. 2. All of the declarations of that variable are declared with the same type, or '*'. One of the VariableDefinitions with the specific type will be returned so that the correct type is used by the compiler e.g. if a Variable is declared twice, once as * and once as String, the result of this method will be the VariableDefinition typed as String. If all the VariableDefinitions are declared with the same type, then one will be arbitrarily returned.

Parameters:

project - The Project to use to resolve things

defs - an Array of definitions to compare

Returns:

the definition to use as the result of the lookup, if the ambiguity was successfully resolved, otherwise null

isInProject

public boolean isInProject(ICompilerProject project)

Description copied from interface: IDefinition

Debugging method that can be used to assert that a definition is a specified project.

Specified by:

isInProject in interface IDefinition

Overrides:

isInProject in class DefinitionBase

Returns:

true if this definition is in the specified project.