BasicResolveResultsclass
An implementation of ResolveResults for normal noun resolution.
class BasicResolveResults : ResolveResults
Superclass Tree (in declaration order)
BasicResolveResults
ResolveResults
` object`
Subclass Tree
BasicResolveResults
ActorResolveResults
DisambigResults
Global Objects
(none)
Summary of Properties
allowActionRemapping allowEquivalentFiltering issuingActor_ targetActor_
Summary of Methods
allNotAllowed ambiguousNounPhrase askMissingLiteral askMissingObject beginSingleObjSlot beginTopicSlot canResolveInteractively emptyNounPhrase endSingleObjSlot endTopicSlot filterWithDistinguisher getImpliedObject incCommandCount insufficientQuantity noMatch noMatchForAll noMatchForAllBut noMatchForListBut noMatchForLocation noMatchForPossessive noMatchForPronoun noMatchPossessive noteActorSpecified noteAdjEnding noteBadPrep noteEmptyBut noteIndefinite noteLiteral noteMatches noteMiscWordList noteNounSlots notePlural notePronoun noteWeakPhrasing nothingInLocation noVocabMatch reflexiveNotAllowed setActors singleObjectRequired uniqueObjectRequired unknownNounPhrase wrongReflexive zeroQuantity
Properties
allowActionRemapping
allow remapping the action
allowEquivalentFiltering
allow making an arbitrary choice among equivalents
issuingActor_
no description available
targetActor_
The target and issuing actors for the command being resolved.
Methods
allNotAllowed ( )
use the basic noMatch handling
ambiguousNounPhrase (keeper, asker, txt, matchList, fullMatchList, scopeList, requiredNum, resolver)
Handle an ambiguous noun phrase. We’ll first check to see if we can find a Distinguisher that can tell at least some of the matches apart; if we fail to do that, we’ll just pick the required number of objects arbitrarily, since we have no way to distinguish any of them. Once we’ve chosen a Distinguisher, we’ll ask the user for help interactively if possible.
askMissingLiteral (action, which)
there’s nothing to do with a literal at this point, since we’re not ranking anything
askMissingObject (asker, resolver, responseProd)
ask the resolver to supply an implied default object
beginSingleObjSlot ( )
we don’t care about these right now
beginTopicSlot ( )
no description available
canResolveInteractively (action)
Service routine - determine if we can interactively resolve a need for more information. If the issuer is the player, and the target actor can talk to the player, then we can resolve a question interactively; otherwise, we cannot.
We can’t interactively resolve a question if the issuer isn’t the player, because there’s no interactive user to prompt for more information.
We can’t interactively resolve a question if the target actor can’t talk to the player, because the question to the player would be coming out of thin air.
emptyNounPhrase (resolver)
return the response
endSingleObjSlot ( )
no description available
endTopicSlot ( )
no description available
filterWithDistinguisher (lst, dist)
filter a match list with a specific Distinguisher
getImpliedObject (np, resolver)
If we didn’t find any unknown words, it means that they used a word that’s in the dictionary in a way that makes no sense to us. Simply return an empty list and let the resolver proceed with its normal handling for unmatched noun phrases.
incCommandCount ( )
no description available
insufficientQuantity (txt, matchList, requiredNum)
abort with an error
noMatch (action, txt)
indicate that we couldn’t match the phrase
noMatchForAll ( )
show an error
noMatchForAllBut ( )
this isn’t an error - ignore it
noMatchForListBut ( )
show an error
noMatchForLocation (loc, txt)
let the (singular) owner object generate the error
noMatchForPossessive (owner, txt)
show an error
noMatchForPronoun (typ, txt)
show an error
noMatchPossessive (action, txt)
show an error
noteActorSpecified ( )
we don’t care about how many subcommands there are
noteAdjEnding ( )
abort with an error
noteBadPrep ( )
let the location object generate the error
noteEmptyBut ( )
show an error
noteIndefinite ( )
we don’t care about adjective-ending noun phrases at this point
noteLiteral (txt)
try reading an object response
noteMatches (matchList)
we don’t care about pronouns right now
noteMiscWordList (txt)
we don’t care about indefinites at this point
noteNounSlots (cnt)
we don’t care about this during execution - it only matters for determining the strength of the command during the ranking process
notePlural ( )
we don’t care about the matches just now
notePronoun ( )
we don’t care about unstructured noun phrases at this point
noteWeakPhrasing (level)
we don’t care about this during execution; it only matters for the ranking process
nothingInLocation (loc)
let the location object generate the error
noVocabMatch (action, txt)
Results gatherer methods
reflexiveNotAllowed (typ, txt)
show an error
setActors (target, issuer)
set up the actor parameters
singleObjectRequired (txt)
abort with an error
uniqueObjectRequired (txt, matchList)
abort with an error
unknownNounPhrase (match, resolver)
handle a noun phrase that doesn’t match any legal grammar rules for noun phrases
wrongReflexive (typ, txt)
show an error
zeroQuantity (txt)
abort with an error
TADS 3 Library Manual
Generated on 5/16/2013 from TADS version 3.1.3