CommandProdWithAmbiguousConjclassparser.t[1107]

Match class for two command phrases separated by an ambiguous conjunction (i.e., a conjunction that could also separate two noun phrases). Grammar rules based on this class must set the properties 'cmd1_' to the underlying 'predicate' production match of the first command, and 'cmd2_' to the underlying 'commandPhrase' production match of the second command.

class CommandProdWithAmbiguousConj :   CommandProd

Superclass Tree   (in declaration order)

CommandProdWithAmbiguousConj
        CommandProd
                BasicProd
                        object

Subclass Tree  

CommandProdWithAmbiguousConj
        commandPhrase(ambiguousConj)

Global Objects  

(none)

Summary of Properties  

cmdCounted_ 

Inherited from CommandProd :
getActorPhrase 

Inherited from BasicProd :
firstTokenIndex  isSpecialResponseMatch  lastTokenIndex 

Summary of Methods  

countCommands  getCommandSepIndex  getNextCommandIndex  isEndOfSentence  resolveFirstAction  resolveNouns 

Inherited from CommandProd :
execActorPhrase  hasTargetActor 

Inherited from BasicProd :
canResolveTo  getOrigText  getOrigTokenList  setOrigTokenList 

Properties  

cmdCounted_parser.t[1137]

counter: have we counted our command in the results object yet?

Methods  

countCommands (results)parser.t[1126]

count our commands

getCommandSepIndex ( )parser.t[1159]
Get the token index of the first command separator token. This is the first token that is not part of the underlying command.

getNextCommandIndex ( )parser.t[1169]
get the token index of the next command - this is simply the starting index for our second subcommand tree

isEndOfSentence ( )parser.t[1146]
does this command end a sentence

resolveFirstAction (issuingActor, targetActor)parser.t[1140]
resolve my first action

resolveNouns (issuingActor, targetActor, results)parser.t[1108]
no description available

TADS 3 Library Manual
Generated on 5/16/2013 from TADS version 3.1.3