ResolvedTopicclass | parser.t[3086], english.t[2067]

no description available

Modified in english.t[2067]:
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

`aName` | `parser.t[3107]`

no description available

`getBestMatch` | `parser.t[3104]`

no description available

`getTopicText` | `parser.t[3105]`

no description available

`name` | `parser.t[3108]`

no description available

`person` | `parser.t[3109]`

no description available

`theName` | `parser.t[3106]`

no description available

`tokens` | `parser.t[3102]`

no description available

`topicList` | `parser.t[3101]`

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[3087]`

no description available

`getTopicText ( )` | `english.t[2074]`

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 28/03/2016 from adv3Lite version 1.5