ResolvedTopicclassparser.t[3094], english.t[2071]

no description available

Modified in english.t[2071]:
Modification to the ResolvedTopic for use with the English-language specific part of the library.

class ResolvedTopic :   object

Superclass Tree   (in declaration order)

ResolvedTopic
        object

Subclass Tree  

(none)

Global Objects  

(none)

Summary of Properties  

aName  getBestMatch  getTopicText  name  person  theName  tokens  topicList 

Summary of Methods  

construct  getTopicText 

Properties  

aNameparser.t[3115]

no description available

getBestMatchparser.t[3112]
no description available

getTopicTextparser.t[3113]
no description available

nameparser.t[3116]
no description available

personparser.t[3117]
no description available

theNameparser.t[3114]
no description available

tokensparser.t[3110]
no description available

topicListparser.t[3109]
if our list of topics has more than one entry, sort it in ascending order of length of name. That's because the shorter the name, the closer it may be to what the player actually typed.

Methods  

construct (lst, toks)parser.t[3095]

no description available

getTopicText ( )english.t[2078]
The English Tokenizer separates apostrophe-S from the word it's part of, so in restoring the original text we need to join any apostrophe-S back to the word it was separated from.

Adv3Lite Library Reference Manual
Generated on 01/03/2024 from adv3Lite version 1.6.2