QuantifiedPluralProdclass
Quantified plural phrase.
class
QuantifiedPluralProd
:
PluralProd
Superclass Tree (in declaration order)
QuantifiedPluralProd
PluralProd
NounPhraseProd
BasicProd
` object`
Subclass Tree
QuantifiedPluralProd
ExactQuantifiedPluralProd
BothPluralProd
qualifiedPluralNounPhrase(both)
explicitDetPluralNounPhrase(definiteNumber)
explicitDetPluralOnlyNounPhrase(definiteNumber)
qualifiedPluralNounPhrase(allNum)
qualifiedPluralNounPhrase(anyNum)
Global Objects
(none)
Summary of Properties
Inherited from NounPhraseProd
:
filterForCollectives
Inherited from BasicProd
:
firstTokenIndex
isSpecialResponseMatch
lastTokenIndex
Summary of Methods
getQuantity
getVerifyKeepers
resolveMainPhrase
resolveNouns
selectExactCount
Inherited from PluralProd
:
basicPluralResolveNouns
Inherited from NounPhraseProd
:
filterTruncations
Inherited from BasicProd
:
canResolveTo
getOrigText
getOrigTokenList
setOrigTokenList
Properties
(none)
Methods
getQuantity ( )
get the quantity specified - by default, this comes from the quantifier phrase in “quant_”
getVerifyKeepers (results)
OVERRIDDEN
Since the player explicitly told us to use a given number of matching objects, keep the required number, logical or not.
resolveMainPhrase (resolver, results)
Resolve the main noun phrase. By default, we simply resolve np_, but we make this separately overridable to allow this class to be subclassed for quantifying other types of plural phrases.
If this is unable to resolve the list, it can flag an appropriate error via the results object and return nil. If this routine returns nil, our main resolver will simply return an empty list without further flagging of any errors.
resolveNouns (resolver, results)
resolve the noun phrase
selectExactCount (lst, num, scopeList, resolver, results)
Select the desired number of matches from what the normal disambiguation filtering leaves us with.
Note that this will never be called with ‘num’ larger than the number in the current list. This is only called to select a smaller subset than we currently have.
By default, we’ll simply select an arbitrary subset, since we simply want any ‘num’ of the matches. This can be overridden if other behaviors are needed.
TADS 3 Library Manual
Generated on 5/16/2013 from TADS version 3.1.3